Installing Ubuntu10.4 as a KVM not as a container

Paulodm

New Member
Sep 16, 2010
1
0
1
Hi all,

New to the world of virtualisation. I've managed to get windows server virtuals up and running easily using PROXMOX. Thanks for an excellent tool.

I'm trying to get an Ubuntu10.4 installed as a KVM and not a container. Is this possible? I was hoping (from my understanding) that KVM runs completely in its own virtual space and had hoped the kernel issues with the base debian kernel wouldnt make a difference.

the install however just sits permanently at 100% CPU.

Any ideas?
 
Ubuntu 10.04 works perfectly as KVM guest.

Pls post the output of 'pveversion -v', maybe you use some old packages.
 
I have a similar issue. I have a kvm running ubuntu 10.04. I have installed a web server on it and everything was working fine for weeks. Today, I looked at that vm and the cpu was stuck at 96% utilization. Reboot it, open the vnc console and saw that it was hanging just after the message "booting on hard drive" (CPU at 96% again). I have inserted a live ubuntu 10.04 ISO on that VM to see if there was some syslog but the live image has the same issue! I am able to choose the language for the live CD but when I select "Try ubuntu", the CPU hangs at 96%...

What could be the cause of that problem?
 
I tried to Disable ACPI and Disable KVM without any changes. Strange problem. It seems to get stuck just before the start of Grub... Is there a way to do a checkdisk on a qcow2 image?
 
pls also post the output of 'pveversion -v'
 
Ho yes your right... this vm is on a:
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-2-pve
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
 
this list is not complete, you do not have all packages - to fix pls run the following:

Code:
aptitude update

aptitude safe-upgrade 

aptitude install proxmox-ve-2.6.18

finally you should have this (you need to reboot to activate the new kernel):

Code:
proxmox-7-121:~# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-3-pve
proxmox-ve-2.6.18: 1.6-6
pve-kernel-2.6.18-3-pve: 2.6.18-6
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-6
proxmox-7-121:~#
 
Thanks dietmar and tom.

I followed tom procedure and ends up with a working configuration.

Thanks again!