upgrade to 1.8 goes BaD!

nicolasdiogo

Member
Mar 16, 2010
92
0
6
hello,

i tried upgrading the server to 1.8; and i am finding that it just does not work at all.

the box boots, but takes longer then expected.
and then it does not run any guest OS - not even vanilla Ubuntu 10.04

i checked the system to see if kvm was enabled. and it seems fine in the BIOS (i did not change any setting between upgrading and rebooting) and within the OS. see below:

Code:
myserver:~# lsmod | grep kvm
kvm_amd                37383  0
kvm                   261884  1 kvm_amd
myserver:~# egrep '(vmx|svm)' --color=always /proc/cpuinfo
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save
but when trying to start a VM (using kvm) i get the following message on /var/log/syslog:

Code:
Apr 18 09:06:56 myserver pvedaemon[4557]: starting VM 9101 on node 0 (localhost)
Apr 18 09:06:56 myserver qm[4558]: VM 9101 start
Apr 18 09:06:56 myserver kernel: kvm: enabling virtualization on CPU0 failed
Apr 18 09:06:56 myserver kernel: device tap9101i0d0 entered promiscuous mode
Apr 18 09:06:56 myserver kernel: vmbr0: port 2(tap9101i0d0) entering forwarding state
Apr 18 09:06:56 myserver kernel: vmbr0: port 2(tap9101i0d0) entering forwarding state
Apr 18 09:06:56 myserver qm[4558]: VM 9101 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/9101.mon,server,nowait -vnc unix:/var/run/qemu-server/9101.vnc,password -pidfile /var/run/qemu-server/9101.pid -daemonize -usbdevice tablet -name tmpl-ubuntu-server-10.04-x64 -smp sockets=1,cores=2 -nodefaults -boot menu=on,order=cd -vga cirrus -tdf -drive file=/mnt/pve/iso-00/ubuntu-10.04.2-server-amd64.iso,if=ide,index=2,media=cdrom -drive if=ide,index=3,media=cdrom -drive file=/mnt/pve/vms-00/images/9101/vm-9101-disk-1.raw,if=virtio,index=0,cache=none,boot=on -m 512 -netdev type=tap,id=vlan0d0,ifname=tap9101i0d0,script=/var/lib/qemu-server/bridge-vlan,vhost=on -device virtio-net-pci,mac=B6:F9:1F:56:79:8B,netdev=vlan0d0' failed with exit code 1
Apr 18 09:06:56 myserver pvedaemon[4557]: VM 9101 start failed -
Apr 18 09:06:56 myserver kernel: vmbr0: new device tap9101i0d0 does not support netpoll (disabling)
Apr 18 09:06:56 myserver kernel: vmbr0: port 2(tap9101i0d0) entering forwarding state
Apr 18 09:06:56 myserver kernel: vmbr0: port 2(tap9101i0d0) entering disabled state
Apr 18 09:07:00 myserver proxwww[4578]: Starting new child 4578
Apr 18 09:07:37 myserver proxwww[4585]: Starting new child 4585
Apr 18 09:08:06 myserver ntpd[3145]: synchronized to 88.190.16.52, stratum 2
i am particularly intrigued by the statement of:

kvm: enabling virtualization on CPU0 failed


in the log message, since KVM seems to be enabled on this machine.


other details on this installation:
pveversion
pve-manager/1.8/5754

Code:
 dpkg --get-selections | grep pve
libpve-storage-perl                install
pve-firmware                    install
pve-headers-2.6.32-4-pve            install
pve-kernel-2.6.32-4-pve                install
pve-kernel-2.6.35-1-pve                install
pve-manager                    install
pve-qemu-kvm                    install


besides downgrading to previous version of kernel. is there any suggestion on how to fix this behaviour?

please let me know if you require further info to help.

many thanks,


Nicolas
 
Last edited: