From: Stefan Bader <stefan.bader@canonical.com>
To: Rolu <rolu@roce.org>
Cc: xen-devel@lists.xen.org
Subject: Re: Possible bug, dom0 crash on ubuntu
Date: Mon, 18 Jun 2012 11:00:42 +0200 [thread overview]
Message-ID: <4FDEEE3A.9090302@canonical.com> (raw)
In-Reply-To: <CABs9EjkQS4VbUjPE6mt_P2zCi3JxAT0LaiztiRTEb-SntUnGXQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1872 bytes --]
On 17.06.2012 05:23, Rolu wrote:
> On Sun, Jun 17, 2012 at 5:04 AM, AP <apxeng@gmail.com> wrote:
>>
>> On Jun 16, 2012 5:56 PM, "Rolu" <rolu@roce.org> wrote:
>>>
>>> When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0
>>> crashes. I've included a serial console log below.
>>>
>>> I've used:
>>> Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to
>>> apply the AT_EMPTY_PATH patch from
>>> http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
>>> get it to compile.
>>> Linux 3.2.0-25, which is the default kernel in Ubuntu's repository right
>>> now.
>>> Ubuntu 12.04 Precise
>>>
>>> Booting with the default Xen 4.1 from the Ubuntu repositories works.
>>>
>>> Using the kernel from
>>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/, which is
>>> a mainline Linux kernel (and also more recent) works with my compiled
>>> version of Xen 4.2
>>>
>>> So,
>>> * Is xen 4.2 not happy with the 3.2 kernel I've used?
>>> * Is this due to something Ubuntu modified in their default kernel?
>>> * Is this an issue with Xen?
>>> * Did I break something?
>>
>> This is an issue with the Ubuntu kernel. Check this thread out:
>> http://lists.xen.org/archives/html/xen-devel/2012-05/msg00049.html
>>
This is an issue between libc not checking all flags correctly and a current
hack to work around a bug on older Xen versions.
If I understood correctly there was a fix going into libc but I am also in the
process of changing that hack to prevent those issues. But it will go into 12.10
first and then move backwards.
-Stefan
>> Adding xsave=0 to the Xen kernel line in grub is the workaround.
>>
>
> Indeed, this worked. Thanks!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-06-18 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 0:52 Possible bug, dom0 crash on ubuntu Rolu
2012-06-17 3:04 ` AP
2012-06-17 3:23 ` Rolu
2012-06-18 9:00 ` Stefan Bader [this message]
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=4FDEEE3A.9090302@canonical.com \
--to=stefan.bader@canonical.com \
--cc=rolu@roce.org \
--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).