ghost82

Can you please try this command in an unraid terminal and paste the output please? cat /proc/iomem

This is really odd...despite having: Mar 5 15:17:30 IchiTheTower kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot video=efifb:off efifb attaches the same...: Mar 5 15:17:30 IchiTheTower kernel: pci 0000:01:00.0: BAR 1: assigned to efifb This is new to me, I never saw this. Try this. Before starting the vm, run unraid terminal and type: echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind type enter at the end of each line. Then try to start the vm and see if gpu passthrough works.

Error 10 is a general error, unfortunately. The fact that you need to relocate memory sounds like a crap firmware. Or it could be an old or crap driver too. If your device has a firmware upgrade, upgrade it. If your device has new drivers apply newer. It could worth a try also deleting Upperfilters and LowerFilters registry keys, they should be located under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ Here you need to find the sub class of your device (it could be 4D36E96C-E325-11CE-BFC1-08002BE10318, but double check it) and inside this you will find these 2 keys.

That's strange because: BAR 1: can't reserve is an error due to memory being in use by something else. Repost diagnostics with changes applied please.

ok, try to change from this: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Dane/Windows/imagetest/Windows 10test1/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> To this: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Dane/Windows/imagetest/Windows 10test1/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk>

Yes, just a couple of more questions.. I understood you don't want to go with bare metal, I asked about it just to understand the workflow. So, case 1 with bare metal, you have a wds server machine and another machine with windows 10, connected over a network, each machine has its own hd with its operating system. You boot from the windows 10 machine over pxe network to the wds server, and from there in some way you are able to see the hd of the windows 10 machine and do your things. In case 2, with 2 vms (one wds server and one windows 10), you run both vms at the same time, both are connected within the same network, you boot the win10 vm over pxe successfully to the wds server vm, but the hd (img) of the windows 10 vm is not there, am I right? If this is the case, can you attach the xml of the 2 vms, especially that of the win10 client? I suspect the issue is that you have your hd in the win 10 vm (img file) attached to a virtio controller and changing it to sata may solve your issue, if you attach the xml I can modify it.

I'm quite sure you explained well, however I never did such things, so if you could explain more into details it will help, and maybe someone else can reply instead of only people who managed with wds/pxe etc. What I understood is only that you have a windows 10 vm up and running into unraid. What you want to do next is confusing for me, but it's probably my fault! Can you specify which tools you use on bare metal, which are the physical machines involved (for ex: you have a machine with win10, you have a wds server, you have another third party pc, ?) and how the workflow works (with commands/instructions). Thanks

Never tried, so these are only suggestions. I think too that's the issue is missing driver. I would try these two options: 1. add driver package to wds, the drivers of the emulated network card are into the separate virtio iso image which you can download for free; windows doesn't include any virtio driver. OR 2. I would try to change the virtio model type, I think drivers should be builtin if using for example: <model type='e1000-82545em'/>

RX 580 should have more or less the same performance as your nvidia 1060. For compatibility: https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html Cons: gpu reset bug Notes: - for polaris avoid XFX, PowerColour, HIS and VisionTek brands - only used cards available, at current prices higher (about 2x) than to that they were sold as new, old and who knows if they were stressed (mining?) or not - if you will going to use port adapters (dp to hdmi, dp to vga, etc) mac os may not like them

VL805/806 seems a nogo because of broken firmware, sorry. I would suggest a 20$/Eur usb card like the inateck with fresco fl1100 controller.

Yes, as you can see: Mar 3 08:50:30 TheWall kernel: pci 0000:01:00.0: BAR 1: assigned to efifb Mar 3 08:52:02 TheWall kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x4000000000-0x43ffffffff 64bit pref] ... ... BAR 1 is already in use by efifb, so you need to not make it to attach, or detach on the fly. append initrd=/bzroot video=efifb:off Check also your vbios, best way is to dump from linux, but gpu-z is also fine, the important thing is that you do not download one from internet. If dumped with gpu-z remove the header.

This is wrong, it must be on the same line: append initrd=/bzroot video=vesafb:off video=efifb:off Then reboot. PS: most probably you don't need video=vesafb:off, unless you are booting unraid in non uefi mode

From your diagnostics you didn't apply this, or you applied them wrong, try to apply or post a screenshot of your changes to syslinux config. Syslog is empty (???)

diagnostics

Main difference is that in first case you attach the real disk to an emulated controller (scsi in your example), in the second case you pass directly the real disk+controller. In first case there's some overhead because of the emulated controller (maybe not noticeable at all in everyday use, unless you read the numbers coming from a disk benchmark app).

Try with video=efifb:off in the append line of your syslinux config.

in a unraid terminal: fdisk /path/to/vdisk.img Type: a Choose the number to the corresponding partition you want to make "active". Type w to write changes

For example, for this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> You have first block with source address 03:00.0 You have second block with source address 03:00.1 You have first block with target address 03:00.0 You have second block with target address 04:00.0 This is wrong. To fix it, you add multifunction='on' in the first block, and you change in the second block, bus, slot and function, so that it has the same target bus and slot, but different function: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> Yes

I noticed that acidanthera has it's own audk repository... It's a forked edk2 repository with added commits from acidanthera's developers, which is synched with edk2. At the time of writing it's still synched with 202111 stable (usually it's synched with stable after some weeks), maybe we should use that instead of the original edk2 repo, for better support (?). I will compile and share it too once it's synched with 202202. Update: attached ovmf compiled from audk repo (synched with edk2 stable 202202) OVMF_AUDK_202202-06-03-2022.zip

It's only your choice... With vdisk, copy vdisks on new drive(s), create a new vm and point the vdisk(s) to the moved one(s). For disks/sata-nvme controllers passthrough, clone the vdisk to the real disk and passthrough the whole disk by-id (or any other identification method), or passthrough the sata/nvme controller to which the disk is attached, without setting any virtual controller.

What video driver are you using?

diagnostics?

You may need to isolate the gpu (attach to vfio at boot), all the components, video, audio. You may need to pass to the vm not only the video, but also the gpu audio in a multifunction device. You may be affected by the infamous amd gpu reset bug.

Take into account that mac os needs to have the drivers for the hardware. And usb can be quite tricky to work, I couldn't make work (or better, they work somehow but with strange behavior) asmedia 1042 and intel c600; only fresco fl1100 worked (the one in the screenshot above). The main difference between windows and mac os is that near everything you attach to windows will probably work, not in mac os.

Try this: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox BigSur</name> <uuid>d401e640-fd71-4e48-bf57-d03a43a02854</uuid> <description>MacOS Big Sur</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='11'/> </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/d401e640-fd71-4e48-bf57-d03a43a02854_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> </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 BigSur/BigSur-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/BigSur-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='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox BigSur/macos_disk.img'/> <target dev='hde' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <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='0x01' 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='0x01' 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='0x01' 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='0x01' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <interface type='bridge'> <mac address='52:54:00:f3:7c:d7'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disk1/vbios/MSI.GT710.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0749'/> <product id='0x1000'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2188'/> <product id='0x0ae1'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <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> Replace oskey at the bottom