[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Domain0 booting on LVM device

Ok, this may be a dumb question, but I wasn't aware I was using an initrd image ... I don't see any evidence of it in my menu.lst.

I have built my xen0 kernel with everything static (I don't do a lot of modules).

In my .config, I have "CONFIG_BLK_DEV_DM=y" ... shouldn't that take care of it?

What's really bizare is that I can create guests over LVM LV's with the same kernel....


Robin Green wrote:

On Mon, 21 Feb 2005, Puthiyaparambil, Aravindh wrote:

I have Domain 0 booting off an LVM volume. It works fine.

Same here.

You most likely don't have an initrd image that has the Device Mapper
modules built into it. I don't have much experience with Debian but with
SLES9 the mk_initrd script does this for you as long as you have
compiled the dom0 kernel with the "Device Mapper support" as modules.

In Fedora-type systems it's mkinitrd. If you don't use the same type of
root filesystem on the domU kernel as on the dom0 kernel, you may need to mount the domU / filesystem TEMPORARILY and use the --fstab option to mkinitrd to specify domU's /etc/fstab.

I also had to uncompress my initrd image using gunzip.

Weird, I didn't have to do that with Fedora. What error did you get when you tried to boot with it uncompressed?

As a result of
this I had to increase the size of the initial RAM disk (under Block
Devices) in the dom0 kernel.


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.