KVM VM's Not Starting After Reboot

gobiyoga

New Member
Sep 2, 2016
3
0
1
26
My VM's are not starting after I installed my SSL certificate and rebooted.

When I try to boot my VM's manually I get an error like this:

root@vps:~# qm start 100
kvm: CPU model 'host' requires KVM
start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=37549d93-c9e8-4c0a-8433-2b18b4cf2867' -name WEBSRV -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu host -m 12228 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:c6bcb1a3f16' -drive '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=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=00:50:56:0a:21:82,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=00:50:56:09:ab:82,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301' -machine 'accel=tcg'' failed: exit code 1
ipcc_send_rec failed: File too large

Everything was working fine before I rebooted.
 
This is what I got from syslog:

Code:
root@vps:~# cat /var/log/syslog
Sep  2 06:25:06 vps rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pi                                                                                     d="1129" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Sep  2 06:31:04 vps pvedaemon[4059]: start VM 100: UPID:vps:00000FDB:00048CA3:57                                                                                     C954E8:qmstart:100:root@pam:
Sep  2 06:31:04 vps pvedaemon[1284]: <root@pam> starting task UPID:vps:00000FDB:                                                                                     00048CA3:57C954E8:qmstart:100:root@pam:
Sep  2 06:31:04 vps rsyslogd0: action 'action 17' resumed (module 'builtin:eek:mpip                                                                                     e') [try http://www.rsyslog.com/e/0 ]
Sep  2 06:31:04 vps rsyslogd-2359: action 'action 17' resumed (module 'builtin:eek:                                                                                     mpipe') [try http://www.rsyslog.com/e/2359 ]
Sep  2 06:31:04 vps kernel: [ 2981.875084] device tap100i0 entered promiscuous m                                                                                     ode
Sep  2 06:31:04 vps kernel: [ 2981.878489] vmbr0: port 2(tap100i0) entered forwa                                                                                     rding state
Sep  2 06:31:04 vps kernel: [ 2981.878495] vmbr0: port 2(tap100i0) entered forwa                                                                                     rding state
Sep  2 06:31:05 vps kernel: [ 2982.308433] device tap100i1 entered promiscuous m                                                                                     ode
Sep  2 06:31:05 vps kernel: [ 2982.311985] vmbr0: port 3(tap100i1) entered forwa                                                                                     rding state
Sep  2 06:31:05 vps kernel: [ 2982.311991] vmbr0: port 3(tap100i1) entered forwa                                                                                     rding state
Sep  2 06:31:05 vps kernel: [ 2982.524777] vmbr0: port 2(tap100i0) entered disab                                                                                     led state
Sep  2 06:31:05 vps kernel: [ 2982.783227] vmbr0: port 3(tap100i1) entered disab                                                                                     led state
Sep  2 06:31:05 vps pvedaemon[1283]: client closed connection
Sep  2 06:31:05 vps pvedaemon[4059]: start failed: command '/usr/bin/kvm -id 100                                                                                      -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon '                                                                                     chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbi                                                                                     os 'type=1,uuid=37549d93-c9e8-4c0a-8433-2b18b4cf2867' -name WEBSRV -smp '4,socke                                                                                     ts=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000                                                                                     ' -vga cirrus -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu host -m                                                                                      12228 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -d                                                                                     evice 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-                                                                                     uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,po                                                                                     rt=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initia                                                                                     tor-name=iqn.1993-08.org.debian:01:c6bcb1a3f16' -drive 'if=none,id=drive-ide2,me                                                                                     dia=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2                                                                                     ,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id                                                                                     =drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device                                                                                      'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa' -netdev 'type                                                                                     =tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/                                                                                     var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=00:50:5                                                                                     6:0a:21:82,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=                                                                                     tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/v                                                                                     ar/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=00:50:56                                                                                     :09:ab:82,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301' -machine 'accel                                                                                     =tcg'' failed: exit code 1
 

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!