ghost82

Multifunction is wrong, the audio must be in the same bus, same slot, different function, so change to this: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/gt 1030.rom'/> <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='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> Try..other than that I could think about the vbios, can you share it to have a look?

Hi, you need to setup the gpu as multifunction in the vm, it should be isolated (bound to vfio), allow unsafe interrupts should be enabled in unraid, newest drivers should be installed, modification to syslinux config may be required (es: video=efifb:off), q35+ovmf should be preferred, video rom should be dumped from your gpu and not downloaded somewhere. It is the opposite, from v465 drivers should work as expected inside a vm, so the newest drivers should be preferred. diagnostics may help to identify the issue.

Hi, there was another case about another user having bcd boot error (it was a windows 10 vm) when trying to boot from the nvme; bare metal boot was working. He was using seabios too, as you. He was using unraid 6.10.1 This case seems similar to yours and maybe it can be solved the same way: https://forums.unraid.net/topic/124021-win-10-vm-bootbcd-io-error-after-unraid-6101-update/ I compiled the latest version of seabios (1.16.0-4-gdc88f9b), maybe you can try this. Extract file bios.bin from the zip and save it somewhere on unraid (i.e. /path/to/bios.bin). Open the vm settings in xml view and change from: <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> </os> to: <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader type='rom'>/path/to/bios.bin</loader> <boot dev='hd'/> <bootmenu enable='yes' timeout='30000'/> </os> Try to boot. Seabios-1.16.0-4-gdc88f9b.zip

You should not edit the go file at all for gpu passthrough. General steps are: - bind to vfio in system devices all the components of the gpu - setup the vm by passing through all the bounded devices in a multifunction device - for blackscreen/garbage screen additional entries in the syslinux configuration, for example video=efifb:off

You could use virsh command: virsh destroy vmname to force stop the vm virsh shutdown vmname to gracefully shutdown the vm virsh undefine --nvram vmname to delete the vm (note the --nvram, required for ovmf vms) virsh list --all to list the status of all vms PS: as far as 'vmname', if it contains space(s) use double quotes, for example: virsh destroy "Windows 10"

Hi, do you have any example for this?

default?just go to the network settings and set your nics as you want. Simply setup bridge for at least one adapter that has internet access.

What's your goal?Having internet access inside vms? As said virbr0 comes from libvirt itself, it's the default nat network; with virbr0 the vms will not be seen on the lan. So...as a general advice, I would suggest to use a bridge connection, such as br0: to do this you need to configure in unraid a nic (eth0 for example) in bridge mode (br0 for example), and use br0 in the vm settings; eth0 and br0 will be in the same range of ip addresses with the ip usually assigned by the router itself. It seems you messed with the netowrk settings in unraid and you don't have any brX bridge defined.

Not sure I understood correctly. From your image you are using virbr0 network: virbr0 is a NAT connection, with dhcp managed by libvirt, virsh net-edit default: <network> <name>default</name> <uuid></uuid> <forward mode='nat'/> <bridge name='virbr0' stp='on' delay='0'/> <mac address='xx:xx:xx:xx:xx:xx'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254'/> </dhcp> </ip> </network> As you can see the guest will have an ip in the range 192.168.122.2-254. So check within the vm if an ip is assigned. Or, your issue is that you can't see an ip address of the vm in the unraid gui? The message is pretty self explanatory (I think): Now..the guest IS running, but you probably don't have the qemu guest agent installed inside the vm or it is not working as expected: I think unraid is using a guest agent command to get the ip of the vm. Simply install it inside the vm or fix it.

Interesting matter! To connect a vm to the host I can think about different ways: - passthrough (vt-d) a high speed network card to the vm, like infiniband and have a second network card of the same high speed type on the host, connected to the same switch - use a bridge connection between the host and the vm: you can have a bridge connection between a host and a vm having a physical nic on the host, or even without having a physical nic, by creating a dummy network interface in the host (this is something I've just learnt now) - mount filesystems in the vm in a different way than the more standard network protocols (ntfs or smb), depending on the guest/available drivers/compatibility: for example 9p fs about bridge connections and virtio/virtio-net: virtio and virtio-net are para-virtualized drivers and the operating systems know that it's not a real physical device; there isn't a real "link speed" applied, if you read one in a guest it's only cosmetic. This is true also if you setup a bridge connection bound to a real nic: in my case for example I have a virtio bridge connection bound to an intel 82574L 1GbE physical nic in the host, but an iperf3 test host<->guest shows speeds up to 16-17 Gbits/s. As far as I know virtio/virtio-net is the fastiest and easiest way to connect vms.

yes, that is correct, save after delete.

switch to xml view and delete this block (similar): <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x03f0'/> <product id='0x0324'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> save and try

Is the keyboard issue in the host or in the vm?I mean, is it an error when you start the vm and you get the error in unraid about device not being there, or windows is trying to boot but fails because there's no keyboard?

It seems you have a panic for your HD 7450, probably when you get to the vm tab: Jun 22 06:36:50 BlackBox kernel: fbcon: radeondrmfb (fb1) is primary device Jun 22 06:36:50 BlackBox kernel: fbcon: Remapping primary device, fb1, to tty 1-63 Jun 22 06:36:50 BlackBox kernel: BUG: kernel NULL pointer dereference, address: 0000000000000194 Jun 22 06:36:50 BlackBox kernel: #PF: supervisor read access in kernel mode Jun 22 06:36:50 BlackBox kernel: #PF: error_code(0x0000) - not-present page Jun 22 06:36:50 BlackBox kernel: PGD 0 P4D 0 Jun 22 06:36:50 BlackBox kernel: Oops: 0000 [#1] SMP PTI Jun 22 06:36:50 BlackBox kernel: CPU: 5 PID: 30416 Comm: rpc-libvirtd Not tainted 5.15.46-Unraid #1 Jun 22 06:36:50 BlackBox kernel: Hardware name: GIGABYTE MX31-BS0/MX31-BS0, BIOS R12 01/09/2020 Jun 22 06:36:50 BlackBox kernel: RIP: 0010:fbcon_del_cursor_timer+0x1a/0x39 Jun 22 06:36:50 BlackBox kernel: Code: 5e e9 cd e7 c3 ff 58 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 44 00 00 48 81 bf e8 01 00 00 74 14 47 81 75 26 53 48 8b 9f 40 03 00 00 <f6> 83 94 01 00 00 02 74 13 48 8d bb d8 00 00 00 e8 9f f9 c5 ff 83 Jun 22 06:36:50 BlackBox kernel: RSP: 0018:ffffc900019379a8 EFLAGS: 00010246 Jun 22 06:36:50 BlackBox kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Jun 22 06:36:50 BlackBox kernel: RDX: 000000000000003e RSI: 0000000000000000 RDI: ffff888105baf800 Jun 22 06:36:50 BlackBox kernel: RBP: ffff88868521d000 R08: 0000000000000001 R09: 0000000000000001 Jun 22 06:36:50 BlackBox kernel: R10: 0000000000aaaaaa R11: ffffc900077d8420 R12: 000000000000003e Jun 22 06:36:50 BlackBox kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000 Jun 22 06:36:50 BlackBox kernel: FS: 000014b0084e7640(0000) GS:ffff88885fd40000(0000) knlGS:0000000000000000 Jun 22 06:36:50 BlackBox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 22 06:36:50 BlackBox kernel: CR2: 0000000000000194 CR3: 00000001a2132005 CR4: 00000000003726e0 Jun 22 06:36:50 BlackBox kernel: Call Trace: Jun 22 06:36:50 BlackBox kernel: <TASK> Jun 22 06:36:50 BlackBox kernel: con2fb_release_oldinfo.constprop.0+0x81/0x129 Jun 22 06:36:50 BlackBox kernel: set_con2fb_map+0x146/0x27b Jun 22 06:36:50 BlackBox kernel: fbcon_fb_registered+0x11f/0x12e Jun 22 06:36:50 BlackBox kernel: register_framebuffer+0x25d/0x2ae Jun 22 06:36:50 BlackBox kernel: __drm_fb_helper_initial_config_and_unlock+0x3bf/0x494 [drm_kms_helper] Jun 22 06:36:50 BlackBox kernel: radeon_fbdev_init+0xdd/0x102 [radeon] Jun 22 06:36:50 BlackBox kernel: radeon_modeset_init+0x89b/0x8bd [radeon] Jun 22 06:36:50 BlackBox kernel: radeon_driver_load_kms+0xf2/0x197 [radeon] Jun 22 06:36:50 BlackBox kernel: drm_dev_register+0xf1/0x1b9 [drm] Jun 22 06:36:50 BlackBox kernel: radeon_pci_probe+0xc8/0xf3 [radeon] Jun 22 06:36:50 BlackBox kernel: local_pci_probe+0x44/0x85 Jun 22 06:36:50 BlackBox kernel: pci_device_probe+0x145/0x197 Jun 22 06:36:50 BlackBox kernel: really_probe+0x11e/0x2e8 Jun 22 06:36:50 BlackBox kernel: __driver_probe_device+0x91/0xc0 Jun 22 06:36:50 BlackBox kernel: driver_probe_device+0x1e/0x73 Jun 22 06:36:50 BlackBox kernel: __device_attach_driver+0x76/0x85 Jun 22 06:36:50 BlackBox kernel: ? driver_allows_async_probing+0x45/0x45 Jun 22 06:36:50 BlackBox kernel: bus_for_each_drv+0x8a/0xb0 Jun 22 06:36:50 BlackBox kernel: __device_attach+0xba/0x132 Jun 22 06:36:50 BlackBox kernel: bus_rescan_devices_helper+0x3a/0x65 Jun 22 06:36:50 BlackBox kernel: drivers_probe_store+0x34/0x4c Jun 22 06:36:50 BlackBox kernel: kernfs_fop_write_iter+0x126/0x152 Jun 22 06:36:50 BlackBox kernel: new_sync_write+0x7f/0xb7 Jun 22 06:36:50 BlackBox kernel: vfs_write+0xd9/0x124 Jun 22 06:36:50 BlackBox kernel: ksys_write+0x76/0xbe Jun 22 06:36:50 BlackBox kernel: do_syscall_64+0x83/0xa5 Jun 22 06:36:50 BlackBox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jun 22 06:36:50 BlackBox kernel: RIP: 0033:0x14b009c5b4df Jun 22 06:36:50 BlackBox kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 89 b8 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 dc b8 f8 ff 48 Jun 22 06:36:50 BlackBox kernel: RSP: 002b:000014b0084e6610 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Jun 22 06:36:50 BlackBox kernel: RAX: ffffffffffffffda RBX: 000000000000000c RCX: 000014b009c5b4df Jun 22 06:36:50 BlackBox kernel: RDX: 000000000000000c RSI: 000014afb41afac0 RDI: 0000000000000029 Jun 22 06:36:50 BlackBox kernel: RBP: 000014afb41afac0 R08: 0000000000000000 R09: 000014affc0063e0 Jun 22 06:36:50 BlackBox kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000029 Jun 22 06:36:50 BlackBox kernel: R13: 0000000000000029 R14: 0000000000000000 R15: 000014b00a3dcbb0 Jun 22 06:36:50 BlackBox kernel: </TASK> Jun 22 06:36:50 BlackBox kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod amdgpu gpu_sched it87 hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel radeon kvm ast drm_vram_helper drm_ttm_helper ttm crct10dif_pclmul ipmi_ssif crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd drm_kms_helper rapl intel_cstate drm mpt3sas intel_uncore ahci i2c_i801 raid_class input_leds i2c_smbus scsi_transport_sas i2c_algo_bit led_class libahci intel_pch_thermal acpi_ipmi agpgart video i2c_core ipmi_si backlight Jun 22 06:36:50 BlackBox kernel: syscopyarea sysfillrect sysimgblt fb_sys_fops button thermal fan [last unloaded: igb] Jun 22 06:36:50 BlackBox kernel: CR2: 0000000000000194 Jun 22 06:36:50 BlackBox kernel: ---[ end trace 123781c430b71e14 ]--- Jun 22 06:36:50 BlackBox kernel: RIP: 0010:fbcon_del_cursor_timer+0x1a/0x39 Jun 22 06:36:50 BlackBox kernel: Code: 5e e9 cd e7 c3 ff 58 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 44 00 00 48 81 bf e8 01 00 00 74 14 47 81 75 26 53 48 8b 9f 40 03 00 00 <f6> 83 94 01 00 00 02 74 13 48 8d bb d8 00 00 00 e8 9f f9 c5 ff 83 Jun 22 06:36:50 BlackBox kernel: RSP: 0018:ffffc900019379a8 EFLAGS: 00010246 Jun 22 06:36:50 BlackBox kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Jun 22 06:36:50 BlackBox kernel: RDX: 000000000000003e RSI: 0000000000000000 RDI: ffff888105baf800 Jun 22 06:36:50 BlackBox kernel: RBP: ffff88868521d000 R08: 0000000000000001 R09: 0000000000000001 Jun 22 06:36:50 BlackBox kernel: R10: 0000000000aaaaaa R11: ffffc900077d8420 R12: 000000000000003e Jun 22 06:36:50 BlackBox kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000 Jun 22 06:36:50 BlackBox kernel: FS: 000014b0084e7640(0000) GS:ffff88885fd40000(0000) knlGS:0000000000000000 Jun 22 06:36:50 BlackBox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 22 06:36:50 BlackBox kernel: CR2: 0000000000000194 CR3: 00000001a2132005 CR4: 00000000003726e0 But unfortunately I don't know how to fix it...

What about the fractal design 7 xl? I have an old fractal design xl r2 and it was near perfect. The new 7 xl is quite expensive (at least for me), but it seems it has all one should have need; it has also a 3 vertical slot space to install a pcie riser.

I'm continuing to follow this, don't worry I don't forget. As soon as unraid will be out with something different for virtualization (and/or libvirt and/or qemu) I will test it and let you know. But for now...it's bugged...

1. bind to vfio at boot iommu group 16 (Tools -> System Devices) 2. enable allow unsafe interrupts (Settings -> VM) 3. Setup the gpu passthrough for your vm and remove vnc+qxl graphics: if you use the gui, passthrough the video, do not passthrough the audio (you will pass it manually in step 4 below) 4. Once you setup the video passthrough, switch to xml view (top tight), you will find a block similar to this: <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='0x00' slot='0x05' function='0x0'/> </hostdev> What could change is the target address (00:05.0), i.e. this line: <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> Replace the first whole block with this: <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='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x3'/> </hostdev> NOTE: if your target address is different than 00:05.0 (bus:slot.function), replace all the addresses accordingly. 5. Save, reboot and try

Download again the iso, it seems corrupted, check its hash at the end of download. Issue similar to this: https://forums.unraid.net/topic/124980-hp-z230-cant-get-win10-vm-booting-to-installer-ubuntu-vm-works-fine/

Attach diagnostics

Try to download again the windows 10 iso and/or check its hash to see if it's corrupted.

No, no, these 2 commands: echo 1 > /sys/bus/pci/devices/0000\:06\:00.0/remove echo 1 > /sys/bus/pci/rescan for a gpu located at bus 6, slot 0, function 0 in the host; this will power cycle the gpu "on the fly".

If you are pressing a key when prompted, and I believe you are pressing it without nothing happening, I suspect the issue is that the boot is not detecting your keyboard. How are you passing through the keyboard?Check the xml and see if you have the keyboard block type ps2 and/or the emulated usb controller with your usb keyboard passed through or the real usb controller with a keyboard attached. If you use vnc I think you need a keyboard block defined. Compare the 2 xml (win10 win11) and see if there's something different about the keyboard.

Sometimes if you have input/output error when dumping the rom, even if it's apparently not in use by the host and isolated (seen a lot of times in other builds), it helps removing the pci device and rescan for it, then the vbios dump could work as expected. Anyway you got good luck with a third party vbios.

sorry but, which prompt? It seems this is a boot from a corrupted vdisk and not from the iso dvd, is your vdisk empty? When you boot the vm does the keyboard work in ovmf?

You explained a lot of things, some contraddicting. ?? ?? and.... I read the whole discussion and I spent some of my time, if I write something I write it because I think it can solve the issue or point to its resolution, but if you think I'm not reading or understanding, well, stay with your issue and get help from someone else, n.p., one thread less to follow