VM 100 automatically turns off

S

serduk

New Member
Dec 11, 2024
10
0
1
Good afternoon.
I'm new to Proxmox settings.
I have only 4 virtual machines.

Of these 4 VM, only one, number 100,
automatically turns off after a certain time.
I manually start this virtual machine 100.

I logged into the server and manually started the VM 100 on December 12, 09:06:47.
I tried to understand from the logs what happened before this time, but I couldn’t.
 

Attachments

What is the guest OS? What version of PVE? What CPU do you have?

It could be a bug. Some older kernels with PVE 7 triggered this bug when run on older hardware.

T

Thread 'VM shutdown, KVM: entry failed, hardware error 0x80000021'

Hello Community,

The following problem exists, a Windows Server 2019 VM migrated to Proxmox crashes regularly. The following can be found in /var/log/syslog:

May 10 08:37:14 prox01 QEMU[1148]: KVM: entry failed, hardware error 0x80000021 May 10 08:37:14 prox01 QEMU[1148]: If you're running a guest on an Intel machine without unrestricted mode May 10 08:37:14 prox01 kernel: [87072.394575] set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state. May 10 08:37:14 prox01 QEMU[1148]: support, the failure can be most likely due to the guest entering an invalid May 10 08:37:14 prox01 QEMU[1148]...

And this wiki entry:

https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Older_Hardware_and_New_5.15_Kernel
 
  • Like
Reactions: serduk
BobhWasatch said:
What is the guest OS? What version of PVE? What CPU do you have?

It could be a bug. Some older kernels with PVE 7 triggered this bug when run on older hardware.

T

Thread 'VM shutdown, KVM: entry failed, hardware error 0x80000021'

Hello Community,

The following problem exists, a Windows Server 2019 VM migrated to Proxmox crashes regularly. The following can be found in /var/log/syslog:

May 10 08:37:14 prox01 QEMU[1148]: KVM: entry failed, hardware error 0x80000021 May 10 08:37:14 prox01 QEMU[1148]: If you're running a guest on an Intel machine without unrestricted mode May 10 08:37:14 prox01 kernel: [87072.394575] set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state. May 10 08:37:14 prox01 QEMU[1148]: support, the failure can be most likely due to the guest entering an invalid May 10 08:37:14 prox01 QEMU[1148]...

And this wiki entry:

https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Older_Hardware_and_New_5.15_Kernel
Click to expand...

I have Proxmox 7.2-3
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Dec 13 03:09:35 +06 2024 on pts/0
root@pve1:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
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.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
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.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
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-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
root@pve1:~#
 
serduk said:
Thank u.
Does this mean I just need to upgrade
my Proxmox version from version 7 to version 8?
Will this solve my problem?
Click to expand...
Before a big update (like 7->8) it is good to found the cause of the issue, mainly if there are hardware issue on the host must be solved before (to avoid unforeseen events during the upgrade that could make the system unusable in some cases).
If there are OOM for vm memory configuration issue will be not solved by upgrade.
There may be other causes, but they should be looked at specifically.
 
Last edited:
  • Like
Reactions: Kingneutron
Hi,
Fantu said:
Before a big update (like 7->8) it is good to found the cause of the issue, mainly if there are hardware issue on the host must be solved before (to avoid unforeseen events during the upgrade that could make the system unusable in some cases).
If there are OOM for vm memory configuration issue will be not solved by upgrade.
There may be other causes, but they should be looked at specifically.
Click to expand...
the most likely cause is the one suggested in the very first reply by @BobhWasatch because it matches the error message in the system log. Upgrading should resolve that issue, and also Proxmox VE 7 is end-of-life for a few months now. An OOM error would look completely differently in the system log.
 
  • Like
Reactions: Kingneutron
You must log in or register to reply here.
Top Bottom