From: Tony Jones <tony@immunix.com>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen "restarting system" on Fedora FC4
Date: Wed, 2 Mar 2005 12:10:40 -0800 [thread overview]
Message-ID: <20050302201040.GA13446@immunix.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503021505190.1691@chimarrao.boston.redhat.com>
On Wed, Mar 02, 2005 at 03:06:17PM -0500, Rik van Riel wrote:
> On Wed, 2 Mar 2005, Tony Jones 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 ...
Correct. I wasn't expecting to need one for fs.
Mark was referring to needing one for the console (udev).
Whether the "Warning: unable to open an initial console." message has
any bearing on the fact that the machine reboots a little later after
SELinux starts I'm unsure of. I was assuming it wasn't related ~shrug~
Can I blame SELinux :)
Tony
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-02 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 19:39 Xen "restarting system" on Fedora FC4 Tony Jones
2005-03-02 19:44 ` Mark Williamson
2005-03-02 19:51 ` Rik van Riel
2005-03-02 20:00 ` Tony Jones
2005-03-02 20:06 ` Rik van Riel
2005-03-02 20:10 ` Tony Jones [this message]
2005-03-02 20:11 ` Mark Williamson
2005-03-02 20:59 ` Tony Jones
2005-03-02 23:38 ` nils toedtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050302201040.GA13446@immunix.com \
--to=tony@immunix.com \
--cc=riel@redhat.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.