Running Proxmox 8.0.4 and attempting to install a Windows 7 VM (don't ask why, old software needs it). Original Windows 7 install worked well and was able to install SP1 with no problem. When adding the semi-official SP2 update (see here) I observed a VM "Status: internal-error" warning in the GUI. Looking at the system log I see the following error for the VM:
Oct 18 14:29:19 megatron pvedaemon[66263]: resume VM 200: UPID:megatron:000102D7:000525C4:65304E2F:qmresume:200:root@pam:
Oct 18 14:29:19 megatron systemd[1]: Started 200.scope.
Oct 18 14:29:19 megatron kernel: device tap200i0 entered promiscuous mode
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered disabled state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered forwarding state
Oct 18 14:29:26 megatron QEMU[66274]: KVM: entry failed, hardware error 0x80000021
Oct 18 14:29:26 megatron QEMU[66274]: If you're running a guest on an Intel machine without unrestricted mode
Oct 18 14:29:26 megatron QEMU[66274]: support, the failure can be most likely due to the guest entering an invalid
Oct 18 14:29:26 megatron QEMU[66274]: state for Intel VT. For example, the guest maybe running in big real mode
Oct 18 14:29:26 megatron QEMU[66274]: which is not supported on less recent Intel processors.
Oct 18 14:29:26 megatron QEMU[66274]: RAX=0000000000000000 RBX=0000000000000000 RCX=0000000040000070 RDX=0000000000000000
Oct 18 14:29:26 megatron QEMU[66274]: RSI=fffffa800e40c010 RDI=fffffa8007eca010 RBP=fffff8800332b3e0 RSP=fffff8800332b338
Oct 18 14:29:26 megatron QEMU[66274]: R8 =fffffa8006d0eb30 R9 =0000000000000000 R10=fffffa8006e098e0 R11=fffffa8010c93c60
Oct 18 14:29:26 megatron QEMU[66274]: R12=0000000000000056 R13=fffffa8006e0a640 R14=fffffa8007c13ab0 R15=fffff8800332b6c0
Oct 18 14:29:26 megatron QEMU[66274]: RIP=fffff8000271722c RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
Oct 18 14:29:26 megatron QEMU[66274]: ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
Oct 18 14:29:26 megatron QEMU[66274]: SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: FS =0053 00000000fffd6000 0000fc00 0040f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: GS =002b fffff88003121000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: LDT=0000 0000000000000000 ffffffff 00c00000
Oct 18 14:29:26 megatron QEMU[66274]: TR =0040 fffff88003125f40 00000067 00008b00 DPL=0 TSS64-busy
Oct 18 14:29:26 megatron QEMU[66274]: GDT= fffff8800312c540 0000007f
Oct 18 14:29:26 megatron QEMU[66274]: IDT= fffff8800312c5c0 00000fff
Oct 18 14:29:26 megatron QEMU[66274]: CR0=80050031 CR2=fffff900c212e000 CR3=0000000000187000 CR4=000006f8
Oct 18 14:29:26 megatron QEMU[66274]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Oct 18 14:29:26 megatron QEMU[66274]: DR6=00000000ffff0ff0 DR7=0000000000000400
Oct 18 14:29:26 megatron QEMU[66274]: EFER=0000000000000d01
Oct 18 14:29:26 megatron QEMU[66274]: Code=25 a8 4b 00 00 b9 70 00 00 40 0f ba 32 00 72 06 33 c0 8b d0 <0f> 30 5a 58 59 c3 90 90 90 90 90 90 90 90 90 90 90 90 90 90 cc cc cc cc cc cc 66 66 0f 1f
Oct 18 14:29:26 megatron kernel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
Oct 18 14:29:26 megatron pvestatd[1899]: status update time (5.481 seconds)
I've seen mention of this error in the forums for Proxmox 7 but I have a newer install which shouldn't have the same issue, though I've yet to try the original workaround. Any suggestions? Maybe a different VCPU would be more appropriate?
Oct 18 14:29:19 megatron pvedaemon[66263]: resume VM 200: UPID:megatron:000102D7:000525C4:65304E2F:qmresume:200:root@pam:
Oct 18 14:29:19 megatron systemd[1]: Started 200.scope.
Oct 18 14:29:19 megatron kernel: device tap200i0 entered promiscuous mode
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered disabled state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 18 14:29:19 megatron kernel: vmbr0: port 4(tap200i0) entered forwarding state
Oct 18 14:29:26 megatron QEMU[66274]: KVM: entry failed, hardware error 0x80000021
Oct 18 14:29:26 megatron QEMU[66274]: If you're running a guest on an Intel machine without unrestricted mode
Oct 18 14:29:26 megatron QEMU[66274]: support, the failure can be most likely due to the guest entering an invalid
Oct 18 14:29:26 megatron QEMU[66274]: state for Intel VT. For example, the guest maybe running in big real mode
Oct 18 14:29:26 megatron QEMU[66274]: which is not supported on less recent Intel processors.
Oct 18 14:29:26 megatron QEMU[66274]: RAX=0000000000000000 RBX=0000000000000000 RCX=0000000040000070 RDX=0000000000000000
Oct 18 14:29:26 megatron QEMU[66274]: RSI=fffffa800e40c010 RDI=fffffa8007eca010 RBP=fffff8800332b3e0 RSP=fffff8800332b338
Oct 18 14:29:26 megatron QEMU[66274]: R8 =fffffa8006d0eb30 R9 =0000000000000000 R10=fffffa8006e098e0 R11=fffffa8010c93c60
Oct 18 14:29:26 megatron QEMU[66274]: R12=0000000000000056 R13=fffffa8006e0a640 R14=fffffa8007c13ab0 R15=fffff8800332b6c0
Oct 18 14:29:26 megatron QEMU[66274]: RIP=fffff8000271722c RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
Oct 18 14:29:26 megatron QEMU[66274]: ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
Oct 18 14:29:26 megatron QEMU[66274]: SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: FS =0053 00000000fffd6000 0000fc00 0040f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: GS =002b fffff88003121000 ffffffff 00c0f300 DPL=3 DS [-WA]
Oct 18 14:29:26 megatron QEMU[66274]: LDT=0000 0000000000000000 ffffffff 00c00000
Oct 18 14:29:26 megatron QEMU[66274]: TR =0040 fffff88003125f40 00000067 00008b00 DPL=0 TSS64-busy
Oct 18 14:29:26 megatron QEMU[66274]: GDT= fffff8800312c540 0000007f
Oct 18 14:29:26 megatron QEMU[66274]: IDT= fffff8800312c5c0 00000fff
Oct 18 14:29:26 megatron QEMU[66274]: CR0=80050031 CR2=fffff900c212e000 CR3=0000000000187000 CR4=000006f8
Oct 18 14:29:26 megatron QEMU[66274]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Oct 18 14:29:26 megatron QEMU[66274]: DR6=00000000ffff0ff0 DR7=0000000000000400
Oct 18 14:29:26 megatron QEMU[66274]: EFER=0000000000000d01
Oct 18 14:29:26 megatron QEMU[66274]: Code=25 a8 4b 00 00 b9 70 00 00 40 0f ba 32 00 72 06 33 c0 8b d0 <0f> 30 5a 58 59 c3 90 90 90 90 90 90 90 90 90 90 90 90 90 90 cc cc cc cc cc cc 66 66 0f 1f
Oct 18 14:29:26 megatron kernel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
Oct 18 14:29:26 megatron pvestatd[1899]: status update time (5.481 seconds)
I've seen mention of this error in the forums for Proxmox 7 but I have a newer install which shouldn't have the same issue, though I've yet to try the original workaround. Any suggestions? Maybe a different VCPU would be more appropriate?