KVM guest dies silently

OSA

New Member
Apr 5, 2017
7
0
1
38
Dear Colleagues,

I'm struggling to catch the reason for shutting down of one of my KVM guests (CentOS 7.3 with 3.10.0-514.10.2 kernel)
Just for information - this is production one and I have one more node with same OS at this host
and everything is OK with it.

I've set i6300esb watchdog up (not in realtime mode because unable to set scheduler - see my last comment at redhat bugzilla - id=805397#c6) but it didn't help - it is unable to detect and restart when my machine dies.

Just for information - I've enabled kdump, kernel.panic = 15 on guest OS
Also, I've checked SSD (this is Hetzner hosting with dual 500GB SSD in RAID1)

Last sporadic shutdown was detected today at 5:16 UTC+2
But still logs are silent both on host and guest.
VM died 2 times yesterday, once 2 days ago, once 6 days ago.
Simply without any periodicity.

I'm thinking about enabling verbose syslog messages on PVE host via
echo "1" >/etc/pve/.debug
but it writes too much info to logs and I am worried to get out of space soon.

Here is the configuration of my Proxmox host and affected node.
Virtual Environment 4.4-13/7ea56165
Node 'vm'
Logs
()

==== general system info ====
# hostname
vm
# pveversion --verbose
proxmox-ve: 4.4-86 (running kernel: 4.4.49-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.4.40-1-pve: 4.4.40-82
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-49
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-97
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: not correctly installed
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80

# top -b -n 1 | head -n 15
top - 05:50:26 up 3 days, 22:17, 1 user, load average: 0.39, 0.36, 0.27
Tasks: 197 total, 1 running, 196 sleeping, 0 stopped, 0 zombie
%Cpu(s): 14.4 us, 0.4 sy, 0.0 ni, 85.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 32757468 total, 20850244 used, 11907224 free, 186980 buffers
KiB Swap: 8388604 total, 0 used, 8388604 free. 278400 cached Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
22856 root 20 0 24.955g 0.012t 13624 S 105.3 37.7 5:10.66 kvm
1 root 20 0 30188 5624 3076 S 0.0 0.0 0:04.11 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.03 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:04.51 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:+
7 root 20 0 0 0 0 S 0.0 0.0 2:42.33 rcu_sched
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root rt 0 0 0 0 S 0.0 0.0 0:00.48 migration/0

# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 94
Model name: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Stepping: 3
CPU MHz: 3897.382
CPU max MHz: 4000.0000
CPU min MHz: 800.0000
BogoMIPS: 6816.61
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7

==== info about storage (lvm and zfs) ====
# cat /etc/pve/storage.cfg
lvm: storage1
vgname vg0
shared 0
content rootdir,images

dir: local
path /var/lib/vz
maxfiles 0
content vztmpl,iso,rootdir,images

dir: SambaBackup
path /mnt/SambaBackup
maxfiles 2
shared 1
content images,backup,vztmpl,iso

# pvesm status
SambaBackup dir 1 524288000 166207554 358080445 32.20%
local dir 1 20511356 3912464 15533932 20.62%
storage1 lvm 1 487727104 447741952 39985152 92.30%

# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=4091193,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=6551496k,mode=755)
/dev/mapper/vg0-root on / type ext4 (rw,noatime,discard,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/md0 on /boot type ext3 (rw,relatime,stripe=4,data=ordered)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=3275748k,mode=700)
# df --human
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 6.3G 25M 6.3G 1% /run
/dev/dm-0 20G 3.8G 15G 21% /
tmpfs 16G 40M 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/md0 488M 186M 277M 41% /boot
/dev/fuse 30M 16K 30M 1% /etc/pve
tmpfs 3.2G 0 3.2G 0% /run/user/0

==== info about virtual machines ====
# qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
101 secondary running 8192 150.00 27441
102 main running 24576 249.00 22856

# cat /etc/pve/qemu-server/102.conf
agent: 1
balloon: 15500
boot: cdn
bootdisk: virtio0
cores: 7
cpuunits: 45000
hotplug: disk,network,usb,memory,cpu
ide2: local:iso/CentOS-7-x86_64-Minimal.iso,media=cdrom
memory: 24576
name: main
net0: virtio=00:50:56:00:B0:46,bridge=vmbr0
numa: 1
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=d551ac36-89d2-4ebc-8bef-ad0a29bb8a55
sockets: 1
virtio0: storage1:vm-102-disk-1,discard=on,size=249G
watchdog: model=i6300esb,action=reset

# cat /etc/pve/qemu-server/101.conf
args: --redir tcp:5555::22
balloon: 5500
bootdisk: virtio0
cores: 4
hotplug: disk,network,usb,memory,cpu
ide2: local:iso/CentOS-7-x86_64-Minimal.iso,media=cdrom
memory: 8192
name: secondary
net0: virtio=00:50:56:00:BA:82,bridge=vmbr0
numa: 1
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=ec9ccafc-d844-42dc-b608-9dd075e40e0a
sockets: 1
virtio0: storage1:vm-101-disk-1,discard=on,size=150G
watchdog: model=i6300esb,action=reset

==== info about bios ====
# dmidecode -t bios
# dmidecode 2.12
SMBIOS 3.0 present.
# SMBIOS implementations newer than version 2.8 are not
# fully supported by this version of dmidecode.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: FUJITSU // American Megatrends Inc.
Version: V5.0.0.11 R1.7.0.SR.2 for D3401-H1x
Release Date: 11/25/2015
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16384 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.7

Handle 0x004E, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 2
en|US|iso8859-1
ja|JP|unicode
Currently Installed Language: en|US|iso8859-1

==== info about disks ====
# lsblk --ascii
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
|-sda1 8:1 0 512M 0 part
| `-md0 9:0 0 511.4M 0 raid1 /boot
`-sda2 8:2 0 465.3G 0 part
`-md1 9:1 0 465.1G 0 raid1
|-vg0-root 251:0 0 20G 0 lvm /
|-vg0-swap 251:1 0 8G 0 lvm [SWAP]
|-vg0-vm--101--disk--1 251:2 0 150G 0 lvm
`-vg0-vm--102--disk--1 251:3 0 249G 0 lvm
sdb 8:16 0 465.8G 0 disk
|-sdb1 8:17 0 512M 0 part
| `-md0 9:0 0 511.4M 0 raid1 /boot
`-sdb2 8:18 0 465.3G 0 part
`-md1 9:1 0 465.1G 0 raid1
|-vg0-root 251:0 0 20G 0 lvm /
|-vg0-swap 251:1 0 8G 0 lvm [SWAP]
|-vg0-vm--101--disk--1 251:2 0 150G 0 lvm
`-vg0-vm--102--disk--1 251:3 0 249G 0 lvm
Could you please assist me and advise on how this issue can be troubleshooted.

Thank you.
 

Attachments

  • conf.txt
    conf.txt
    10.3 KB · Views: 3
  • conf.jpg
    conf.jpg
    178.9 KB · Views: 5
Hi2All,

just faced fresh VM shutdown. likely enabled debug yesterday.

from guest /var/log/messages:

Apr 6 11:51:46 asterisk: [2017-04-06 11:51:46.043] some log
Apr 6 12:00:48 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="1270" x-info="..."] start

so last events in logs on guest are dated ~11:52
12:00:48 - time when I started VM manually

in messages log on PVE:
Apr 6 10:52:22 vm kernel: [443919.943521] vmbr0: port 2(tap102i0) entered disabled state
So this is the time when guest died

sed -n '/Apr 6 10:52:01/,/Apr 6 10:53:00/p' syslog.1 with debug is in the attachment

Could you please help me in defining the root of the issue?
 

Attachments

Once again - 2 minutes ago just silent shutdown of VM

Colleagues, do you have any ideas how to troubleshoot this and fix?
 
you can start the vm on the console in the foreground and see if any message appears there when the vm stops
you can get the command line with
Code:
qm showcmd <ID>

and you have to remove the "-daemonize" part
 
Hi @dcsapak
Thank you for your update.

Could you please clarify what exactly should I do?

Is the following plan correct?

1. Shut down VM
2. Connect to PVE host via ssh and launch
qm start 102 in screen
3. wait for vm stop
4. connect to screen via ssh and execute
qm showcmd 102 ?

Sorry, haven't found where I should remove "-daemonize" part
 
stop the vm
connect via ssh
and execute
qm showcmd 102

the output is the command for starting the vm
remove the '-daemonize' part there and execute it

leave it running until the vm stops

see if any messages appear
 
Hi @dcsapak

Just crashed one more time.

There is only one new line in console
"kvm: Looped descriptor"

P.S.
here is my starting command:
root@vm ~ # /usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/102.pid -smbios 'type=1,uuid=d551ac36-89d2-4ebc-8bef-ad0a29bb8a55' -name main -smp '1,sockets=1,cores=7,maxcpus=7' -device 'kvm64-x86_64-cpu,id=cpu2,socket-id=0,core-id=1,thread-id=0' -device 'kvm64-x86_64-cpu,id=cpu3,socket-id=0,core-id=2,thread-id=0' -device 'kvm64-x86_64-cpu,id=cpu4,socket-id=0,core-id=3,thread-id=0' -device 'kvm64-x86_64-cpu,id=cpu5,socket-id=0,core-id=4,thread-id=0' -device 'kvm64-x86_64-cpu,id=cpu6,socket-id=0,core-id=5,thread-id=0' -device 'kvm64-x86_64-cpu,id=cpu7,socket-id=0,core-id=6,thread-id=0' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga cirrus -vnc unix:/var/run/qemu-server/102.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 'size=1024,slots=255,maxmem=4194304M' -object 'memory-backend-ram,id=ram-node0,size=1024M' -numa 'node,nodeid=0,cpus=0-6,memdev=ram-node0' -object 'memory-backend-ram,id=mem-dimm0,size=512M' -device 'pc-dimm,id=dimm0,memdev=mem-dimm0,node=0' -object 'memory-backend-ram,id=mem-dimm1,size=512M' -device 'pc-dimm,id=dimm1,memdev=mem-dimm1,node=0' -object 'memory-backend-ram,id=mem-dimm2,size=512M' -device 'pc-dimm,id=dimm2,memdev=mem-dimm2,node=0' -object 'memory-backend-ram,id=mem-dimm3,size=512M' -device 'pc-dimm,id=dimm3,memdev=mem-dimm3,node=0' -object 'memory-backend-ram,id=mem-dimm4,size=512M' -device 'pc-dimm,id=dimm4,memdev=mem-dimm4,node=0' -object 'memory-backend-ram,id=mem-dimm5,size=512M' -device 'pc-dimm,id=dimm5,memdev=mem-dimm5,node=0' -object 'memory-backend-ram,id=mem-dimm6,size=512M' -device 'pc-dimm,id=dimm6,memdev=mem-dimm6,node=0' -object 'memory-backend-ram,id=mem-dimm7,size=512M' -device 'pc-dimm,id=dimm7,memdev=mem-dimm7,node=0' -object 'memory-backend-ram,id=mem-dimm8,size=512M' -device 'pc-dimm,id=dimm8,memdev=mem-dimm8,node=0' -object 'memory-backend-ram,id=mem-dimm9,size=512M' -device 'pc-dimm,id=dimm9,memdev=mem-dimm9,node=0' -object 'memory-backend-ram,id=mem-dimm10,size=512M' -device 'pc-dimm,id=dimm10,memdev=mem-dimm10,node=0' -object 'memory-backend-ram,id=mem-dimm11,size=512M' -device 'pc-dimm,id=dimm11,memdev=mem-dimm11,node=0' -object 'memory-backend-ram,id=mem-dimm12,size=512M' -device 'pc-dimm,id=dimm12,memdev=mem-dimm12,node=0' -object 'memory-backend-ram,id=mem-dimm13,size=512M' -device 'pc-dimm,id=dimm13,memdev=mem-dimm13,node=0' -object 'memory-backend-ram,id=mem-dimm14,size=512M' -device 'pc-dimm,id=dimm14,memdev=mem-dimm14,node=0' -object 'memory-backend-ram,id=mem-dimm15,size=512M' -device 'pc-dimm,id=dimm15,memdev=mem-dimm15,node=0' -object 'memory-backend-ram,id=mem-dimm16,size=512M' -device 'pc-dimm,id=dimm16,memdev=mem-dimm16,node=0' -object 'memory-backend-ram,id=mem-dimm17,size=512M' -device 'pc-dimm,id=dimm17,memdev=mem-dimm17,node=0' -object 'memory-backend-ram,id=mem-dimm18,size=512M' -device 'pc-dimm,id=dimm18,memdev=mem-dimm18,node=0' -object 'memory-backend-ram,id=mem-dimm19,size=512M' -device 'pc-dimm,id=dimm19,memdev=mem-dimm19,node=0' -object 'memory-backend-ram,id=mem-dimm20,size=512M' -device 'pc-dimm,id=dimm20,memdev=mem-dimm20,node=0' -object 'memory-backend-ram,id=mem-dimm21,size=512M' -device 'pc-dimm,id=dimm21,memdev=mem-dimm21,node=0' -object 'memory-backend-ram,id=mem-dimm22,size=512M' -device 'pc-dimm,id=dimm22,memdev=mem-dimm22,node=0' -object 'memory-backend-ram,id=mem-dimm23,size=512M' -device 'pc-dimm,id=dimm23,memdev=mem-dimm23,node=0' -object 'memory-backend-ram,id=mem-dimm24,size=512M' -device 'pc-dimm,id=dimm24,memdev=mem-dimm24,node=0' -object 'memory-backend-ram,id=mem-dimm25,size=512M' -device 'pc-dimm,id=dimm25,memdev=mem-dimm25,node=0' -object 'memory-backend-ram,id=mem-dimm26,size=512M' -device 'pc-dimm,id=dimm26,memdev=mem-dimm26,node=0' -object 'memory-backend-ram,id=mem-dimm27,size=512M' -device 'pc-dimm,id=dimm27,memdev=mem-dimm27,node=0' -object 'memory-backend-ram,id=mem-dimm28,size=512M' -device 'pc-dimm,id=dimm28,memdev=mem-dimm28,node=0' -object 'memory-backend-ram,id=mem-dimm29,size=512M' -device 'pc-dimm,id=dimm29,memdev=mem-dimm29,node=0' -object 'memory-backend-ram,id=mem-dimm30,size=512M' -device 'pc-dimm,id=dimm30,memdev=mem-dimm30,node=0' -object 'memory-backend-ram,id=mem-dimm31,size=512M' -device 'pc-dimm,id=dimm31,memdev=mem-dimm31,node=0' -object 'memory-backend-ram,id=mem-dimm32,size=1024M' -device 'pc-dimm,id=dimm32,memdev=mem-dimm32,node=0' -object 'memory-backend-ram,id=mem-dimm33,size=1024M' -device 'pc-dimm,id=dimm33,memdev=mem-dimm33,node=0' -object 'memory-backend-ram,id=mem-dimm34,size=1024M' -device 'pc-dimm,id=dimm34,memdev=mem-dimm34,node=0' -object 'memory-backend-ram,id=mem-dimm35,size=1024M' -device 'pc-dimm,id=dimm35,memdev=mem-dimm35,node=0' -object 'memory-backend-ram,id=mem-dimm36,size=1024M' -device 'pc-dimm,id=dimm36,memdev=mem-dimm36,node=0' -object 'memory-backend-ram,id=mem-dimm37,size=1024M' -device 'pc-dimm,id=dimm37,memdev=mem-dimm37,node=0' -object 'memory-backend-ram,id=mem-dimm38,size=1024M' -device 'pc-dimm,id=dimm38,memdev=mem-dimm38,node=0' -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -chardev 'socket,path=/var/run/qemu-server/102.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -device 'i6300esb,bus=pci.0,addr=0x4' -watchdog-action reset -drive 'file=/var/lib/vz/template/iso/CentOS-7-x86_64-Minimal.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/dev/vg0/vm-102-disk-1,if=none,id=drive-virtio0,discard=on,format=raw,cache=none,aio=native,detect-zeroes=unmap' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=00:50:56:00:B0:46,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'

Could you please follow me to further steps?
 
can you try with memory hotplug disabled? the only reference to this kvm line was in reference to memory hotplug and a subsequent reboot of the vm
 
Hi
Disabled hotplug at all.
I will monitor for several weeks and get back to you with results.

Meanwhile,
if there any other solutions for this problem except disabling hotplug?
Is this fixed somewhere ? kernel update?
Now I use 3.10 but can't use 4 due to issues with stability
 
No new reboots so far )
Seems hotplug disabling helped.

What's the next ? Are there any plans to fix this permanently (or disable hotplug by defult) ?
 

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!