All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: xen-devel@lists.sourceforge.net
Subject: Re: [Fwd: Installing from distribution CDs]
Date: Wed, 02 Feb 2005 14:04:19 -0600	[thread overview]
Message-ID: <42013243.4020401@codemonkey.ws> (raw)
In-Reply-To: <1107373210.17156.12.camel@localhost>

This patch was not meant for inclusion but I still should have put this 
for good measure:

Signed-off-by: Anthony Liguori

Anthony Liguori wrote:

>On Wed, 2005-02-02 at 12:39, Jared Rhine wrote:
>  
>
>>I don't think so; the bottom of my /linuxrc execs /sbin/init.  This
>>marks the end of the standard initrd process of doing a pivot-root and
>>getting on with life.  It doesn't have to be an either/or between
>>linuxrc and init.
>>    
>>
>
>This is likely to support older kernels as initrd does a pivot for you.
>
>  
>
>>As mentioned, I can't speak to the innards, but I can offer solid
>>proof that I need an init=/linuxrc on my boot line, and that this
>>snippet would not be needed if I wasn't using a Xen'ed kernel.  On a
>>regular kernel, the /linuxrc is found and used automatically in
>>preference to /sbin/init, if it is present.
>>    
>>
>
>Now here's something for you to do which should be confusing as the
>solution.  Add a root=/dev/hdc or whatever to your command line and I
>bet it will work without the init=/linuxrc.
>
>Apparently what's happening is that at some point during the domain boot
>process, Xen decides that the root device is /dev/ram0 if there is no
>root= command line on the kernel.  In
>init/do_mounts_rd.c:rd_load_image() if the ramdisk loads to what it
>thinks is the root device, the initrd actions are never taken.
>
>Of course, patching that function to remove that check results in the
>same behavior.  I've not yet tracked down what's going on but that's the
>problem.
>
>I've also included a new patch against a recent xen-unstable.  It's
>another proof-of-concept one.  This time, I can actually start a rescue
>CD properly (which means initrd is working with SLES-9).  The distro
>install doesn't work though.  However, another 2.6-based distro might
>have more luck.
>
>Regards,
>
>  
>

-- 
Anthony Liguori
anthony@codemonkey.ws



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  reply	other threads:[~2005-02-02 20:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02  8:51 [Fwd: Installing from distribution CDs] Ian Pratt
2005-02-02 11:31 ` Jared Rhine
2005-02-02 15:03   ` Anthony Liguori
2005-02-02 18:39     ` Jared Rhine
2005-02-02 19:40       ` Anthony Liguori
2005-02-02 20:04         ` Anthony Liguori [this message]
2005-02-02 14:57 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2005-02-09  1:47 Ian Pratt
2005-02-09  2:11 ` Anthony Liguori
2005-02-09  0:11 Ian Pratt
2005-02-09  1:00 ` Anthony Liguori
2005-02-09 22:56   ` Jared Rhine
2005-02-02 22:26 Ian Pratt
2005-02-03  2:16 ` Anthony Liguori
2005-02-03  4:07   ` Christian Limpach
2005-02-03  4:52     ` Anthony Liguori
2005-02-03 10:54       ` Christian Limpach
2005-01-11 20:48 Anthony Liguori

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=42013243.4020401@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.