[SOLVED] VM crashes at about the same time over and over again

BiggestPig

Member
Nov 18, 2021
2
0
6
24
Solved: Seems to be a general problem with some Intel CPUs. Just search for your CPU in the forum.

Hi,

I have a strange Problem where a OPNsense VM crashes every few days at about the same time.
The VM gets the internal-error state and is not reachable anymore. In the VM itself is no error visible.

pveversion -v:
Code:
proxmox-ve: 7.4-1 (running kernel: 5.15.104-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

qm config VMID:
Code:
agent: 1
boot: order=scsi0
cores: 4
cpu: host
machine: q35
memory: 8192
meta: creation-qemu=7.1.0,ctime=1671995061
name: HAM01-OPNsense
net0: virtio=56:F6:F6:5D:A9:B0,bridge=vmbr1,firewall=1
net1: virtio=A6:9F:7B:7A:98:B3,bridge=vmbr2,firewall=1
numa: 1
onboot: 1
ostype: l26
scsi0: lambo:vm-100-disk-0,discard=on,iothread=1,size=32G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=75da9b64-32b6-48d4-9adb-b18de925fc18
sockets: 1
vmgenid: 23348b2a-4121-484c-81ee-b7513ca482d7

Output from journalctl for the most recent crash:
Code:
Apr 27 06:18:00 pve2 QEMU[2165]: KVM internal error. Suberror: 3
Apr 27 06:18:00 pve2 QEMU[2165]: extra data[0]: 0x0000000080000b0e
Apr 27 06:18:00 pve2 QEMU[2165]: extra data[1]: 0x0000000000000031
Apr 27 06:18:00 pve2 QEMU[2165]: extra data[2]: 0x0000000000000083
Apr 27 06:18:00 pve2 QEMU[2165]: extra data[3]: 0x000000082e865fe0
Apr 27 06:18:00 pve2 QEMU[2165]: extra data[4]: 0x0000000000000002
Apr 27 06:18:00 pve2 QEMU[2165]: RAX=000000082e865e00 RBX=fffffe0011e5d090 RCX=00000000c0000101 RDX=00000000ffffffff
Apr 27 06:18:00 pve2 QEMU[2165]: RSI=00007fffdebf3ed4 RDI=fffffe0011e5d090 RBP=fffffe0011e5d080 RSP=fffffe0011e5cfb0
Apr 27 06:18:00 pve2 QEMU[2165]: R8 =0000000000000000 R9 =0000000000000000 R10=00000008335921b0 R11=0000000000000000
Apr 27 06:18:00 pve2 QEMU[2165]: R12=000000083360d880 R13=0000000000000002 R14=0000000000000000 R15=000000082e865e00
Apr 27 06:18:00 pve2 QEMU[2165]: RIP=ffffffff811332b1 RFL=00010082 [--S----] CPL=0 II=0 A20=1 SMM=0 HLT=0
Apr 27 06:18:00 pve2 QEMU[2165]: ES =003b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Apr 27 06:18:00 pve2 QEMU[2165]: CS =0020 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
Apr 27 06:18:00 pve2 QEMU[2165]: SS =0000 0000000000000000 ffffffff 00c00000
Apr 27 06:18:00 pve2 QEMU[2165]: DS =003b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Apr 27 06:18:00 pve2 QEMU[2165]: FS =0013 0000000839102800 ffffffff 00c0f300 DPL=3 DS   [-WA]
Apr 27 06:18:00 pve2 QEMU[2165]: GS =001b ffffffff82611000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Apr 27 06:18:00 pve2 QEMU[2165]: LDT=0000 0000000000000000 ffffffff 00c00000
Apr 27 06:18:00 pve2 QEMU[2165]: TR =0048 ffffffff82611384 00002068 00008b00 DPL=0 TSS64-busy
Apr 27 06:18:00 pve2 QEMU[2165]: GDT=     ffffffff826113ec 00000067
Apr 27 06:18:00 pve2 QEMU[2165]: IDT=     ffffffff81f5d710 00000fff
Apr 27 06:18:00 pve2 QEMU[2165]: CR0=80050033 CR2=ffffffff811332b1 CR3=000000082e865e00 CR4=003506e0
Apr 27 06:18:00 pve2 QEMU[2165]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Apr 27 06:18:00 pve2 QEMU[2165]: DR6=00000000ffff0ff0 DR7=0000000000000400
Apr 27 06:18:00 pve2 QEMU[2165]: EFER=0000000000000d01
Apr 27 06:18:00 pve2 QEMU[2165]: Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!