Everything posted by ghost82
-
Atheros AR9280 Wireless Card BAR error
Hi, I'm not 100% sure, because in the diagnostics logs the latest messages in qemu don't seem to be correct in disabling device.json: -device '{"driver":"vfio-pci","host":"0000:05:00.0","id":"hostdev0","bus":"pci.0","addr":"0x6"}' \ The above is in json format. However it's strange that you are able to run the vm without any error with the current xml... If limetech updated qemu without updating libvirt, maybe you need to change in the xml from this: <qemu:capabilities> <qemu:del capability='device.json'/> </qemu:capabilities> to this: <qemu:capabilities> <qemu:del capability='device.json+hotplug'/> </qemu:capabilities> Worth a try... Attach new diagnostics with this change. It's a pity that the new libvirt isn't included in RC5, but I saw that you already wrote it in the appropriate thread.
-
** Hackintosh ** Tips to make a bare metal MacOS
It never happen to me with mac os vms, but this can be very tricky to solve, it happens sometimes with my win 11 vm and still I don't understand why, the system is shutting down, black screen, but the vm is reporting in execution and needs a force stop. Does it happen randomly or always with your vm? You can try these, hope it helps: 1. try to lower the pc-q35 version, try for example 5.1, without ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off 2. try to shutdown from the guest 3. try to shutdown from unraid terminal: virsh shutdown macosVMname This uses acpi command Or: virsh shutdown macosVMname --mode agent This uses qemu-guest-agent instead of acpi Or: virsh -c qemu:///system shutdown macosVMname This last command seems working ok for my win11 vm, no more random hangs. 4. It can be related to hardware passthrough: you could try to remove all optional passed through hardware, add one at a time, and look at what it's causing the hang.
-
Unraid GPU Passthrough failing after Hardware change
At which vm should we look at?You have 19....
-
I'm having an odd issue with AMD gpu passthrough to macOS VM. The GPU is sort of working, never seen this issue before.
Mac os doesn't like qxl video on a bus different than 0 (i.e.: built-in), that's probably why you are getting the "guest has not initialized the display"; moreover looking at your xml you attached the qxl device to a "pcie to pci bridge", instead of a "pcie root port". The whole layout needs to be re-arranged. Moreover the gpu (digital audio/video) is not set as multifunction. I don't know if mac os likes qxl (and vnc) + gpu passthrough (it depends on the smbios you chose, if the real mac you are emulating has an integrated gpu then it's ok, otherwise not), if it doesn't work try also to delete vnc+qxl blocks from the xml, i.e. delete this from the xml in this post, below: <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> Replace the whole xml with this: <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit 5ad5f709-3506-4953-b339-152a9fa799c3 or other application using the libvirt API. --> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox Monterey</name> <uuid>5ad5f709-3506-4953-b339-152a9fa799c3</uuid> <description>MacOS Monterey</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="Monterey.png" os="osx"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5ad5f709-3506-4953-b339-152a9fa799c3_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <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/user/domains/Macinabox Monterey/Monterey-opencore.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/isos/Monterey-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Macinabox Monterey/macos_disk.img'/> <target dev='hde' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <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='0x8'/> <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='0x9'/> <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='0xa'/> <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='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:3b:a6:7d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </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'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/HD7870_vbios.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04f2'/> <product id='0x1053'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1a2c'/> <product id='0x2c27'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=... <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/> </qemu:commandline> </domain> Readd the osk at the bottom.
-
NVME M.2 Passthrough
Please take into account that above xml will need to be changed once 6.10RC5 or stable will be released, since this will include the newer libvirt 8.2.0. More into details it's not recommended the workaround I proposed, i.e. delete the capability of device.json, but a workaround was only fixed with libvirt 8.2.0. Anyway, if you won't be able to fix it by yourself, come again here and ask.
-
NVME M.2 Passthrough
Replace the whole xml with this and save, then try to start the vm: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11</name> <uuid>e42cd44a-88be-9deb-e2a1-57e99d0b3a4a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='10'/> <vcpupin vcpu='1' cpuset='24'/> <vcpupin vcpu='2' cpuset='11'/> <vcpupin vcpu='3' cpuset='25'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='26'/> <vcpupin vcpu='6' cpuset='13'/> <vcpupin vcpu='7' cpuset='27'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/e42cd44a-88be-9deb-e2a1-57e99d0b3a4a_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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/disks/Windows_VM/Domain/Windows 11/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <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='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f1:89:b7'/> <source bridge='virbr0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </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'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/VM/Domain/vBios/RTX2080.rom'/> <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='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <alias name='ua-sm2263'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x0025'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.ua-sm2263.x-msix-relocation=bar2'/> </qemu:commandline> <qemu:capabilities> <qemu:del capability='device.json'/> </qemu:capabilities> </domain>
-
NVME M.2 Passthrough
Firmware crap (often seen in nvme controllers, but also other devices), not unraid fault, you need to relocate the bar in the xml. Depending on the libvirt/qemu versions, one of the following 3 solutions apply; assign an alias to the nvme controller, then add the custom arg I think for unraid <= 6.10RC2: ... <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='YOURNVMEALIAS'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </hostdev> ... ... <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.YOURNVMEALIAS.x-msix-relocation=bar2'/> </qemu:commandline> </domain> Obviously replace the bus/slot/function addresses (source and target) with that of your controller. ------------------------------------------ For Unraid >= 6.10RC3 and libvirt <8.2.0: ... <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='YOURNVMEALIAS'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </hostdev> ... ... <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.YOURNVMEALIAS.x-msix-relocation=bar2'/> </qemu:commandline> <qemu:capabilities> <qemu:del capability='device.json'/> </qemu:capabilities> </domain> Obviously replace the bus/slot/function addresses (source and target) with that of your controller. ------------------------------------------ For libvirt>=8.2.0 (a version of unraid with libvirt 8.2.0 is still not released): ... <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='YOURNVMEALIAS'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </hostdev> ... ... <qemu:override> <qemu:device alias='YOURNVMEALIAS'> <qemu:frontend> <qemu:property name='x-msix-relocation' type='string' value='bar2'/> </qemu:frontend> </qemu:device> </qemu:override> </domain> Obviously replace the bus/slot/function addresses (source and target) with that of your controller.
-
Windows 10 Vm freeze with amd 5950x and amd GPU
not needed to see if it works or not, you can optimize eventually later.
-
Windows 10 VM without color and crash
Yes, probably that memory adresses were in use by efifb: that commands disables efi framebuffer (efifb), so you can pass it. It's an alternative to video=efifb:off kernel argument.
-
Windows 10 VM without color and crash
Check with "cat /proc/iomem" command in terminal in unraid what is using memory addresses in range 0x7000000000-0x77ffffffff and blacklist/disable it with a kernel parameter (syslinux configuration).
-
Windows 10 Vm freeze with amd 5950x and amd GPU
You need to passthrough all the components of the gpu, you didn't pass the audio portion: 0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] [1002:6610] (rev 83) Subsystem: Dell Radeon R5 340X OEM [1028:0083] Kernel modules: radeon, amdgpu 0b:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] [1002:aab0] Subsystem: Dell Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] [1028:aab0] So: <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/Downloads/192110.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> </hostdev> Make sure 192110.rom is a proper vbios for your gpu. You need to isolate the gpu, bind to vfio at boot iommu group 27.
-
Rename Primary vDisk Folder?
Yes. Backup first, if something doesn't work fix it or revert.
-
Help | GPU Passthrough not working in any VM | Both Nvidia & AMD
Sounds like wrong vbios, dump your own. correct not needed, but ok may be not needed but correct i440fx doesn't work with mac os Moreover, in your mac os vm: <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> Don't use 6.2, use max 6.0. correct 1050ti not working with mac os monterey, max supported high sierra. Don't use downloaded vbios
-
Windows VM stopped working
Check bios settings especially vtx/vtd settings, maybe they resetted for whatever reason.
-
Passthrough new Video Card
It should be same, you can have them in separate iommu groups (alone) or in the same iommu group (alone, without any other device, apart bridges). Make sure to setup multifunction for audio/video in the xml.
-
can't proceed Win 11 VM install / buttons not clickable due to screen res
did you try to scroll with the mouse?
-
Ubuntu server VM, Failed to write entry... ignoring: read-only file system errors - production unit
I think you could try: 1. identify the port from reading labels on your motherboard (may be difficult to read) 2. identify the port from reading the manual of your motherboard 3. identify the port from the attached disk: sdf should be your 'parity2 disk' Nevermind, you have a pcie sata card?do the same as above replacing 'motherboard' with 'your sata card' https://delightlylinux.wordpress.com/2019/08/02/how-to-find-a-hard-drives-sata-port-in-bash/#:~:text=To find the physical SATA,%3A0%3A0%3A0. [2:0:0:0] disk ATA Hitachi HUS72404 A5F0 /dev/sdb /dev/sg1 dir: /sys/bus/scsi/devices/2:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1/ata2/host2/target2:0:0/2:0:0:0] [5:0:0:0] disk ATA SanDisk SSD PLUS 04RL /dev/sdc /dev/sg2 dir: /sys/bus/scsi/devices/5:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1/ata5/host5/target5:0:0/5:0:0:0] [6:0:0:0] disk ATA SanDisk SSD PLUS 04RL /dev/sdd /dev/sg3 dir: /sys/bus/scsi/devices/6:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1/ata6/host6/target6:0:0/6:0:0:0] [9:0:0:0] disk ATA Hitachi HUS72404 A5F0 /dev/sde /dev/sg4 dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2/0000:02:06.0/0000:06:00.0/ata9/host9/target9:0:0/9:0:0:0] [10:0:0:0] disk ATA Hitachi HUS72404 A5F0 /dev/sdf /dev/sg5 dir: /sys/bus/scsi/devices/10:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2/0000:02:06.0/0000:06:00.0/ata10/host10/target10:0:0/10:0:0:0] [11:0:0:0] disk ATA Hitachi HUS72404 A5F0 /dev/sdg /dev/sg6 dir: /sys/bus/scsi/devices/11:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2/0000:02:06.0/0000:06:00.0/ata11/host11/target11:0:0/11:0:0:0] [12:0:0:0] disk ATA Hitachi HUS72404 A5F0 /dev/sdh /dev/sg7 dir: /sys/bus/scsi/devices/12:0:0:0 [/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2/0000:02:06.0/0000:06:00.0/ata12/host12/target12:0:0/12:0:0:0]
-
Trouble Passing through Nvidia GTX 770 GPU to Windows 11 VM
Unfortunately no errors related to your vm in the logs, so something is happening inside the vm. You can try to apply these tips: https://forums.unraid.net/topic/121833-passthrough-new-video-card/?do=findComment&comment=1112210
-
Passthrough new Video Card
Layout of q35 is different than i440fx, you cannot just change machine type: faster option is to create a new vm pointing to the same vdisk(s).
-
Passthrough new Video Card
You don't have that 3060 installed, you have the 'old' 1070, so I cannot say anything about the 3060. For the 1070: If you didn't change anything this could be hardware related (?) Unfortunately there's nothing useful in the logs. Things to try: 1. check that the gpu is fully functional in bare metal 2. set the gpu as multifunction, from this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/1070gpu vbios.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </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='0x00' slot='0x08' function='0x0'/> </hostdev> to this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/1070gpu vbios.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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='0x00' slot='0x06' function='0x1'/> </hostdev> 3. bind to vfio at boot iommu group 1: you will have no video output for unraid, the screen will seem frozen, connect from another device on your lan 4. change the physical pcie slot of the gpu (top slot for vfio doesn't work well with some bios/mb) 5. change machine type to q35, it better supports pcie passthrough 6. make sure '1070gpu vbios.rom' is working for your gpu 7. for black screen issues set vm with vnc and enable remote desktop inside the vm, then set again gpu passthrough and connect to the vm with remote desktop and look at system devices 8. for black screen issue do '7' and install latest nvidia drivers from remote desktop 9. check for bios updates for your motherboard
-
Win10 VM Best Practices - Sluggish Desktop GUI Experience
One of the things to try when you have issues with a vm is create a new vm with the same settings, pointing at the old vdisk(s); this basically restores the ovmf vars file with a clean one; so yes, restoring vars file with a fresh one is a thing to try. BTW: there's lada and lada...
-
Win10 VM Best Practices - Sluggish Desktop GUI Experience
Then I don't know but happy it's solved now. Sometimes I got weird issues with the ovmf vars file which I was never able to track down and only replacing it with a new one fixed the issues, but never had performance issues related to the vars file. By replacing the vars file you basically resetted the cmos. That file stores nvram variables, it's sometimes recommended to reset it as a general fix, especially on macintosh, who knows what happened...take your solution as a black box and be happy
-
Trouble Passing through Nvidia GTX 770 GPU to Windows 11 VM
Code 43 depends on different issues, you attached only the xml, and the xml has no errors. https://forums.unraid.net/topic/37579-need-help-read-me-first/ Tip....: attach diagnos.....
-
Ubuntu server VM, Failed to write entry... ignoring: read-only file system errors - production unit
It should be the disk, if smart data are ok check connecting cables. Moreover, looking again at diagnostics, your hd sdf is dropping offline and resetting. Mar 7 01:27:06 SERVER-VM kernel: ata10.00: exception Emask 0x10 SAct 0x400000 SErr 0x400000 action 0x6 frozen Mar 7 01:27:06 SERVER-VM kernel: ata10.00: irq_stat 0x08000000, interface fatal error Mar 7 01:27:06 SERVER-VM kernel: ata10: SError: { Handshk } Mar 7 01:27:06 SERVER-VM kernel: ata10.00: failed command: WRITE FPDMA QUEUED Mar 7 01:27:06 SERVER-VM kernel: ata10.00: cmd 61/40:b0:70:7d:e1/05:00:27:01:00/40 tag 22 ncq dma 688128 out Mar 7 01:27:06 SERVER-VM kernel: res 50/00:40:70:7d:e1/00:05:27:01:00/40 Emask 0x10 (ATA bus error) Mar 7 01:27:06 SERVER-VM kernel: ata10.00: status: { DRDY } Mar 7 01:27:06 SERVER-VM kernel: ata10: hard resetting link
-
Win10 VM Best Practices - Sluggish Desktop GUI Experience
maybe you changed the machine type version? Same xml settings but new qemu versions with different machine versions could change the irq of the devices.