Got similar behavior with windows server 2012r2 VMs.
Environment:
uname -a Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 amd64 Linux kernel image for version 4.13.0 on 64 bit x86 SMP
apt policy qemu qemu: Installed: (none) Candidate: 1:2.11+dfsg-1ubuntu5~cloud0 Version table: 1:2.11+dfsg-1ubuntu5~cloud0 500
Windows VMs error out and create a memory dump:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a01f5891f186c5, 0xb3b72bdee47188a0, 0x0000032000000000, 0x0000000000000017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 033018-31234-01.
Based on microsoft docs:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x109---critical-structure-corruption CRITICAL_STRUCTURE_CORRUPTION Parameters Parameter Description 1 Reserved 2 Reserved 3 Reserved 4 The type of the corrupted region. (See the following table later on this page.)
... 0x17 Local APIC modification <--- this
Which is the same as with other reports out there:
https://www.spinics.net/lists/kvm/msg159977.html https://forum.proxmox.com/threads/new-windows-vm-keeps-dying.39145/#post-193639
From what I see the change was backported but there was no new build yet.
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/arch/x86/kvm/x86.c?h=hwe&id=78d2542b88d16
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738972
I suggest this is marked as a duplicate to 1738972
Got similar behavior with windows server 2012r2 VMs.
Environment:
uname -a
Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image- 4.13.0- 36-generic 4.13.0- 36.40~16. 04.1 amd64 Linux kernel image for version 4.13.0 on 64 bit x86 SMP
apt policy qemu dfsg-1ubuntu5~ cloud0 2.11+dfsg- 1ubuntu5~ cloud0 500
qemu:
Installed: (none)
Candidate: 1:2.11+
Version table:
1:
Windows VMs error out and create a memory dump:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a01f5891f1 86c5, 0xb3b72bdee47188a0, 0x0000032000000000, 0x0000000000000 017). A dump was saved in: C:\Windows\ MEMORY. DMP. Report Id: 033018-31234-01.
Based on microsoft docs:
https:/ /docs.microsoft .com/en- us/windows- hardware/ drivers/ debugger/ bug-check- 0x109-- -critical- structure- corruption STRUCTURE_ CORRUPTION Parameters
CRITICAL_
Parameter Description
1 Reserved
2 Reserved
3 Reserved
4 The type of the corrupted region. (See the following table later on this page.)
...
0x17 Local APIC modification <--- this
Which is the same as with other reports out there:
https:/ /www.spinics. net/lists/ kvm/msg159977. html /forum. proxmox. com/threads/ new-windows- vm-keeps- dying.39145/ #post-193639
https:/
From what I see the change was backported but there was no new build yet.
http:// kernel. ubuntu. com/git/ ubuntu/ ubuntu- xenial. git/commit/ arch/x86/ kvm/x86. c?h=hwe& id=78d2542b88d1 6
See https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1738972
I suggest this is marked as a duplicate to 1738972