From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Atom2 <ariel.atom2@web2web.at>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Subject: Re: HVM domains crash after upgrade from XEN 4.5.1 to 4.5.2
Date: Thu, 19 Nov 2015 23:53:01 +0000 [thread overview]
Message-ID: <564E60DD.6000507@citrix.com> (raw)
In-Reply-To: <564E2AC7.3080109@web2web.at>
On 19/11/2015 20:02, Atom2 wrote:
> Am 19.11.15 um 02:06 schrieb Andrew Cooper:
>> Thanks! That is what I was looking for.
>>
>> Sadly, it is less useful than I was hoping. The guest is not appearing
>> to do anything interesting which causes the bad state; it is almost a
>> full second between the previous action of note, and the crash.
>>
>> Can you email me the bad HVMLoader binary please?
> Hi Andrew,
> Sure I can email the binary. What version of the HVMLoader do you want
> me to send to you? Should this be one with the debug option and debug
> symbols or a standard build without any of those? I assume we are
> talking about amd64 - right?
hvmloader is always a 32bit binary, no matter what your host environment
is. I would like any of the ones which reliably crash for you,
preferably debug if that is available.
>
> Given the recent findings do you still want me to boot with minimal
> command line options to rule out an interaction with the options as
> suggested in an earlier answer?
No - this is unnecessary now.
>
> I can certainly do this, but would need to reconfigure certain things
> as both my HVM domUs require PCI passthrough devices (which you have
> stripped off the suggested minimal command line) to be available.
> Failing to see those devices puts those domUs into an unconfigured
> state and they re-start their initial setup process.
Don't worry - Jan figured this out from the disassembly, which I
admittedly missed.
It would be nice to see your vm's .cfg file to help me reproduce the issue.
~Andrew
next prev parent reply other threads:[~2015-11-19 23:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 1:08 HVM domains crash after upgrade from XEN 4.5.1 to 4.5.2 Atom2
2015-11-12 12:52 ` Jan Beulich
2015-11-12 13:01 ` Andrew Cooper
2015-11-12 14:29 ` Atom2
2015-11-12 15:32 ` Jan Beulich
2015-11-12 16:43 ` Andrew Cooper
2015-11-12 23:00 ` Atom2
2015-11-13 7:25 ` Jan Beulich
2015-11-13 10:09 ` Andrew Cooper
2015-11-14 0:16 ` Atom2
2015-11-14 20:32 ` Andrew Cooper
2015-11-15 0:14 ` Atom2
2015-11-15 15:12 ` Andrew Cooper
2015-11-16 0:39 ` Atom2
2015-11-16 10:02 ` Andrew Cooper
2015-11-15 20:12 ` Doug Goldstein
2015-11-16 1:05 ` Atom2
2015-11-16 15:31 ` Konrad Rzeszutek Wilk
2015-11-16 19:16 ` Atom2
2015-11-16 19:25 ` Konrad Rzeszutek Wilk
2015-11-16 19:39 ` Doug Goldstein
2015-11-16 19:47 ` Konrad Rzeszutek Wilk
2015-11-16 19:45 ` Atom2
2015-11-16 23:01 ` Andrew Cooper
2015-11-16 23:10 ` Atom2
2015-11-18 22:51 ` Atom2
2015-11-18 23:17 ` Andrew Cooper
2015-11-19 0:31 ` Atom2
2015-11-19 1:06 ` Andrew Cooper
2015-11-19 20:02 ` Atom2
2015-11-19 23:53 ` Andrew Cooper [this message]
2015-11-24 11:53 ` Atom2
2015-11-19 10:24 ` Jan Beulich
2015-11-19 10:38 ` Andrew Cooper
2015-11-19 19:51 ` Atom2
2015-11-20 7:57 ` Jan Beulich
2015-11-24 10:32 ` Atom2
2015-11-24 10:43 ` Jan Beulich
2015-11-27 22:51 ` Atom2
2015-11-30 9:04 ` Jan Beulich
2015-11-16 19:47 ` Doug Goldstein
2015-11-16 20:14 ` Atom2
2015-11-12 14:12 ` Atom2
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=564E60DD.6000507@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ariel.atom2@web2web.at \
--cc=cardoe@cardoe.com \
--cc=konrad.wilk@oracle.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).