Re: [Xen-devel] Xen "restarting system" on Fedora FC4

[nils toedtmann <xen-devel@xxxxxxxxxxxxxxxxxx>]

On Wed, Mar 02, 2005 at 12:59:04PM -0800, Tony Jones wrote:
> On Wed, Mar 02, 2005 at 08:11:38PM +0000, Mark Williamson wrote:
> > > > As for the initrd comment from Mark. The domU rpm from RH doesn't
> > > > provide one.  There is one provided by the dom0 rpm.   I'm sure I
> > > > can create one if necessary, I would have expected the RH rpm to do
> > > > it. Do you specify the initrd in the "ramdisk=" config option?
> > >
> > > The domU kernel doesn't usually need an initrd, since
> > > ext3 is compiled in.  Once we have a "boot loader" for
> > > the unprivileged domains, we can get rid of the xen0
> > > and xenU kernels, and have just one kernel-xen ...
> > 
> > I thought the initrd was needed on Fedora so that udev would work?  Is that 
> > not correct?
> 
> Mark/Rik.
> 
> You are correct. I needed an initrd. Perhaps the warning about "unable to open
> console" should be more than a warning :)


There's another solution to provide the initial console
devices, see 

  <http://fedora.redhat.com/docs/udev/>

Mount and chroot into the rootfs (or boot it somehow and 
move udev away: "mkdir /tmp/dev; mount --move /dev /tmp/dev")
Create all devices you need before udev is started:

  /sbin/MAKEDEV null console zero

(maybe "null tty0 zero" would be enough) (If you booted it, 
put udev back in its place: "mount --move /tmp/dev /dev")
No initrds needed anymore.

/nils.

-- 
there is no sig.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel