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

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


  • To: Xen users mailing list <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Ray Barnes <tical.net@xxxxxxxxx>
  • Date: Tue, 23 Jun 2009 18:25:11 -0400
  • Delivery-date: Tue, 23 Jun 2009 15:25:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=sKgTj/1psoCN8oPrYQ89CyWqbETSBP814s2zZjvWw5xAdPb+Q+7DlPFPCvuCX16u4p yKaaZdzLs7YQPGQn7tEp6lx3CrZMl+8+PyGBrsuCEhAup9PcJDG22JaS9UYOaxA4POsf 5o5HMr+DQlSKYESq/4V80BFygb0cQ5z3/uN+c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

As the subject states, I'm looking for pointers on porting paravirtualized RHEL guests from Xen back to real hardware.  It seems straight-forward enough - 'yum install kernel' to put a real kernel on the box.  Make sure the menu.lst entries are ok.  Install the grub boot blocks on the hard drive.  Etc. etc.
 
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?
 
-Ray
 
_______________________________________________
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®.