All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: 0bo0 <0.bugs.only.0@gmail.com>, "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable & pvops on *Suse distro? successful howto?
Date: Thu, 04 Feb 2010 08:11:30 +0000	[thread overview]
Message-ID: <C79031B2.8F7F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <c67eed301002031119j667ce3a1p4963c38cab01a51@mail.gmail.com>

On 03/02/2010 19:19, "0bo0" <0.bugs.only.0@gmail.com> wrote:

> On Wed, Feb 3, 2010 at 11:04 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>> So the question is why grub doesn't work after you edit /boot/grub/grub.conf
>> ?
>> Sounds like grub.conf gets corrupted/broken.
> 
> if i have two configs in grub -- the PVOPS stanza, as above, and a
> non-pvops stanza -- if i simply change the default to the non-pvops
> stanza, then grub functions normally, the selection menu appears, and
> i can boot with no problems to the non-pvops setup.
> 
> if i repeat, with default to non-pvops, but then *manually* select the
> pvops config & boot it ... *nothing* happens.  the sysem simply stops
> there.  no errors, no console output, no further response.

I haven't seen you post the non-pvops versus pvops grub stanzas for
comparison, but assuming the Xen line in each stanza is identical, it would
be really odd that one gets you Xen boot output and the other doesn't. Are
you setting up Xen to print to serial line in exactly the same way in both
cases?

The only thing I could think of, if the GRUB setup is okay, is that Xen is
messing up with the particular size of pvops kernel+initrd you pass to it.
I.e., a bug where Xen fails really early, before setting up serial line
even. That would make you very unlucky since I can't remember when we last
had such an early bug, but it is possible.

 -- Keir

  parent reply	other threads:[~2010-02-04  8:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 16:53 xen-unstable & pvops on *Suse distro? successful howto? 0bo0
2010-02-03 18:16 ` Pasi Kärkkäinen
2010-02-03 18:40   ` 0bo0
2010-02-03 18:48     ` Pasi Kärkkäinen
2010-02-03 18:55       ` 0bo0
2010-02-03 19:04         ` Pasi Kärkkäinen
2010-02-03 19:19           ` 0bo0
2010-02-03 19:26             ` Pasi Kärkkäinen
2010-02-04  8:11             ` Keir Fraser [this message]
2010-02-04  3:05         ` Konrad Rzeszutek Wilk
2010-02-04  5:34           ` 0bo0
2010-02-03 19:00   ` Boris Derzhavets
2010-02-03 19:15     ` 0bo0

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=C79031B2.8F7F%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=0.bugs.only.0@gmail.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    /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.