1812

you can compare to my working xml, I don't have time at the moment to go line by line for you, but you may find differences (excluding drive locations and uuid, nvram file name, Mac address, etc...) don't worry about the added Qemu arguments in mine, they are for pcie definitions, as it was added for a patch in an RC. This xml also has 2 network "cards" for the e1000 and vmxnet 3 that I used for testing of different speeds. This xml comes from one of my 2 Mojave vm's, and this one is running a 730. topology was removed to maximize performance. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Desk Mojave</name> <uuid>94j4a882-fbde-110e-131h-f4531884123e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>5242880</memory> <currentMemory unit='KiB'>5242880</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='6'/> <emulatorpin cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/94j4a882-fbde-110e-131h-f4531884123e_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'/> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/domains/Mojave2/vdisk.img'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='9' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='10' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='10'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='88:58:00:cd:3d:c1'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0' multifunction='on'/> </interface> <interface type='bridge'> <mac address='53:24:00:8u:13:32'/> <source bridge='br0'/> <model type='vmxnet3'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0f' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x1f' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

if you're "just changing" using the GUI and not modifying the xml manually, that is probably your issue. It hasn't played real nice with osx vm's in the past. I only ever edit the xml.

are you removing the vnc bit from the xml?

I'd start over at the beginning as you may have borked it.

I created mine probably a little different than what is in the video (as I got impatient when Mojave was first released.) I left the steps here but they were based on the high Sierra install video. Everything else was essentially the same with no special modifications.

I don't use any vbios, so possibly start there.

Just follow the steps in the video at the top of the thread. Some settings won’t do anything and some will cause issues. I’m not near my computer for a bit so I can’t walk through each setting.

Time to start from scratch. Pro tip: once you have a base img up and running with vnc, make a backup copy on the array. That way of you mess it up later it only takes a few minutes to copy over a known working good img vs starting over again (learned this the hard way a few times.)

Sometimes on the forum we assume others have read documentation or watched the videos on basic vm setup and performance. It’s not your fault, but rather ours.

You may have misconfigured in the vm creation as well. But I can tell you that even if it's all 100% correct, running the img file in a parity protected array will never perform we'll.

This is your problem, plain and simple. you still need to do some tuning like isolating cpu's from unRaid, but you'll never get good performance after tuning/optimizing as every change or file that needs to be made to the img file takes first one spin of the parity disk and then another spin of both the parity and data disk. This does not take into account any other data being used on the drive as a share, or the system as a whole. If you want get a little bump, and you have an extra spinning drive, then you can mount it via unassigned devices plugin, or as a cache drive and move the img file there, then change the xml to reflect the new destination. then at least you'll have somewhat improved write performance vs what you have now which is going to be abysmal. Otherwise your current xml and logs show no major errors after a little bit of looking. Trying to disable sound will not help you as it is in the same iommu group as the video output of the gpu, which will then prohibit the vm from starting.

I'm currently looking at them, but go ahead and respond to what I put, is this vm hosted in a parity protected array on a spinning disk?

without looking at your diagnostics, it appears your img file is on the array disk 2, meaning a spinning disk. This means any reads are limited to about 110-120MB/s but writes are 30MB/s or less if you have a parity disk.

post full diagnostics file after failure to boot vm and the xml you are using (minus the apple key) This doesn't really tell me anything. Also just edit your post and remove this, as it has the apple key in it.

I got tired of flaky Nvidia audio around Sierra and just bought cheap usb audio adapters. They work perfectly and no futzing with kexts, installing this, removing that, screwing up the vm, punching the monitor, yelling at the dog... it's just simpler.

I've updated my original results with new info above, seems it's running higher bandwidth on (moderately) higher end card vs what I first tested with.

you may need a dummy plug to set a resolution. also, try team viewer or other similar screen sharing programs vs vnc.

leave your cable how they are. only thing to watch out for is making sure that your onboard/integrated GPU is set as primary in your bios. that will leave unRaid GUI on that monitor. then you can run cables to another monitor for your osx vm from the Nvidia card. You can use any other VM with the card as well, just not at the same time.

I currently use a 710 and a 730 on 2 different Mojave vm’s with no issues. You just pass it through and the native macOS drivers run it. That’s it. You may have issues with audio but that’s a minor annoyance vs not having video.

can't really use it for Mojave currently.

I use a 710 in one Mojave VM and a 730 in another with no issues ootb.

I can report that after updating to 6.7 rc4 and adding that to the xml, there is no change in reported cinebencz fps performance on high Sierra or Mojave. BUT both vm's also reported correctly the PCIe lane width before the patch. ---- EDIT Above testing was on a GT710, tested on another server running a 1060 and I'm happy to report the following OceanCL before 368.2 max fps Bandwidth host to device: 2.79GB/s, Device to host: 3.09GB/s OceanCL after 764.5 max fps Bandwidth host to device: 10.56GB/s, Device to host: 11.65GB/s Cuda Z before host to device: 27.9958MiB/s device to host: 3085.54MiB/s Cuda Z after host to device: 10.8593GiB/s device to host: 11.11552GiB/s Only a 1-3fps gain in Valley benchmark, but I suspect I might see some large gains on video editing due to higher bandwidth availability. Nice update!

go cheap 710 for now, see what happens in 6 months.

wait no longer:

I think eventually apple will have to authorize the drivers. It's just a waiting game. I've looked at radeon cards, but never made the jump.