[SOLVED]: Proxmox + KVM: entry failed, hardware error 0x80000021

Got only one VM with Windows 2016 (among many other VMs) which fails with error mentioned below.
(It has UEFI boot option, never seen such behaviour on BIOS based VMs).

Solution: set CPU type in VM hardware settings to the "qemu64".
(Made that change 2 days ago and VM is still running, however previously it did not work more than 2 minutes).

So there was no need to reboot Proxmox with updated kernel or use any other workaround.


--
The error: 

journalctl --since "3 days ago" 

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: KVM: entry failed, hardware error 0x80000021

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: If you're running a guest on an Intel machine without unrestricted mode

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: support, the failure can be most likely due to the guest entering an invalid

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: state for Intel VT. For example, the guest maybe running in big real mode

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: which is not supported on less recent Intel processors.

Mar 04 15:18:42 proxmox.domain kernel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.

Mar 04 15:18:42 proxmox.domain audit[1742797]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1742797 comm=43505520302F4B564D exe="/usr/bin/qemu-system-x86_64" sig=6 >

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: EAX=0000ac70 EBX=68152180 ECX=00000000 EDX=00000000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: ESI=39374080 EDI=3953c080 EBP=00000000 ESP=a5afa8c0

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: ES =0000 00000000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: CS =aa00 7ffaa000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: SS =0000 00000000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: DS =0000 00000000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: FS =0000 00000000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: GS =0000 00000000 ffffffff 00809300

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: LDT=0000 00000000 ffffffff 00c00000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: TR =0040 69d0a000 00000067 00008b00

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: GDT=     69d0bfb0 00000057

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: IDT=     00000000 00000000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: CR0=00050032 CR2=6e830000 CR3=49a23000 CR4=00000000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: DR6=00000000ffff0ff0 DR7=0000000000000400

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: EFER=0000000000000000

Mar 04 15:18:42 proxmox.domain QEMU[1742797]: Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:76: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed.

[SOLVED]: ERROR: Error opening output file vhdxz. (urbackupsrv decompress-file)

# urbackupsrv decompress-file -f /tmp/test/Image_E_241022-1054.vhdxz
2025-01-10 09:25:33: ERROR: Error opening output file "/tmp/test/Image_E_241022-1054.vhdxz"

Solution:

1. Change ownership of the parent directory (where vhdxz file located) to urbackup user

# chown urbackup /tmp/test/ 

2. Run it as urbackup user (running as root did not work for me!)

# sudo -u urbackup urbackupsrv decompress-file -f /tmp/test/Image_E_241022-1054.vhdxz
2025-01-10 09:26:02: Decompressing "/tmp/test/Image_E_241022-1054.vhdxz"... 0%
2025-01-10 09:26:02: Decompressing "/tmp/test/Image_E_241022-1054.vhdxz"... 1%
2025-01-10 09:26:02: Decompressing "/tmp/test/Image_E_241022-1054.vhdxz"... 2%
2025-01-10 09:26:02: Decompressing "/tmp/test/Image_E_241022-1054.vhdxz"... 3%
...

 

[РЕШЕНО]: 1С ошибка 1053 служба не ответила на запрос своевременно | ragent has stopped working" (APPCRASH) | Прекращена работа программы 1C | ragent rserver exception code c0000005

В моём случае причиной ошибки был антивирус. Дальше разбирайтесь с антивирусом (отключайте/лечите/добавляйте исключения).

Проверьте журнал системы (Event Viewer -> Windows Logs -> System):

"Microsoft Antimalware has detected malware or other potentially unwanted  software." (Source: Microsoft Antimalware, Event ID: 1116)

Microsoft Antimalware has detected malware or other potentially unwanted software.
 For more information please see the following:
http://go.microsoft.com/fwlink/?linkid=37020&name=PUA:Win32/Packunwan&threatid=298189&enterprise=1
     Name: PUA:Win32/Packunwan
     ID: 298189
     Severity: Severe
     Category: Potentially Unwanted Software
     Path: file:_C:\Program Files\1cv8\8.3.12.1529\bin\x ;file:_C:\Program Files\1cv8\8.3.9.2309\bin\x
     Detection Origin: Local machine
     Detection Type: Concrete
     Detection Source: Real-Time Protection
     User:      Process Name: C:\Program Files\1cv8\8.3.12.1529\bin\rphost.exe
     Signature Version: AV: 1.421.263.0, AS: 1.421.263.0, NIS: 0.0.0.0
     Engine Version: AM: 1.1.24090.11, NIS: 0.0.0.0

P.S. Если запустить службу как процесс в командной строке
(Пуск - cmd с правами администора - "C:\Program Files\1cv8\8.3.9.2309\bin\ragent.exe" -srvc -agent -regport 1741 -port 1740 -range 1760:1791 -d E:\1c_log\1cv82\srvinfo\ -debug)
То вы увидите "ragent has stopped working" (APPCRASH), в русской версии Windows это скорее всего переводится как "Прекращена работа программы"

 

ragent rserver exception code c0000005

#1C #1С