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

Re: [Xen-users] Manually create Fedora domU on CentOS 5.3 dom0


  • To: Geert Janssens <info@xxxxxxxxxxxx>
  • From: Grant McWilliams <grantmasterflash@xxxxxxxxx>
  • Date: Wed, 23 Sep 2009 15:07:50 -0700
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 23 Sep 2009 15:08:59 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=WeYc9/xdq0VjFvJs9je0UL8e0FV0Vvwncn+t0+AkMjechR99TpTlDkcCWZLbvpKmGm hX+MNq/5Jp2q8EWtaAQk6o/jWTMJ56nuo3/LL+6smRiZF2S7kre0JMf0n1VE646v4zP5 1M4enbXcxmstikXXG/iJYndZ9+6fQkVppHt98=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> I found this thread on xen-users
> http://lists.xensource.com/archives/html/xen-users/2009-06/msg00650.html
> Which refers to an Amazon EC2 tech doc, explaining how to install Fedora on
> a single root filesystem.
>
> Following these instructions, I managed to install fedora 11 on an LVM
> partition. However, when attempting to start this setup as a Xen PV, I get
> this error right after pygrub finishes:
> Error: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only load
> images built for the generic loader or Linux images')
>
> I'm not sure how to proceed here. Is a special initrd required in a PV
> environment ?
>
> More details:
> My environment is all 32 bit (xen, dom0, domU)
> dom0 kernel is 2.6.18-128.1.10.el5.centos.plusxen
> xen is gitco xen 3.3.1
> domU kernel is 2.6.30.5-43.fc11.i586
>
> Geert

Â
You know I'm not sure you're going about this the easiest way. I've never installed on a LVM partition but I do use them.
I'll give you the 4 step process that I would have used. Maybe it doesn't match exactly to what you wanted but it's fast and it works.

1. Download a Fedora Disk Image from Stacklet. http://stacklet.com/downloads/images/list/Fedora
2. Make your LV.
3. Modify the included domU config file to add the LV as a second disk
4. Start the VM and once booted up, format the LV and use it for whatever you want.

I'm sure there's a cleaner way but doing this I can have a working VM in about 15 minutes that's using LVM. For databases it's worth the trouble to use LVM because you gain about 4% in speed on the sql-bench test.

Another thing that is more directly related to your problem is you probably want to be using the kernel from gitco if you're using the gitco xen like this. This might actually solve your problem as apposed to just avoiding it. Here's my grub.conf entry using the gitco xen kernel.

title CentOS (2.6.18-128.4.1.el5xen)
ÂÂÂ root (hd0,0)
ÂÂÂ kernel /xen.gz-3.4.0
ÂÂÂ module /vmlinuz-2.6.18-128.4.1.el5xen ro root=/dev/vgsys/lvroot rhgb quiet
ÂÂÂ module /initrd-2.6.18-128.4.1.el5xen.img


Grant McWilliams
_______________________________________________
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®.