[SOLVED] Having Issues w/ Win 10 and Host CPU Type

[TrendMend]

Good Day,

First off, I'd like to say how much I've enjoyed PVE over closed-source competitors, such as ESXi - Everything that has worked, has worked extremely well. I've been facing an issue throughout my transition though - I virtualized my physical Windows OS that's been operating on the same server with the goal of GPU pass-thru as my main workstation, but whenever I attempt to transition from KVM64 to my host CPU, windows refuses to boot. I am perfectly able to get into safe-mode, but no luck finding the cause. When booting, the display will freeze and PVE will through out an "internal-error", with little information in the syslog, and the bootlog even less. I've attempted to compare the working and crashing bootlog, but the differences were so major that I couldn't pick anything out.

I've also attempted to repair it using the installation media, with no luck. Nothing I've done has helped, and I don't really know what to do anymore. Thoughts on the steps from here? Thanks.

Config:

# args%3A -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off,-amd-stibp'
agent: 1
bios: ovmf
boot: order=ide0;ide2
cores: 4
cpu: host
efidisk0: local-lvm:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-100-disk-0,size=469276M
ide2: local:iso/Win10_21H1_English_x64.iso,media=cdrom,size=5687620K
machine: pc-q35-6.0
memory: 8096
name: Win10
net0: virtio=1A:47:06:30:CE:26,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=450f98d4-caab-4569-87d7-d9e8e5cfe781
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
vga: std
vmgenid: b211d045-a36e-4fc8-bef7-0e7188a6a917

Syslog:

Oct 14 13:46:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 14 13:46:01 pve systemd[1]: Finished Proxmox VE replication runner.
Oct 14 13:46:01 pve systemd[1]: pvesr.service: Consumed 1.031s CPU time.
Oct 14 13:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 14 13:47:00 pve systemd[1]: pvesr.service: Succeeded.
Oct 14 13:47:00 pve systemd[1]: Finished Proxmox VE replication runner.
Oct 14 13:47:08 pve pvedaemon[72738]: worker exit
Oct 14 13:47:08 pve pvedaemon[1033]: worker 72738 finished
Oct 14 13:47:08 pve pvedaemon[1033]: starting 1 worker(s)
Oct 14 13:47:08 pve pvedaemon[1033]: worker 81168 started
Oct 14 13:47:11 pve QEMU[80895]: KVM internal error. Suberror: 1
Oct 14 13:47:11 pve QEMU[80895]: emulation failure
Oct 14 13:47:11 pve QEMU[80895]: KVM internal error. Suberror: 1
Oct 14 13:47:11 pve QEMU[80895]: emulation failure
Oct 14 13:47:11 pve QEMU[80895]: EAX=00000000 EBX=00000003 ECX=00000003 EDX=00000000
Oct 14 13:47:11 pve QEMU[80895]: ESI=00000000 EDI=7ffc4000 EBP=22c05f00 ESP=7ffc4ff8
Oct 14 13:47:11 pve QEMU[80895]: EIP=7ffcc28f EFL=00033002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
Oct 14 13:47:11 pve QEMU[80895]: ES =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: CS =0000 00000000 00000fff 0080f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: SS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: DS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: FS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: GS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
Oct 14 13:47:11 pve QEMU[80895]: TR =0040 feffd000 00002088 00008b00 DPL=0 TSS64-busy
Oct 14 13:47:11 pve QEMU[80895]: GDT=     000000007ff66228 0000004f
Oct 14 13:47:11 pve QEMU[80895]: IDT=     000000007ffac000 000001ff
Oct 14 13:47:11 pve QEMU[80895]: CR0=80050033 CR2=0000000000000000 CR3=000000007ffa3000 CR4=00002e78
Oct 14 13:47:11 pve QEMU[80895]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Oct 14 13:47:11 pve QEMU[80895]: DR6=00000000ffff0ff0 DR7=0000000000000400
Oct 14 13:47:11 pve QEMU[80895]: EFER=0000000000000500
Oct 14 13:47:11 pve QEMU[80895]: Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
Oct 14 13:47:11 pve QEMU[80895]: EAX=00000000 EBX=00000001 ECX=00000001 EDX=00000000
Oct 14 13:47:11 pve QEMU[80895]: ESI=f7475980 EDI=7ffc0000 EBP=22cc1d08 ESP=7ffb8ff8
Oct 14 13:47:11 pve QEMU[80895]: EIP=7ffc828f EFL=00033002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
Oct 14 13:47:11 pve QEMU[80895]: ES =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: CS =0000 00000000 00000fff 0080f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: SS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: DS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: FS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: GS =0020 00000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Oct 14 13:47:11 pve QEMU[80895]: LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
Oct 14 13:47:11 pve QEMU[80895]: TR =0040 feffd000 00002088 00008b00 DPL=0 TSS64-busy
Oct 14 13:47:11 pve QEMU[80895]: GDT=     000000007ff660b8 0000004f
Oct 14 13:47:11 pve QEMU[80895]: IDT=     000000007ffac000 000001ff
Oct 14 13:47:11 pve QEMU[80895]: CR0=80050033 CR2=0000000000000000 CR3=000000007ffa3000 CR4=00002e78
Oct 14 13:47:11 pve QEMU[80895]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Oct 14 13:47:11 pve QEMU[80895]: DR6=00000000ffff0ff0 DR7=0000000000000400
Oct 14 13:47:11 pve QEMU[80895]: EFER=0000000000000500
Oct 14 13:47:11 pve QEMU[80895]: Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

 

[aaron]

What CPU do you have in that machine?

 

[TrendMend]

What CPU do you have in that machine?

I have an Intel Xeon E5520 installed. Ended up solving the problem by reinstalling Proxmox - I think the package repository definitely played a part (I believe I misconfigured it) as well as choosing an incorrect bus type for the drive image. For anyone experiencing the same issue, I encourage you to try a few different bus types or a whole reinstall (if possible). I'll mark it as solved. Thank you.