[SOLVED] VM crash with Backup Job

V

virmix

Member
Sep 4, 2020
36
1
13
I check and do test to reproduce the error.

1st Test : If I create a Back Job star and end right, but in some hours later crash. I create a daily job and every day crash.

2nd Test : For 2 week I run backup manualy from VM and never crash.

3rd Test : Create a new job for Monday and Wenesday, all go right and backup end, but in some hours later crash. Only crash in Monday and Wenesday.

4th Test: I delete VM and create new VM with same OS & VirtIO & QEMU and do the same.

My VM is Windows 2022 and I check QEMU Service and all go right. Start when Backup beging and stop when finish.

I know the crash not happend when backup is running, but always happend in the day of running job.


ERROR
Jun 10 06:03:24 node1 QEMU[2895327]: KVM: entry failed, hardware error 0x80000021
Jun 10 06:03:24 node1 kernel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
Jun 10 06:03:24 node1 QEMU[2895327]: If you're running a guest on an Intel machine without unrestricted mode
Jun 10 06:03:24 node1 QEMU[2895327]: support, the failure can be most likely due to the guest entering an invalid
Jun 10 06:03:24 node1 QEMU[2895327]: state for Intel VT. For example, the guest maybe running in big real mode
Jun 10 06:03:24 node1 QEMU[2895327]: which is not supported on less recent Intel processors.
Jun 10 06:03:24 node1 QEMU[2895327]: EAX=00a30a7c EBX=c4d9f180 ECX=00000000 EDX=00000000
Jun 10 06:03:24 node1 QEMU[2895327]: ESI=c4dab1c0 EDI=b5ce7080 EBP=11378690 ESP=113784b0
Jun 10 06:03:24 node1 QEMU[2895327]: EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0
Jun 10 06:03:24 node1 QEMU[2895327]: ES =0000 00000000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: CS =c200 7ffc2000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: SS =0000 00000000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: DS =0000 00000000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: FS =0000 00000000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: GS =0000 00000000 ffffffff 00809300
Jun 10 06:03:24 node1 QEMU[2895327]: LDT=0000 00000000 000fffff 00000000
Jun 10 06:03:24 node1 QEMU[2895327]: TR =0040 c4dae000 00000067 00008b00
Jun 10 06:03:24 node1 QEMU[2895327]: GDT= c4daffb0 00000057
Jun 10 06:03:24 node1 QEMU[2895327]: IDT= 00000000 00000000
Jun 10 06:03:24 node1 QEMU[2895327]: CR0=00050032 CR2=04e79e00 CR3=056d5000 CR4=00000000
Jun 10 06:03:24 node1 QEMU[2895327]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Jun 10 06:03:24 node1 QEMU[2895327]: DR6=00000000ffff0ff0 DR7=0000000000000400
Jun 10 06:03:24 node1 QEMU[2895327]: EFER=0000000000000000
Jun 10 06:03:24 node1 QEMU[2895327]: Code=kvm: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed.
Click to expand...

CPU E3-1240 v5 @ 3.50GHz

Code: 
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 
Last edited:
Hi,
please see this thread. There are a few suggested workarounds, but AFAIK the root cause of the issue was not yet determined.
 
  • Like
Reactions: rursache
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back