XenServer Converting HVM to Parravirtualised

Hi everyone,

Recently I have been tasked with the daunting process of converting a setup of HVM enabled VMs (running on Citrix XenServer 5.6.0) into PV (paravirtualised) containers.

The constraints of the project was that:

1) The operating system must be functionally identical after the migration. 2) minimal modification to the operating system (with exception of kernel / drive mapping)

I also was allowed to change the bootloader(ie, grub) in what ever way I see fit.

However, I have attempted this, I will firstly like to show you my steps I took.

This at the moment is CentOS5.5 specific:

---Steps:

1) yum install kernel-xen

This installed: 2.6.18-194.32.1.el5xen

2) edited: /boot/grub/menu.lst changed my specs to match:

title CentOS (2.6.18-194.32.1.el5xen)

root (hd0,0)

kernel /vmlinuz-2.6.18-194.32.1.el5xen ro root=/dev/VolGroup00/LogVol00 console=xvc0

initrd /initrd-2.6.18-194.32.1.el5xen.img

Then I changed my xenserver parameters to match:

xe vm-param-set uuid=[vm uuid] PV-bootloader-args="--kernel /vmlinuz-2.6.18-194.32.1.el5xen --ramdisk /initrd-2.6.18-194.32.1.el5xen.img"

xe vm-param-set uuid=[vm uuid] HVM-boot-policy=""

xe vm-param-set uuid=[vm uuid] PV-bootloader=pygrub

xe vbd-param-set uuid==[Virtual Block Device/VBD uuid] bootable=true

Some things to note, I am running a VolGroup LVM ;)

Anyways, after all these steps (which aren't much!) I boot the VM and it boots initial kernel just fine, however I am presented with this error:

-----------------BOOT SCREEN-------------------
device-mapper: dm-raid45: initialized v0.2594l

Waiting for driver initialization.

Scanning and configuring dmraid supported devices

Scanning logical volumes

Reading all physical volumes. This may take a while...

Activating logical volumes

Volume group "VolGroup00" not found

Creating root device.

Mounting root filesystem.

mount: could not find filesystem '/dev/root'

Setting up other filesystems.

Setting up new root fs

setuproot: moving /dev failed: No such file or directory

no fstab.sys, mounting internal defaults

setuproot: error mounting /proc: No such file or directory

setuproot: error mounting /sys: No such file or directory

Switching to new root and running init.

unmounting old /dev

unmounting old /proc

unmounting old /sys

switchroot: mount failed: No such file or directory

-----------/ENDBOOT-----------------

Now my hints are that it cannot detect / because of the fact that when you change from HVM mode to PV it does something (not that obvious)

When you make a SR (storage) on a HVM, you get it mounted to the guest os as /dev/hda.

However in PV mode, this presents itself as /dev/xvda...

Could this be the answer? and if so, how the heck to I implement it??

I am truly stumped at this point :)

--Karl.
LVL 1
crucial_paradigmAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

crucial_paradigmAuthor Commented:
Update: so I have gotten a bit further in my quest, as it now detects the LVM's...

To do this, I required to recompile the xen-kernel initrd image.

Command: mkinitrd -v --builtin=xen_vbd --preload=xenblk initrd-2.6.18-194.32.1.el5xen.img 2.6.18-194.32.1.el5xen

Now when I boot I get this:

-------------------------BOOT-------------------

Loading dm-raid45.ko module

device-mapper: dm-raid45: initialized v0.2594l

Scanning and configuring dmraid supported devices

Scanning logical volumes

Reading all physical volumes. This may take a while...

Found volume group "VolGroup00" using metadata type lvm2

Activating logical volumes

3 logical volume(s) in volume group "VolGroup00" now active

Creating root device.

Mounting root filesystem.

mount: error mounting /dev/root on /sysroot as ext3: Device or resource busy

Setting up other filesystems.

Setting up new root fs

setuproot: moving /dev failed: No such file or directory

no fstab.sys, mounting internal defaults

setuproot: error mounting /proc: No such file or directory

setuproot: error mounting /sys: No such file or directory

Switching to new root and running init.

unmounting old /dev

unmounting old /proc

unmounting old /sys

switchroot: mount failed: No such file or directory

Kernel panic - not syncing: Attempted to kill init!

Anyone have any thoughts on this?? nudge nudge??

--Karl.
0
crucial_paradigmAuthor Commented:
Gathering no one wants to answer this?
0
crucial_paradigmAuthor Commented:
Shame no one answered this. closing this as I have now worked it out.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
crucial_paradigmAuthor Commented:
No one answered.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.