xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Atom2 <ariel.atom2@web2web.at>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: HVM domains crash after upgrade from XEN 4.5.1 to 4.5.2
Date: Mon, 16 Nov 2015 10:02:21 +0000	[thread overview]
Message-ID: <5649A9AD.9060809@citrix.com> (raw)
In-Reply-To: <564925B7.4090801@web2web.at>


[-- Attachment #1.1: Type: text/plain, Size: 2035 bytes --]

On 16/11/15 00:39, Atom2 wrote:
> Am 15.11.15 um 16:12 schrieb Andrew Cooper:
> [big snip]
>> Great - so confirms the issue as a SeaBIOS interaction issue, rather
>> than a hypervisor regression.
>>
>> As I said before, I am still certain that a guest should not be able
>> to get itself into the crashing state (short of a hardware errata),
>> so I still suspect that there is a latent hypervisor emulation bug
>> which has been tickled by the SeaBIOS update.
>>
>> Would you please mind running the bad HVMLoader on Xen 4.5.2 with
>> hvm_debug=0xc3f ? I am still hoping that that will shed some light on
>> SeaBIOS actions just leading up to the crash.
> Hi Andrew,
> Please see the attached two files. One is the dmesg from booting the
> system. This looks pretty normal in my view. The other is the output
> of "xl dmesg" which is most likely what you were after. It's probably
> worth noting that the "traps.c" output between lines 259 and 314 and
> again between lines 346 and 353 seem to be xen-4.5.2 specific and
> don't show up under xen-4.5.1, but that may not be of any relevance
> for the SeaBIOS issue we are experiencing. Though I'd still be
> interested to know whether that's anything for me to worry about ...

Sorry, but you need to be using a debug build of Xen.  The internals of
hvm_debug are not compiled in a regular build.

I am also only interested in `xl dmesg`.  There will be lots of log
lines prefixed with [HVM:$DOMID.$VCPUID].

>>
>> Are you able to experiment with newer versions of Xen?  It would be
>> interesting to see whether the issue is still present in Xen 4.6
> Currently xen-4.6 is not stable in gentoo and I try to stick to stable
> packages as much as possible. But in case the above does not help you
> any further, I am happy to give this a try as well. Would this just be
> a straightforward test to see whether it works at all or would you
> require debug symbols as well?

That's ok.  It is unlikely that this issue has been fixed since, so I
suspect that it is still present.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 3003 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-11-16 10:02 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 [this message]
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
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=5649A9AD.9060809@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ariel.atom2@web2web.at \
    --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).