June 30, 20224 yr Keep running into a problem with a windows 7 VM. As the title says, the VM completely locks up a few minutes after booting, I can VNC into the machine, but everything is just locked up and I have to hard reset. Any thoughts on what is causing this and/or how to resolve? diganostics removed This is also in the VM log: qxl_send_events: spice-server bug: guest stopped, ignoring KVM internal error. Suberror: 3 extra data[0]: 0x000000008000002f extra data[1]: 0x0000000000000020 extra data[2]: 0x00000000000005aa extra data[3]: 0x0000000000000004 RAX=0000000000000000 RBX=fffffa800053f880 RCX=0000000040000070 RDX=0000000000000000 RSI=000000000001bfd8 RDI=0000000000000002 RBP=fffff880009ae9c0 RSP=fffff880009ae918 R8 =0000000000000001 R9 =0000000000000000 R10=fffffa8003c021e0 R11=fffff880009aeaa0 R12=0000000000000000 R13=0000000000000000 R14=0000058000000000 R15=fffffa8000566850 RIP=fffff800026e422c RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 00000000fff9a000 00003c00 0040f300 DPL=3 DS [-WA] GS =002b fffff8000280ad00 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 fffff80000b96080 00000067 00008b00 DPL=0 TSS64-busy GDT= fffff80000b95000 0000007f IDT= fffff80000b95080 00000fff CR0=80050031 CR2=0000000001dedcf0 CR3=0000000000187000 CR4=000406f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 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 Edited July 1, 20224 yr by derek_zoolander
July 1, 20224 yr Author Solution For anyone having a similar issue. I am on Alderlake - I was passing hyperthreaded cores to the VM. It appears that only passing main cores has resolved this issue. Posting in case anyone else searching for a solution stumbles here
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.