xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Sundstrom <sunkan+lists.xen-devel@zappa.cx>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] XEN domU crash when PV grub chainloads 32-bit domU grub
Date: Tue, 22 Sep 2015 13:26:11 +0000	[thread overview]
Message-ID: <20150922132611.Horde.ddrVf5nBPTIgMpU8wnaYWqY@apache.zappa.cx> (raw)
In-Reply-To: <560101D2.5060005@citrix.com>


Citerar Andrew Cooper <andrew.cooper3@citrix.com>:

> On 21/09/2015 21:03, Andreas Sundstrom wrote:
>> Using 64-bit dom0 and 32-bit domU PV (para-virtualized) grub sometimes
>> fail when chainloading the domU's grub. 64-bit domU seem to work 100%
>> of the time.
>
> You say sometimes.  Do you mean that repeated attempts to boot a 32bit
> domU causes it to ether boot correctly, or die in the below manor?

Yes that is correct, it may or may not be able to complete the booting.

>> When it fails "xl create vm -c" outputs this:
>> Parsing config from /etc/xen/vm
>> libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain
>> type for domid=16
>> Unable to attach console
>> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console
>> child [0] exited with error status 1
>
> These error messages are just because the domain crashes sufficiently
> early that libxl can't find the console information.  Running `xl
> create` without '-c' would remove the libxl errors.

Correct, they only appear due to the failed connecting of the console
so not really relevant to the actual issue.

>> I am unable to understand how to debug grub further on my own, I have
>> printed out text from grub so that I understood that it is the
>> chainload that fails. I see no output from the domU grub (except when
>> it works as it should of course). I can help with further testing if
>> needed.
>
> It does appear to be an intermittent bug in 32bit grub-xen in the
> eventual domU, but I have no help to offer with respect to debugging
> grub-xen further.
>
> ~Andrew

As Ian Campbell suggested I have also filed a bug with upstream grub:
http://savannah.gnu.org/bugs/?46014

/Andreas

  parent reply	other threads:[~2015-09-22 13:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 20:03 [BUG] XEN domU crash when PV grub chainloads 32-bit domU grub Andreas Sundstrom
2015-09-22  7:22 ` Andrew Cooper
2015-09-22  8:52   ` Ian Campbell
2015-09-22 13:26   ` Andreas Sundstrom [this message]
2015-09-22  8:53 ` Ian Campbell
2015-09-22 22:37 ` Samuel Thibault
2015-09-23  8:34   ` Ian Campbell
2015-09-23 12:47     ` Andreas Sundstrom
2015-09-23 14:18       ` Ian Campbell
2015-09-24 17:28         ` Andreas Sundstrom
2015-09-25  8:36           ` Ian Campbell
2015-09-25 13:23             ` Andreas Sundstrom
2015-09-23  8:37   ` Andreas Sundstrom
     [not found] ` <1442912018.10338.118.camel@citrix.com>
2016-01-22 12:56   ` Vladimir 'φ-coder/phcoder' Serbinenko
     [not found]   ` <56A226F8.3020301@gmail.com>
2016-01-22 13:01     ` Andrew Cooper
     [not found]     ` <56A22847.3020708@citrix.com>
2016-01-22 13:08       ` Vladimir 'φ-coder/phcoder' Serbinenko
     [not found]       ` <56A229DA.7030904@gmail.com>
2016-01-22 13:43         ` Andrew Cooper
2016-01-22 17:44     ` Andreas Sundstrom

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=20150922132611.Horde.ddrVf5nBPTIgMpU8wnaYWqY@apache.zappa.cx \
    --to=sunkan+lists.xen-devel@zappa.cx \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).