ghost82

fx 1800 is not supported unless you run avery old version of mac os, like el capitan.

check that you don't have any other device in iommu group 61 except for the gpu audio/video. If it contains other devices use acs patch to hopefully split the group. Make sure to bind to vfio at boot gpu audio and video. Try also to enable unsafe interrupts.

It should be an issue within the os guest, not an issue with qemu or kvm. The guest agent in the guest is needed to send some commands from the host to the guest. There should be no need of the qemu-kvm package in the guest. It seems that the swap disk cannot be found. See if this helps with your issue: https://bbs.archlinux.org/viewtopic.php?id=247036 It's for arch, but you can consider and search as a general linux issue. Or this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962359 Or this: https://forum.manjaro.org/t/some-clarification-on-hibernate-needed/108659/4

so is it solved now?when you boot the recovery you have a rectangular window with 4 or 5 choices (can t remember exactly). One of those is disk utility.

In your log you have: Aug 3 10:53:47 Foundation kernel: pci 0000:0c:00.0: BAR 1: assigned to efifb Boot with: video=efifb:off in your syslinux config, reboot and try.

What kind of recovery are you talking about?I never seen a mac os recovery withut disk utilities...any screenshot?

You probably need to format it (apfs) from disk utility, booted from recovery, next exit disk utility and choose install mac os.

Look for "port forwarding": you set it in the router. Basically you connect to an ip on port xxx and the router redirects it on port yyy (80, or whatever you set), so you can have different services on the same port.

Ventura is not officially supported. Anyway, to boot and install it you should upgrade opencore and all the kexts to the latest release version. Make sure you have also a real haswell or newer cpu, cpus with no avx2 are no more supported. You may need to change also the emulated cpu from penryn (passthrough or emulated haswell+).

Did you install the correct version of the web drivers? Did you modify the opencore config.plist to enable web drivers on boot? --> in boot-args: nvda_drv_vrl=1 About vnc, the qxl virtual video adapter must be on bus 0, better to be in bus 0, slot 1, function 0.

It seems your rom file is empty, you didn't dump it correctly. If it's the only gpu in your system you couldn't dump it in linux. Either add another primary gpu and move the 1060 in a secondary slot to dump the vbios, or boot windows and dump it with gpuz (and check if you need to remove the header with a hex editor), or try your luck and download a rom from internet. Edit: reading again, and you have igpu which should be set as primary when you boot unraid. The above is still valid, make sure you have dumped a proper file.

check this, by SimonF:

No, no difference, but still the 6600/600xt lack the full x16; however technology of 6000 series is more advanced than 5000 series so it somewhat compensate this.

You can look at the geekbench site to have a view of opencl/metal benchmarks or any other site with benchmark results; from what I see the 6600xt will perform slightly better than the 5600xt.

Not sure, the 5000 series suffers the reset bug as you know, if you look at the gnif vendor reset github repository (issues) you will find different cases, some successful, some other not, this may depend not only on the gpu but also on the mb bios and how it handles the gpu, so it's quite difficult to say if it will work for sure or not. I know the difference in price is quite a lot for a 5600xt and a 6900xt, but I would think twice before buying a 5000 series card..I still would prefer the 6600xt even if I agree with you that it sucks that it has 8 lanes...however this depends on the user case: unless you use the gpu also in windows for gaming, and gaming some quite powerful games, the 6600xt will perform quite well.

Maybe related to wrong path, from your screenshot system has a capital letter: /mnt/user/System/... Same for other paths, log is reporting all lower case. You need to generate proper smbios data, you need to setup en0 interface as "built-in", don't use vmxnet3, these are the main things. Search the forum for imessage/facetime, this topic has been discussed several times.

The best? 6900xt, better if it's the reference amd model (from big sur 11.4), and avoid the xtxh models, go for xtx. If it costs too much the 6600xt is ok (from monterey 12.1), also the 6600 non xt version. Any other prior model should have some issue with the reset bug, maybe fixable, but if you don't want any reset bug go for one of the 6000 series (6900xt or 6600xt or 6600 or 6800xt, NOT the 6700xt).

Do you need both gpus in your vm?Leave the igpu for unraid and pass only the 1060 to the vm. Delete this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </hostdev> Having said that, these are the errors: 1- the 1060 passthrough setup is wrong, replace this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> with this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> 2- Enable unsafe interrupts: Settings -> VM -> change "VFIO allow unsafe interrupts" to Yes, then reboot the server

vmdk needs to be converted; I suggest to convert your vmdk image to raw img, then you could use qemu-img utility to do what you want.

I bet your vm name is not "Macinabox BigSur of VM", but maybe "Macinabox BigSur"

You setup the disk with virtio: no windows version includes virtio drivers. I suggest to setup the vm with legacy devices, sata, ide, e1000, etc, at least for the basic devices.

Something like this should work, set it to run at array start: #!/bin/bash #DEFINE VARIABLES# SourceFile='/ABSOLUTE/PATH/TO/YOUR/vgabios-qxl.bin' TargetFolder='/user/share/qemu/' #COPY VBIOS# cp "$SourceFile" "$TargetFolder" Copy your vgabios.qxl.bin somewhere accessibile to unraid Modify the path of SourceFile Check TargetFolder is correct

Hi, you attached diagnostics with: - no passthrough in the vm settings; - no gtx 1060 installed in the system No way to tell you if something is wrong in the config or not. Anyway, as a general approach, if I were you I: 1- install the matrox g200 in the primary slot 2- install the gtx 1060 in a secondary slot [3- setup the matrox as primary gpu in bios] [4- allow unsafe interrupts in unraid] 5- attach to vfio at boot all components of the gpu (use acs override patch if components are in the same iommu group with other devices) 6- reboot [7- dump the gpu vbios] 8- setup the gpu passthrough of the 1060 in the gui (all components should be passed, audio, video, [usb]), in a q35+ovmf machine, [pass your dumped vbios] 9- switch to the xml view and change bus/slot/functions, so that the gpu in the guest is a multifunction device [...] may be required If you run a linux machine you should see some output on the monitor, probably it will use nouveau drivers, but this depends on the linux distribution. If you want to switch to nvidia drivers refer to specific forums, as installing the nvidia drivers can be a mess.

You should start by reading/following this discussion:

Hi, when a vm has the autostart set you will find its xml (symlink) in /etc/libvirt/qemu/autostart/ folder, for ex. /etc/libvirt/qemu/autostart/myvm.xml So, your script could check for files inside that folder to know if a vm is set to autostart or not.