On Wed, May 25, 2011 at 1:42 AM, M A Young <m.a.young@durham.ac.uk> wrote:

On Wed, 25 May 2011, Lefu Ntho wrote:

and correctly so, Michael, that --oldpackage did the trick, thanx a lot, I
have bravely removed previously installed xen and kernel, I then reinstalled
xen and kernel-2.6.32.39 via yum, rebooted the machine remotely, I executed
uname -r and 2.6.32.39-175.xendom0.fc13.x86_64 is returned :)

but
vm info
Error: Unable to connect to xend: No such file or directory. Is xend
running?

Did you edit grub.conf to allow the kernel to boot via the hypervisor? That kernel doesn't do it for you. You want something along the lines of

Title something
root (hd?,?)
kernel /xen.gz or /boot/xen.gz
module /vmlinuz-something kernel_boot_args
module /initramfs-something

adjusted to match your boot environment as given by the other grub entries.

Michael Young