[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-users
Subject:    RE: [Xen-users] RHEL5 as PVM on RHEL5 xen
From:       "Petersson, Mats" <Mats.Petersson () amd ! com>
Date:       2007-03-30 14:55:24
Message-ID: 907625E08839C4409CE5768403633E0B018E1B61 () sefsexmb1 ! amd ! com
[Download RAW message or body]

 

> -----Original Message-----
> From: Nico Kadel-Garcia [mailto:nkadel@gmail.com] 
> Sent: 30 March 2007 15:52
> To: Petersson, Mats
> Cc: trilok nuwal; Daniel P. Berrange; Xen list
> Subject: Re: [Xen-users] RHEL5 as PVM on RHEL5 xen
> 
> Petersson, Mats wrote:
> >  
> >> ---Original Message-----
> >> From: xen-users-bounces@lists.xensource.com 
> >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> >> trilok nuwal
> >> Sent: 30 March 2007 14:02
> >> To: Daniel P. Berrange
> >> Cc: Xen list
> >> Subject: Re: [Xen-users] RHEL5 as PVM on RHEL5 xen
> >>
> >> Yes, could you please tell me the way i shuld make the initrd.
> >> I did in this way but it is not right as it dont have 
> >> anything for the frontend drivers as you mentioned.
> >>
> >> /sbin/mkinitrd /boot/initrdimg 2.6.18-8.el5xen
> >>     
> >
> > Assuming that Fedora and RHEL have similar enough syntax 
> [which is very
> > likely, as they originate from the same source], you need to add
> > "--with=netfront" and "--with=blkfront" or something similar to that
> > (e.g. you may need to specify .ko on the name of the module). 
> >   
> You don't need network drivers to *boot*. He's got other 
> problems going 
> on: the initrd is a red herring.

That's correct, but you DO need a "blkfront" driver, as that's the way
that the guest is reading the "hard-disk" via Dom0. And you DON'T need
one of those for Dom0, since Dom0 has access to the real hardware. 

--
Mats
> 
> 
> 



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

[prev in list] [next in list] [prev in thread] [next in thread]