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>,
	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 01:06:16 +0000	[thread overview]
Message-ID: <564D2088.3020604@citrix.com> (raw)
In-Reply-To: <564D1875.2060601@web2web.at>

On 19/11/2015 00:31, Atom2 wrote:
> Am 19.11.15 um 00:17 schrieb Andrew Cooper:
>> On 18/11/2015 22:51, Atom2 wrote:
>>> Am 17.11.15 um 00:10 schrieb Atom2:
> [big snip]
>>> Hi Andrew,
>>> as promised I have again tried with a debug build and the results are
>>> very mixed. I initially tried to better understand what the debug USE
>>> flag actually does in gentoo and my understanding (after reading the
>>> so called ebuilds) is now that the XEN hypervisor will be built by
>>> adding a gcc option of "debug=y" - and that's what should compile a
>>> debug build - right?
>> Yes indeed.
>>
>>> So I went on and again enabled the debug USE flag plus gdb symbols and
>>> rebuilt the hypervisor in the hope that this created a valid and
>>> working debug build.
>>>
>>> It, however, seems there's another problem lurking somewhere which
>>> only manifests itself when I boot from the debug build of the
>>> hypervisor.
>> You did manage to get at least one decent log from a properly
>> debugbuild.
>>
>> However, all we need is the hvm_debug output.  This patch:
>>
>> ---8<---
>> diff --git a/xen/include/asm-x86/hvm/support.h
>> b/xen/include/asm-x86/hvm/support.h
>> index 05ef5c5..7a8fbb5 100644
>> --- a/xen/include/asm-x86/hvm/support.h
>> +++ b/xen/include/asm-x86/hvm/support.h
>> @@ -28,7 +28,7 @@
>>
>>   #define HVM_DELIVER_NO_ERROR_CODE  -1
>>
>> -#ifndef NDEBUG
>> +#if 1
>>   #define DBG_LEVEL_0                 (1 << 0)
>>   #define DBG_LEVEL_1                 (1 << 1)
>>   #define DBG_LEVEL_2                 (1 << 2)
>> ---8<---
>>
>> Will enable hvm_debug in a non-debug build of hypervisor.  Can you try
>> that please?
> Done. Please find the xl dmesg output attached to this mail. I guess
> this time it is really what you were expecting. Whether it does make
> sense though, might be a different issue. But I am confident in your
> abilities to figure out what's going on.

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?

~Andrew

  reply	other threads:[~2015-11-19  1:06 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 [this message]
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=564D2088.3020604@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).