[SOLVED] Experiencing a crash when running openwrt: KVM internal error. Suberror: 1

herobrine

New Member
Nov 22, 2023
3
1
1
Hi, everybody
After installing OpenWrt R23.11.11 and running normally for some time, the virtual machine freezes and writes the error "internal error".
When viewing the syslog , I found these messages
Nov 22 03:37:13 pve QEMU[1050]: KVM internal error. Suberror: 1
Nov 22 03:37:13 pve QEMU[1050]: extra data[0]: 0x0000000000000001
Nov 22 03:37:13 pve QEMU[1050]: extra data[1]: 0x0877e8fcca010f0f
Nov 22 03:37:13 pve QEMU[1050]: extra data[2]: 0x6c8d48c489480000
Nov 22 03:37:13 pve QEMU[1050]: extra data[3]: 0x000000000000001e
Nov 22 03:37:13 pve QEMU[1050]: extra data[4]: 0x0000000000010018
Nov 22 03:37:13 pve QEMU[1050]: extra data[5]: 0x0000000000000000
Nov 22 03:37:13 pve QEMU[1050]: extra data[6]: 0x0000000000000000
Nov 22 03:37:13 pve QEMU[1050]: extra data[7]: 0x0000000000000000
Nov 22 03:37:13 pve QEMU[1050]: emulation failure
Nov 22 03:37:13 pve QEMU[1050]: RAX=000000000000434e RBX=ffffffff82217600 RCX=4000000000000000 RDX=0000000000000001
Nov 22 03:37:13 pve QEMU[1050]: RSI=0000000000000000 RDI=000000002056f86c RBP=ffffffff82203e38 RSP=fffffe000000dfa0
Nov 22 03:37:13 pve QEMU[1050]: R8 =0000000000000000 R9 =0000000000000321 R10=0000000000000000 R11=000000000000031c
Nov 22 03:37:13 pve QEMU[1050]: R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=ffffffff82217118
Nov 22 03:37:13 pve QEMU[1050]: RIP=ffffffff81a00a80 RFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
Nov 22 03:37:13 pve QEMU[1050]: ES =0000 0000000000000000 ffffffff 00c00000
Nov 22 03:37:13 pve QEMU[1050]: CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
Nov 22 03:37:13 pve QEMU[1050]: SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
Nov 22 03:37:13 pve QEMU[1050]: DS =0000 0000000000000000 ffffffff 00c00000
Nov 22 03:37:13 pve QEMU[1050]: FS =0000 0000000000000000 ffffffff 00c00000
Nov 22 03:37:13 pve QEMU[1050]: GS =0000 ffff88803ec00000 ffffffff 00c00000
Nov 22 03:37:13 pve QEMU[1050]: LDT=0000 0000000000000000 ffffffff 00c00000
Nov 22 03:37:13 pve QEMU[1050]: TR =0040 fffffe0000003000 00004087 00008b00 DPL=0 TSS64-busy
Nov 22 03:37:13 pve QEMU[1050]: GDT= fffffe0000001000 0000007f
Nov 22 03:37:13 pve QEMU[1050]: IDT= fffffe0000000000 00000fff
Nov 22 03:37:13 pve QEMU[1050]: CR0=80050033 CR2=000000004ac2af3a CR3=000000000e096000 CR4=00350ef0
Nov 22 03:37:13 pve QEMU[1050]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Nov 22 03:37:13 pve QEMU[1050]: DR6=00000000ffff0ff0 DR7=0000000000000400
Nov 22 03:37:13 pve QEMU[1050]: EFER=0000000000000d01
Nov 22 03:37:13 pve QEMU[1050]: Code=24 78 ff ff ff ff e8 49 ec f7 ff e9 a4 09 00 00 0f 1f 40 00 <0f> 01 ca fc e8 77 08 00 00 48 89 c4 48 8d 6c 24 01 48 89 e7 48 8b 74 24 78 48 c7 44 24 78

This is the pveversion:
proxmox-ve: 8.0.2 (running kernel: 6.2.16-18-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2: 6.2.16-18
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.5
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.9
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.9
pve-cluster: 8.0.4
pve-container: 5.0.4
pve-docs: 8.0.5
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.8-3
pve-ha-manager: 4.0.2
pve-i18n: 3.0.7
pve-qemu-kvm: 8.0.2-7
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.13-pve1

the qm config:
agent: 1
boot: order=scsi0
cores: 2
cpu: host
memory: 1024
meta: creation-qemu=8.0.2,ctime=1688134843
name: lede
net0: virtio=<data>,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
parent: set
scsi0: local-lvm:vm-101-disk-0,iothread=1,size=420M
scsihw: virtio-scsi-single
smbios1: uuid=<data>
sockets: 1
vmgenid: <data>

What CPU model does your host have?
Intel Celeron J6412

The openWRT Kernel version: 6.1.61


I implore you to be able to help me with this
Thank you for your help.
 
Hi,
you could try upgrading to kernel 6.5 (see here) and/or QEMU 8.1 (already in the no-subscription repository). Do you have the latest version of the intel-microcode installed? Latest BIOS update?
 
Hi,
you could try upgrading to kernel 6.5 (see here) and/or QEMU 8.1 (already in the no-subscription repository). Do you have the latest version of the intel-microcode installed? Latest BIOS update?
Okay, I'll try to update the kernel to version 6.5 and run it for a while to see what happens.
I haven't installed intel-microcode yet, I'll update them together later.
Thank you very much for taking the time to help me out!
 
Since the update, the corresponding virtual machine has been working fine so far, the problem should have been solved, thanks for your help!
 
Last edited:
  • Like
Reactions: fiona

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!