OVMF/Q35 Windows 10 won't boot (no bios post)

H

HDmac

New Member
May 30, 2022
13
1
3
I'm trying to create a fresh windows 10 VM. This is on a clean proxmox 7.2 install. If I select SeaBIOS/Q35 OR OVMF/i440fx the machine will boot. If I select OVMF/Q35 (for gpu passthrough) the VM won't boot and displays "Guest has not initialized the display yet".


1654036928410.png
1654036951618.png
 
Hi,

do you mean the windows install cd/iso doesn't boot or your installation when you change the settings?
 
Your "Boot order" in options a bit empty mine looks like this.

1654089646932.png
Can you maybe select something there?
 
Probably because i've been messing with it. I have it set to the cd/iso now though, boots fine when i select something other than ovmf/q35
 
Here's the output when starting the VM:

Code: 
Jun  2 10:21:48 pve QEMU[248732]: kvm: terminating on signal 15 from pid 734 (/usr/sbin/qmeventd)
Jun  2 10:21:48 pve kernel: [91236.322754]  sdd: sdd1 sdd2 sdd3 sdd4
Jun  2 10:21:48 pve kernel: [91236.401136] fwbr100i0: port 2(tap100i0) entered disabled state
Jun  2 10:21:48 pve kernel: [91236.441883] fwbr100i0: port 1(fwln100i0) entered disabled state
Jun  2 10:21:48 pve kernel: [91236.441906] vmbr0: port 3(fwpr100p0) entered disabled state
Jun  2 10:21:48 pve kernel: [91236.442085] device fwln100i0 left promiscuous mode
Jun  2 10:21:48 pve kernel: [91236.442087] fwbr100i0: port 1(fwln100i0) entered disabled state
Jun  2 10:21:48 pve kernel: [91236.464532] device fwpr100p0 left promiscuous mode
Jun  2 10:21:48 pve kernel: [91236.464533] vmbr0: port 3(fwpr100p0) entered disabled state
Jun  2 10:21:48 pve pvedaemon[29932]: VM 100 qmp command failed - unable to open monitor socket
Jun  2 10:21:48 pve pvedaemon[31196]: <root@pam> end task UPID:pve:0003CC0F:008B28B0:6298C759:vncproxy:100:root@pam: OK
Jun  2 10:21:48 pve systemd[1]: 100.scope: Succeeded.
Jun  2 10:21:48 pve systemd[1]: 100.scope: Consumed 4min 36.947s CPU time.
Jun  2 10:21:49 pve qmeventd[249000]: Starting cleanup for 100
Jun  2 10:21:49 pve qmeventd[249000]: Finished cleanup for 100
Jun  2 10:22:00 pve pvedaemon[29932]: <root@pam> update VM 100: -machine pc-q35-6.2
Jun  2 10:22:07 pve pvedaemon[29932]: <root@pam> starting task UPID:pve:0003CCE0:008B3DE6:6298C78F:qmstart:100:root@pam:
Jun  2 10:22:07 pve pvedaemon[249056]: start VM 100: UPID:pve:0003CCE0:008B3DE6:6298C78F:qmstart:100:root@pam:
Jun  2 10:22:07 pve systemd[1]: Started 100.scope.
Jun  2 10:22:07 pve systemd-udevd[249073]: Using default interface naming scheme 'v247'.
Jun  2 10:22:07 pve systemd-udevd[249073]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 10:22:08 pve kernel: [91255.943163] device tap100i0 entered promiscuous mode
Jun  2 10:22:08 pve systemd-udevd[249073]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 10:22:08 pve systemd-udevd[249073]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 10:22:08 pve systemd-udevd[249076]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  2 10:22:08 pve systemd-udevd[249076]: Using default interface naming scheme 'v247'.
Jun  2 10:22:08 pve kernel: [91255.963391] vmbr0: port 3(fwpr100p0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.963394] vmbr0: port 3(fwpr100p0) entered disabled state
Jun  2 10:22:08 pve kernel: [91255.963434] device fwpr100p0 entered promiscuous mode
Jun  2 10:22:08 pve kernel: [91255.963455] vmbr0: port 3(fwpr100p0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.963456] vmbr0: port 3(fwpr100p0) entered forwarding state
Jun  2 10:22:08 pve kernel: [91255.965967] fwbr100i0: port 1(fwln100i0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.965969] fwbr100i0: port 1(fwln100i0) entered disabled state
Jun  2 10:22:08 pve kernel: [91255.966001] device fwln100i0 entered promiscuous mode
Jun  2 10:22:08 pve kernel: [91255.966018] fwbr100i0: port 1(fwln100i0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.966019] fwbr100i0: port 1(fwln100i0) entered forwarding state
Jun  2 10:22:08 pve kernel: [91255.968138] fwbr100i0: port 2(tap100i0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.968140] fwbr100i0: port 2(tap100i0) entered disabled state
Jun  2 10:22:08 pve kernel: [91255.968183] fwbr100i0: port 2(tap100i0) entered blocking state
Jun  2 10:22:08 pve kernel: [91255.968184] fwbr100i0: port 2(tap100i0) entered forwarding state
Jun  2 10:22:08 pve pvedaemon[29932]: <root@pam> end task UPID:pve:0003CCE0:008B3DE6:6298C78F:qmstart:100:root@pam: OK
Jun  2 10:22:08 pve pvedaemon[31196]: <root@pam> starting task UPID:pve:0003CD43:008B3E34:6298C790:vncproxy:100:root@pam:

I don't see anything different when I switch it from i440fx and successfully boot except it just hangs on that last line of 'starting task'
 
Can you try changing the version of Machine from 6.2 to something else?
 
Can you show me the storage config /etc/pve/storage.conf? I'm curious about the windows-gaming* parts.
 
It's just iscsi targets.

Code: 
iscsi: windows-gaming-os
        portal 10.0.0.2
        target iqn.2005-10.org.freenas.ctl:windows-gaming
        content images

iscsi: windows-gaming-efi
        portal 10.0.0.2
        target iqn.2005-10.org.freenas.ctl:windows-gaming-efi
        content images
 
Ok, figured it out. Your question got me thinking so I set the EFI disk to local rather than iscsi and its working. Thank you!
 
  • Like
Reactions: shrdlicka
Just wanted to suggest moving the disks to local storage :), awesome that it works now.
 
shrdlicka said:
Just wanted to suggest moving the disks to local storage :), awesome that it works now.
Click to expand...
hey, i got the same issue! the thing here is that i dont want to change the disk to the local one(hdd) because i have a secondary disk(ssd) where i want the win vm.

Greetings!
 
You must log in or register to reply here.
Top Bottom