Internal error on vm

A

Andyr

New Member
Proxmox Subscriber
Jun 13, 2023
1
0
1
Hi! I do have the problem, that i get an internal error on a vm after aprox. 24 hours running time. In this state the vm couldnt be controlled. After restarting the whole host, everything works fine again for aprox. 24 hours, than back in the loop :) Installed on the vm is a windows server. I already created another vm and attached the same harddisk again. Same error on the new vm.

What may i do? Any ideas?

Thank you!

Code: 
pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-4 (running version: 7.4-4/4a8501a8)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx4
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-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-3
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.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.0
pve-cluster: 7.3-3
pve-container: 4.4-4
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-2
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1

Code: 
qm config 103
boot: order=ide0
cores: 4
ide0: local:103/vm-103-disk-0.raw,size=240G
ide2: none,media=cdrom
machine: pc-i440fx-7.2
memory: 8000
meta: creation-qemu=7.2.0,ctime=1686484816
name: xxx
net0: rtl8139=3E:68:19:22:3A:AB,bridge=vmbr1,firewall=1 (i also tryed intel e1000!)
numa: 0
ostype: win7
scsihw: virtio-scsi-single
smbios1: xxx
sockets: 1
vmgenid: xxx
 
Last edited:
Nobody an idea? Today the machine crashed after aprox 15 minutes. So i again have to restart the whole host. Thats really mad! I am thinking about changing to a hyper-v virtualization.

By the way, i already tryed cpu type hosts. No i switched backup to kvm64.

I found this error log.

Code: 
Jun 13 10:51:52 vmhost16 QEMU[134592]: KVM internal error. Suberror: 3
Jun 13 10:51:52 vmhost16 QEMU[134592]: extra data[0]: 0x000000008000002f
Jun 13 10:51:52 vmhost16 QEMU[134592]: extra data[1]: 0x0000000000000020
Jun 13 10:51:52 vmhost16 QEMU[134592]: extra data[2]: 0x0000000000000582
Jun 13 10:51:52 vmhost16 QEMU[134592]: extra data[3]: 0x0000000000000009
Jun 13 10:51:52 vmhost16 QEMU[134592]: RAX=0000000000000000 RBX=fffffa8008c1c8e0 RCX=0000000040000070 RDX=0000000000000000
Jun 13 10:51:52 vmhost16 QEMU[134592]: RSI=fffffa8008c1c9a0 RDI=0000000000000102 RBP=fffff88005a2e9e0 RSP=fffff88005a2e938
Jun 13 10:51:52 vmhost16 QEMU[134592]: R8 =fffffa8007e040e8 R9 =0000000000000000 R10=fffffffffffffff7 R11=0000000000000000
Jun 13 10:51:52 vmhost16 QEMU[134592]: R12=0000000000000000 R13=0000000000000000 R14=0000000000000001 R15=fffff78000000008
Jun 13 10:51:52 vmhost16 QEMU[134592]: RIP=fffff800028c32ec RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
Jun 13 10:51:52 vmhost16 QEMU[134592]: ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS   [-WA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: FS =0053 000000007ef94000 0000fc00 0040f300 DPL=3 DS   [-WA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: GS =002b fffff880020e1000 ffffffff 00c0f300 DPL=3 DS   [-WA]
Jun 13 10:51:52 vmhost16 QEMU[134592]: LDT=0000 0000000000000000 ffffffff 00c00000
Jun 13 10:51:52 vmhost16 QEMU[134592]: TR =0040 fffff880020e5f40 00000067 00008b00 DPL=0 TSS64-busy
Jun 13 10:51:52 vmhost16 QEMU[134592]: GDT=     fffff880020ec540 0000007f
Jun 13 10:51:52 vmhost16 QEMU[134592]: IDT=     fffff880020ec5c0 00000fff
Jun 13 10:51:52 vmhost16 QEMU[134592]: CR0=80050031 CR2=0000000005030000 CR3=00000001f0a14000 CR4=000006f8
Jun 13 10:51:52 vmhost16 QEMU[134592]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Jun 13 10:51:52 vmhost16 QEMU[134592]: DR6=00000000ffff0ff0 DR7=0000000000000400
Jun 13 10:51:52 vmhost16 QEMU[134592]: EFER=0000000000000d01
Jun 13 10:51:52 vmhost16 QEMU[134592]: Code=25 a8 4b 00 00 b9 70 00 00 40 0f ba 32 00 72 06 33 c0 8b d0 <0f> 30 5a 58 59 c3 90 90 90 90 90 90 90 90 90 90 90 90 90 90 cc cc cc cc cc cc 66 66 0f 1f
 
Last edited:
No, but i did now, after you wrote. And i startet the machine at aprox 9 o'clock an i do have an internal error again now. The machine runs about 1,5 hours, i need help, urgent! :(
 
By the way, on the proxmox host are 2 additional vms, which both run independent of the state of the faulty vm, which has the internal error problem. If the machine has the internal error problem, i can access both other installed vms and they are running without problem.
 
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