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

Re: [Xen-users] DomU in it's own LVM partition fails to boot CentOS 5.2 Dom0/U


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • From: Peter Hoose <phoose@xxxxxxxxx>
  • Date: Sat, 24 Jan 2009 16:34:28 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 24 Jan 2009 13:35:20 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Qv5Dd5CG9nqkl8Zwhs2G+8Uqm500S0OsqareaSRfvpC75gfEc6NX2atnRc7wznSy40 Q53rR98kDmh5TmTz0z9kFnE5C3LOBAkuWeXvXrG7BZTrzdf01bkHU8lXZKuDbHQHZyza EaKQhODInfeOw703Njez3VEscP97IKrBpcsFw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

All good now, and I definitely see a big performance improvement with partitions vs. tap:

/dev/xvda:
 Timing cached reads:   7856 MB in  2.00 seconds = 3936.95 MB/sec
 Timing buffered disk reads:  306 MB in  3.00 seconds = 101.95 MB/sec


Previously I was getting ~10MB/s with tap.

On Sat, Jan 24, 2009 at 3:48 PM, Peter Hoose <phoose@xxxxxxxxx> wrote:
Never mind, it may have been the mirror, just tried a different one and the install is chugging along smoothly thus far.

Thanks for all of your help!


On Sat, Jan 24, 2009 at 3:35 PM, Peter Hoose <phoose@xxxxxxxxx> wrote:
> Yes. For this purpose, you create one LV on dom0, map it to domU as
> xvda, and install domU like what you'd do with file-based disk image.

Sweet!

Got much closer this time around my new config:


kernel = "/var/lib/xen/boot/CentOS/CentOS_5_x64_vmlinuz"
ramdisk = "/var/lib/xen/boot/CentOS/CentOS_5_x64_initrd.img"
extra = "text"
name = "guest01"
memory = "1024"

disk = [ 'phy:/dev/VolGroup00/guest01,xvda,w', ]
vif = [ 'bridge=xenbr0', ]
vcpus=1
> >
The disk shows up properly now, and in theory, it lets me create partitions on it, format them, etc... But it bombs out as soon as it starts to install with:

Error
The file system-config-securitylevel-tui-1.6.29.1-2.1.el5.x86_64.rpm
cannot be opened.  This is due to a missing file, a corrupt package
or corrupt media.  Please verify your installation source.

If you exit, your system will be left in an inconsistent state that
will likely require reinstallation.

This happens regardless of packages selected, it seems to be the first file each time, this is install from the same mirror that I used with no problems with file based, so it seems to still be something wrong with my disk setup?

Anyways, it's much closer now and past the first big question/issue I had.

If you have any ideas what caused the above error, I'd appreciate it, if not I'll just hack away at it until it works.

Thanks,
  Peter


On Sat, Jan 24, 2009 at 3:29 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Sun, Jan 25, 2009 at 3:19 AM, Peter Hoose <phoose@xxxxxxxxx> wrote:
> I just created a LVM based vbd in my dom0, I want to use
> this as my 'disk' for my domU, which I would create my partitions on. Is
> this possible,

Yes. For this purpose, you create one LV on dom0, map it to domU as
xvda, and install domU like what you'd do with file-based disk image.

> or do I need to create a /boot, / and /swap on my domU and
> share those with dom0 for it to access natively? IE: Does the dom0 see this
> partition as a disk that it can create partitions on, or does it see it just
> like a normal partition?

I'm not quite sure what you mean, but you can do this :
- create two LVs on dom0, map it to domU as xvda1 (for / ) and xvda2
(for swap). You don't need a separate /boot.
- do mkfs.ext3 and mkswap on dom0 directly on that LV (not creating
partition on top of it)
- populate domU's filesystem (for example, by extracting "templates"
like the one from jailtime.org, or by copying from a working domU.)
- create a suitable initrd

Regards,

Fajar



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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