anony Posted December 10, 2020 Share Posted December 10, 2020 (edited) Version: 6.9.0-beta35 Tried latest stable too. CPU: Ryzen 9 5900x Motherboard: ASUS X570 Hero Wifi BIOS version: 3003 (latest) https://rog.asus.com/motherboards/rog-crosshair/rog-crosshair-viii-hero-wi-fi-model/helpdesk_bios/ I run two VMs on my machine. A Windows 10 system and an ubuntu system. They both use the OVMF BIOS with Q35. Recently I decided to update my motherboard bios to from 2702 to 3003 as it was recently released. After updating, I cannot get my Windows 10 VM to display. After booting the screen goes blank with nothing after. I cannot find any errors in the logs either. My ubuntu VM works completely fine and boots no problem. I have tried the fx bios which also doesn't work. Only SeaBIOS works now - I dont like SeaBIOS; it requires me to reinstall windows since I cant seem to boot from my past OVMF version of Windows 10. I have tried disabling hyperv and messing with bios settings (default) but no luck! I cannot downgrade the motherboard BIOS either. I have also tried re-creating the VM numerous times. Including booting off UEFI version of unraid. What else should I provide? Logs of Windows 10 VM on OVMF -m 30208 \ -overcommit mem-lock=off \ -smp 12,sockets=1,dies=1,cores=6,threads=2 \ -uuid 269b9d68-44ba-e501-0878-d5d36b29911f \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=32,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \ -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_20H2_v2_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.189-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:1a:65:88,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=37,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/mnt/user/isos/gpubios.rom \ -device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-12-10 10:43:11.416+0000: Domain id=5 is tainted: high-privileges 2020-12-10 10:43:11.416+0000: Domain id=5 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) tower-diagnostics-20201210-0244.zip Edited December 10, 2020 by anony Quote Link to comment
rachid596 Posted December 10, 2020 Share Posted December 10, 2020 If you create a new vm it's not working too ? I have the Same motherboard and yesterday i want to install this bios now with your post i do not install it. Quote Link to comment
rachid596 Posted December 10, 2020 Share Posted December 10, 2020 You have flash back option in Asus bios Quote Link to comment
anony Posted December 10, 2020 Author Share Posted December 10, 2020 (edited) 8 minutes ago, rachid596 said: If you create a new vm it's not working too ? I have the Same motherboard and yesterday i want to install this bios now with your post i do not install it. Yes if I create a new VM it doesn't work. Thanks I forgot about BIOS flash back I will try that tomorrow to revert back to 2702. Edited December 10, 2020 by anony 1 Quote Link to comment
rachid596 Posted December 10, 2020 Share Posted December 10, 2020 Yes if I create a new VM it doesn't work. Thanks I forgot about BIOS flash back I will try that tomorrow to revert back to 2702.No problem Envoyé de mon HD1913 en utilisant Tapatalk 1 Quote Link to comment
anony Posted December 12, 2020 Author Share Posted December 12, 2020 (edited) I have downgraded the bios to 2702 with no luck. I have no idea why ubuntu works on both gpu's but windows 10 does not work at all yet windows 10 used to work. Im on my 6th hour trying to fix this - this is my 4th year running unraid and the one thing it had kept this entire time is how much of a pain in the ass it has been. 😀 Edited December 12, 2020 by anony Quote Link to comment
rachid596 Posted December 12, 2020 Share Posted December 12, 2020 I have downgraded the bios to 2702 with no luck. I have no idea why ubuntu works on both gpu's but windows 10 does not work at all yet windows 10 used to work. Im on my 6th hour trying to fix this - this is my 4th year running unraid and the one thing it had kept this entire time is how much of a pain in the ass it has been. Very strange problem. I can't help you sorry. Maybe try q35 machine type. Do you test with 6.9 rc1 ? Envoyé de mon HD1913 en utilisant Tapatalk Quote Link to comment
anony Posted December 12, 2020 Author Share Posted December 12, 2020 1 minute ago, rachid596 said: Very strange problem. I can't help you sorry. Maybe try q35 machine type. Do you test with 6.9 rc1 ? Envoyé de mon HD1913 en utilisant Tapatalk I tried with 6.9 rc1 yes and q35 : ( Quote Link to comment
anony Posted December 13, 2020 Author Share Posted December 13, 2020 I have discovered this error in the log now: 2020-12-13T01:19:05.191309Z qemu-system-x86_64: vfio: Cannot reset device 0000:0a:00.0, depends on group 32 which is not owned. 2020-12-13T01:19:05.191404Z qemu-system-x86_64: vfio: Cannot reset device 0000:0a:00.0, depends on group 32 which is not owned. Quote Link to comment
david279 Posted December 13, 2020 Share Posted December 13, 2020 Yeah you can't pass that device anymore. It's breaking things. Quote Link to comment
anony Posted December 16, 2020 Author Share Posted December 16, 2020 On 12/12/2020 at 10:51 PM, david279 said: Yeah you can't pass that device anymore. It's breaking things. Any idea why? Quote Link to comment
david279 Posted December 16, 2020 Share Posted December 16, 2020 It's might be in a group with other devices. Quote Link to comment
anony Posted December 16, 2020 Author Share Posted December 16, 2020 9 hours ago, david279 said: It's might be in a group with other devices. should beok Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.