| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] New and Current Xen Systems no longer fully boot and pa
Actually I believe the kernel wasn't updated as it
was one from the openvz repositories which allowed me to run Xen
instances and OpenVZ containers simultaneously on the same system. This
did not update during the 5.3 to 5.4 update.
On 29/10/2009 02:36, Fajar A. Nugraha wrote:
On Wed, Oct 28, 2009 at 7:09 PM, Ricky Burgin <ricky@xxxxxxx> wrote:
Hi Pasi,
Thanks for the response. This seems to have been caused by an update from
CentOS 5.3 to 5.4. I'm not exactly sure what packages were specifically
affected during the update, but after reluctantly rebooting the server, it
came back up and Xen started functioning completely normally. Could quite
easily have been xenconsoled, I suppose.
Xen userland must match the version of hypervisor you're running.
Since upgrading to Centos 5.4 should've include kernel-xen (which also
contain the hypervisor) and xen (the userland), it makes sense that
you have to reboot to have it function properly.
I usually exclude these packages from normal update, and only update
them just before I reboot the server:
kernel kernel-devel kernel-xen kernel-xen-devel xen xen-libs glibc
glibc-common glibc-devel glibc-headers glibc-utils
|
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home