John_M

@gfjardim One issue I can see with the plugin is the fact that there are version clashes with the NerdPack plugin for some of the packages it installs. Another is this: Nov 2 14:33:05 Mandaue root: plugin: installing: /boot/config/plugins/preclear.disk.plg Nov 2 14:33:05 Mandaue root: plugin: skipping: /boot/config/plugins/preclear.disk/preclear.disk-2019.04.23a.txz already exists Nov 2 14:33:05 Mandaue root: plugin: skipping: /boot/config/plugins/preclear.disk/preclear.disk-2019.04.23a.md5 already exists Nov 2 14:33:05 Mandaue root: plugin: skipping: /boot/readvz already exists Nov 2 14:33:05 Mandaue root: plugin: setting: /boot/readvz - mode to 755 Nov 2 14:33:05 Mandaue root: plugin: running: anonymous Files under /boot can't be given execute permissions on Unraid version 6.8. Executables need to be copied from the boot flash to some other place before they can be run. See the release notes for the 6.8.0-rc series.

It's covered in the video, near the end. There's an nvram file defined and you have to undefine it before you can remove the VM.

I believe it's the other way round. Difficult hardware is easier to pass though to VMs if you use legacy boot for Unraid but UEFI boot (ie. OVMF instead of SeaBIOS) for the VM. But then, there are plenty of people who understand VMs better than me. One thing you do lose, if you UEFI boot Unraid, is the ability to run MemTest from the boot menu. UEFI boot seems to get stuck waiting for a keyboard if none is connected. All my hardware allows either mode but I have standardised on using BIOS boot.

The solutions to most of your problems are in this thread. Try updating the docker container.

Press the @ key and then start to type the person's user name. When you have entered enough you will be able to choose it from a floating menu that appears.

Is it configured to generate video preview thumbnails? That produces huge quantities of data. https://support.plex.tv/articles/202197528-video-preview-thumbnails/

Wrong. I only had to scroll back a single page to find this: and while we've been discussing it, yet another person has made exactly the same mistake.

Because you used the template editor and lost the customisations to your XML.

It has actually been mentioned repeatedly in this thread that if you use the template editor to change anything at all, then you need to restore the custom parts of the XML afterwards. It's mentioned in the video too.

The Clover bootloader is preconfigured for a 1920x1080 display. No idea, I'm afraid. I don't use Nvidia cards but I would expect the Nvidia driver to handle the audio. I would expect the driver not to be compatible.

Incomplete download: Read timed out. Try again later.

Just a suggestion that you keep a copy of the original working version of the XML so that you can repair your edited version when the customised parts get deleted by the template editor.

That's a common Hackintosh problem. I don't use i-anything. Did you change the NIC type as mentioned in earlier posts?

Yes, I should think it is. I don't know why it's downloading the wrong recovery media but a few people have noticed the same. It worked for me for Catalina and there hasn't been an update to the container since then so I can't explain why it seems to work for some people but not others. I can only tell you that I only used the container once and that was to set up a Catalina VM. I haven't used it a second time and probably won't because I'm not entirely sure how it works, where it's getting its files from or how they are modified from stock. I already have High Sierra and Mojave VMs, which I created the manual way, using installers downloaded directly from Apple on one of my real Macs. Though they took quite a bit of effort I understood and was in control of each step and the use of the EFI partition and Clover Configurator allowed customisation after the installation. This automated method uses a separate Clover boot volume and doesn't appear to allow the kind of customisation I need to ensure that the serial number doesn't clash with any genuine ones from Apple. EDIT: One thought struck me. Did you use it the first time to download the Mojave installer? Maybe there's a bug that causes it to remember the first installer and then download it again the next time, even if something else is selected. You could try removing the container and its appdata and installing it again.

You shouldn't need it for anything later than 1000-series processors, but it won't hurt. In case you struggle to find it it's usually at Advanced -> AMD CBS -> Power Supply Idle Control in the BIOS. Give it a try and report back to let us know if it makes a difference.

The settings would actually be for networking (Settings -> Network Settings). In that case you need to provide more information, unless someone else wants to make a guess.

Have you set up a different bridge for VMs? The container assumes br0, which is the default.

There's a file open on Disk1. That's all I can tell from that syslog snippet. Stop all containers and VMs, close terminal sessions, etc, and try again.

Try again later? [Errno -3] Temporary failure in name resolution',)': /simple/requests/

How does one set the serial number of the virtual Macintosh to be one of the invalid ones so there can be no chance of a clash with a real registered Mac?

Is that the first reboot after the installation or have you got past the point where you choose your language, region and set up a user account? If the latter then what customisation have you done to the EFI partition? It might be worth waiting for SpaceInvaderOne to upload his tutorial before proceeding.

To be honest, I wouldn't bother trying to upgrade from, say Mojave to Catalina. I'd just create a new clean Catalina VM and transfer my applications to it. FWIW I was able to apply the latest security update to High Sierra. I was dubious that it would work since on my real Macs it involved an update to the firmware too so I took a backup of my vdisk first.

Personally, I'd use something like cp --sparse=always /path/to/original.vdisk /path/to/backup.vdisk which would keep it as small as possible.

Try it and report back with your findings. I'm sure a lot of people will be interested. But back up your vdisk first.

There's still an offending post by @rorton on page 1 that needs redacting. You've already asked him to deal with it but I don't think he was listening.