New Kernel - cannot start VM

L

ltor

Member
Jun 1, 2010
35
0
6
Hello,

Recently, I did the upgrade of Proxmox via apt-get upgrade.
I stopped the VMs and rebooted the physical server.
With the last kernel selected, I was not able anymore to start our VMs (log -> cannot start VM)
I have seen some troubles about this last kernel ans patches about udev ont OpenVz Forum and so I decided to restart using the previous kernel...eveything is OK now...
Am I the only one to face with this behaviour ?

Anyway thanks for Promox !
 
ltor said:
Hello,

Recently, I did the upgrade of Proxmox via apt-get upgrade.
I stopped the VMs and rebooted the physical server.
With the last kernel selected, I was not able anymore to start our VMs (log -> cannot start VM)
I have seen some troubles about this last kernel ans patches about udev ont OpenVz Forum and so I decided to restart using the previous kernel...eveything is OK now...
Am I the only one to face with this behaviour ?

Anyway thanks for Promox !
Click to expand...
Hi,
you know that the 2.6.32 kernel hasn't openvz-support?

Udo
 
Thank you for the answer.

But why the proxmox repository propose such a partially functionnal kernel...promox is essentialy a friendly interface to openvz, isn't it ?
 
The question remains : is it serious to provide a so partially functionnal implementation as un official upgrade ?
 
ltor said:
The question remains : is it serious to provide a so partially functionnal implementation as un official upgrade ?
Click to expand...

The answer is simple. There is no OpenVZ implementation for 2.6.32. The OpenVZ/Debian team is working on that currently. We will include it as soon as they release a stable version.

Proxmox VE is based on 2.6.18. We just provide a 2.6.32 kernel for people who want to use 2.6.32 with KVM and without OpenVZ support.
 
You must log in or register to reply here.
Top Bottom