ProxMox 1.5: KVM image not auto starting

M

mjoconr

Renowned Member
Proxmox Subscriber
Dec 5, 2009
88
1
73
Hi All

I just did a test shutdown and restart of my Proxmox system in readiness for moving the system to full production.

The problem is that once the system was powered up again the kvm images did not restart.

Any ideas ?

Mike
 
mjoconr said:
Hi All

I just did a test shutdown and restart of my Proxmox system in readiness for moving the system to full production.

The problem is that once the system was powered up again the kvm images did not restart.

Any ideas ?

Mike
Click to expand...

the first question: do you ticked the 'start at boot'?

works here. do you ran the latest version? pls post your 'pveversion -v' results.

any hint in the syslog?
 
No indication of why they where not started

proxmox-243:~# pveversion -v
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3
proxmox-243:~#

I do get a lot of messages like this:
Feb 24 23:14:32 proxmox-243 proxwww[7110]: Starting new child 7110
Feb 24 23:14:36 proxmox-243 pvedaemon[5351]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:14:37 proxmox-243 pvedaemon[5610]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:14:42 proxmox-243 pvedaemon[5351]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:14:42 proxmox-243 pvedaemon[5610]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:14:47 proxmox-243 pvedaemon[5610]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:14:48 proxmox-243 pvedaemon[5351]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Feb 24 23:15:07 proxmox-243 pvemirror[3004]: starting cluster syncronization
Feb 24 23:15:07 proxmox-243 pvemirror[3004]: syncing templates
Feb 24 23:15:07 proxmox-243 pvemirror[3004]: cluster syncronization finished (0.06 seconds (files 0.00, config 0.00))

I can not see any reason why they did not start.

Mike
 
You can safely ignor those "Cannot encode" warnings.

What happens when you try to start manually:

# qm startall
 
You must log in or register to reply here.
Top Bottom