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

Re: [Xen-users] methods of porting RHEL PV guests to real hardware

  • To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • Date: Wed, 24 Jun 2009 09:02:36 +0700
  • Delivery-date: Tue, 23 Jun 2009 19:03:24 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Wed, Jun 24, 2009 at 8:42 AM, Thaddeus Hogan<thaddeus@xxxxxxxxxx> wrote:
>> ----- "Ray Barnes" <tical.net@xxxxxxxxx> wrote:
>> But how to get an initrd that closely matches the real hardware
>> without *a lot* of trial and error whilst manually specifying the
>> kernel modules that you think the real box will use?
> Of course an easy, if not somewhat brute force way to do this is to install 
> RHEL on the target and then copy most of the filesystem over (bin, sbin, usr, 
> opt, var, etc, and lib <- but don't whack the existing modules dir).

Yup, that's the most reliable method. I usually use LVM and have the
"original" root filesystem and the one from domU on separate LV.

> I would start with scsi_mod, sd_mod, dm_mod, and then any specific hardware 
> module for your HBA.  For specific hardware, it may take some research to 
> identify the module name and all dependencies without having a system running 
> those modules.

copying /etc/modprobe.conf from a real physical machine to domU, and
regenerate initrd should be able to handle most hardware drivers. LVM
is another thing though, so it's easier to simply use a working initrd
(the previous method).


Xen-users mailing list



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