Win10 updated, after reboot stuck

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
I installed Win10 Pro on the following machine:
root@proxmox:~# qm config 113
agent: 1
bios: ovmf
boot: c
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: FreeNAS:113/vm-113-disk-1.qcow2,size=128K
machine: q35
memory: 16384
name: Win10GPU
net0: e1000=8E:23:7B:B7:5F:50,bridge=vmbr3
numa: 0
ostype: win10
scsi0: FreeNAS:113/vm-113-disk-2.qcow2,size=128G
scsihw: virtio-scsi-pci
smbios1: uuid=a8e1f192-5e9c-4b1c-8504-828af214a06d
sockets: 1
spice_enhancements: videostreaming=all
vga: qxl
vmgenid: 47a10b13-fc04-4091-9146-a0b29a312786
root@proxmox:~# qm set 113
no options specified
root@proxmox:~# qm showcmd 113
/usr/bin/kvm -id 113 -name Win10GPU -chardev 'socket,id=qmp,path=/var/run/qemu-server/113.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/113.pid -daemonize -smbios 'type=1,uuid=a8e1f192-5e9c-4b1c-8504-828af214a06d' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=qcow2,id=drive-efidisk0,file=/mnt/pve/FreeNAS/images/113/vm-113-disk-1.qcow2' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/113.vnc,password -no-hpet -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi' -m 16384 -device 'vmgenid,guid=47a10b13-fc04-4091-9146-a0b29a312786' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'qxl-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/113.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61001,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on,streaming-video=all' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:4015b590b4ce' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/mnt/pve/FreeNAS/images/113/vm-113-disk-2.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap113i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=8E:23:7B:B7:5F:50,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35+pve1' -global 'kvm-pit.lost_tick_policy=discard'
root@proxmox:~#
And once it was updated to the latest version of Windows 10, it simply got stuck after reboot:

1590164116419.png
I've tried switching to sata and ide with no luck. I've changed the machine from q35 to i440fx. It just shows this screen and gets stuck. CTRL-ALT-DEL won't do anything either, only full on brute force will restart or shut it down.

The version of PVE is:
root@proxmox:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 1.2.5-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
No errors shown in console or syslog/dmesg
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Tried reinstalling this time using VirtIO instead of Virt SCSI. All seemed to go well except it wouldn't automatically boot windows, I had to launch fs0:\efi\boot\bootx64.efi (or similar) from the UEFI shell. After a few sessions of that, I shut down the VM completely and started it again.

Now FS0: is gone

Shutdown again and changed it into SATA and set options to boot from it. Started again, and now I have the same error as above.

Is it impossible to run Win10 Pro 64bit ??? Seems like I'm either missing a setting or win10 is no longer supported (unlikely ;-) )
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
I've tried Virt SCSI, Virt IO and now on SATA ... Iso is straight from MS themselves and I've used it multiple times with VMWare Workstation and real computers. So I think I'm just doing something wrong with Proxmox. I'll let you know in 10-20min what the result is this time. Key to trigger it seems to be to power down the virtual machine.
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
162
16
18
Hmmm, ok try to update your packages apt update && apt full-upgrade your packages should to be up to date especially qemu packages

pve-qemu-kvm_5.0.0-2_amd64.deb


I hope this helps :)
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
First reboot after installing to SATA lands me in UEFI and I have to launch the EFI loader myself. Shutdown followed by power on and my boot drive is gone again.
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
A
Hmmm, ok try to update your packages apt update && apt full-upgrade your packages should to be up to date especially qemu packages

pve-qemu-kvm_5.0.0-2_amd64.deb


I hope this helps :)
Already tried :( made no difference. It's as if the boot sector on the virtual drive cannot be written or something. Only Win10 that I have working is an image I imported from a VMWare ESXi system
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
(and I've compared notes and see nothing different)

This is my current setup which failed after the first reboot
1590182051773.png
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Well, actually, I used i440fx on the working one and here I use q35 because I need passthru working
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Third try since last post...
1590183355304.png
Same result. Last thing to try is non-UEFI which defeats this purpose but now I'm curious.

I'm deleting EFI and system drive between runs.
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Nope, while SeaBIOS will let the machine do the complete install with reboots in-between, once you shut it down, the next boot will blue screen. Starting it again seems to work.

Some more testing shows that any time I do a graceful shutdown, the machine will BSOD on next power up:
1590184179284.png
Once it has BSOD, the next boot will work.

This is hopeless. I guess vmware does some magic to the harddrive image which makes it work.
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Something is very odd, I have made tweaks to the GRUB command line to enable GPU passthru and since then, the only CPU I can chose is the "host" option. All other options yield

kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
kvm: Host doesn't support requested features

Maybe this is related?
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Was using:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1

Will try:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"

But not until later tonight when I can reboot the host :)
 

TheMrWorf

New Member
Feb 25, 2020
14
0
1
43
Last run I did I deleted my old VM, followed the tutorial to the best of my abilities (given that my proxmox is newer) and I still ended up with a BSOD after clean shutdown. Same error, HAL_INITIALIZATION_FAILED.

After reset, I'm now stuck (again) where I started the thread:
1590452198859.png

Could this be related to me running an AMD EPYC 7452 32-Core Processor (Rome) ? Has anyone tried this?

Grub config is:
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"
(since I mentioned that I messed with this before).

Vm config is:
agent: 1
bios: ovmf
bootdisk: scsi0
cores: 4
efidisk0: FreeNAS:112/vm-112-disk-1.qcow2,size=128K
ide0: FreeNAS:iso/virtio-win-0.1.173.iso,media=cdrom,size=385322K
ide2: FreeNAS:iso/Windows10Pro-64bit.iso,media=cdrom
machine: q35
memory: 16384
name: win10gpu
net0: virtio=36:80:14:1B:0A:BF,bridge=vmbr3,firewall=1
numa: 0
ostype: win10
scsi0: FreeNAS:112/vm-112-disk-0.qcow2,cache=writeback,discard=on,size=128G
scsihw: virtio-scsi-pci
smbios1: uuid=41242767-108e-4626-bbe3-5ee1e47a3fb3
sockets: 1
vmgenid: c89dad09-8d55-4459-af1a-1440e15b4d79

Any clue would help

Also, interestingly enough, I have a VM from my old ESXi setup which I converted and it runs just fine. Here's the vm config:
agent: 1
balloon: 0
bios: ovmf
bootdisk: sata0
cores: 2
cpu: host
efidisk0: FreeNAS:107/vm-107-disk-0.qcow2,size=128K
ide2: FreeNAS:iso/virtio-win-0.1.173.iso,media=cdrom,size=385322K
memory: 8192
name: PrintServer
net0: e1000=2E:A5:B0:1C:B9:6A,bridge=vmbr3
numa: 0
onboot: 1
ostype: win10
sata0: FreeNAS:107/vm-107-disk-0.vmdk,size=64G
smbios1: uuid=b608ca33-7ce0-4b89-9733-877c64c9f78b
sockets: 1
vmgenid: 9fcf60ab-64ad-4859-86ec-9b226fd61d2a

Now, of course, I've tried the same config and I always end up in the same place, HAL_INIT_FAILED and/or non-booting. The OS image is from MS's store and is the same used with ESXi earlier to create the PrintServer config.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!