From: Sander Eikelenboom <linux@eikelenboom.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]
Date: Wed, 15 Jun 2016 10:57:03 +0200 [thread overview]
Message-ID: <1104389404.20160615105703@eikelenboom.it> (raw)
In-Reply-To: <57612E1102000078000F5229@prv-mh.provo.novell.com>
Wednesday, June 15, 2016, 10:29:37 AM, you wrote:
>>>> On 15.06.16 at 01:49, <linux@eikelenboom.it> wrote:
>> Just tested latest xen-unstable 4.8 (xen_changeset git:d337764),
>> but one of the latest commits seems to have broken boot of HVM guests
>> (using qemu-xen) previous build with xen_changeset git:6e908ee worked
>> fine.
> Primary suspects would seem to be 67fc274bbe and bfa84968b2,
> but (obviously) I didn't see any issues with them in my own
> testing, so could you
> - instead of doing a full bisect, revert just those two
Will give reverting that a shot.
> - clarify what specific things you're having your guest(s) do that
> I may not have done with just "ordinary" guests?
That was what i was also wondering about, but it is an ordinary guest, no pci
passthrough or something funky.
Perhaps an Intel vs AMD (this machine has a AMD phenom X6) issue ?
--
Sander
> And then of course this domain_crash() could of course be
> accompanied by some helpful printk() ...
> Thanks, Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-15 8:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 23:49 Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>] linux
2016-06-15 8:29 ` Jan Beulich
2016-06-15 8:57 ` Sander Eikelenboom [this message]
2016-06-15 9:38 ` Sander Eikelenboom
2016-06-15 10:12 ` Jan Beulich
2016-06-15 12:00 ` Sander Eikelenboom
2016-06-15 12:48 ` Jan Beulich
2016-06-15 13:58 ` Sander Eikelenboom
2016-06-15 14:07 ` Jan Beulich
2016-06-15 14:20 ` Boris Ostrovsky
2016-06-15 14:32 ` Boris Ostrovsky
2016-06-15 14:39 ` Jan Beulich
2016-06-15 14:56 ` Boris Ostrovsky
2016-06-15 15:22 ` Jan Beulich
2016-06-15 15:29 ` Paul Durrant
2016-06-15 15:43 ` Jan Beulich
2016-06-15 15:46 ` Paul Durrant
2016-06-15 15:54 ` Jan Beulich
2016-06-15 16:46 ` Boris Ostrovsky
2016-06-16 8:03 ` Jan Beulich
2016-06-15 14:35 ` Jan Beulich
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=1104389404.20160615105703@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=JBeulich@suse.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).