xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: 0bo0 <0.bugs.only.0@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core dump failed"
Date: Wed, 27 Jan 2010 09:10:15 +0000	[thread overview]
Message-ID: <C785B377.7830%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C785A973.7825%keir.fraser@eu.citrix.com>

On 27/01/2010 08:27, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

>> On Tue, Jan 26, 2010 at 4:25 PM, 0bo0 <0.bugs.only.0@gmail.com> wrote:
>>> #1  0x0000000000464082 in xenstore_parse_domain_config ()
>> 
>> making note of the 'domain_config' ...
>> 
>> if in test.cfg i change,
>> 
>>  -   vfb          = [ 'type=vnc, vncdisplay=102, vnclisten=127.0.0.1' ]
>>  +   #vfb          = [ 'type=vnc, vncdisplay=102, vnclisten=127.0.0.1' ]
> 
> Maybe I can repro the crash.

I had a go but couldn't reproduce the qemu crash. I did note however that
your PV guest only gets a qemu-dm process when you include the vfb config
line above. Hence the crash is not really related to vfb directly, but
simply the fact that qemu starts up and then crashes for some other bizarre
reason. I tried reproducing a vbd config similar to yours (since your crash
backtrace indicated crashing in blockdevice-parsing code), but that caused
no problems for me.

I don't know whether it could be related to the domUloader.py bootloader
stuff. I've never used that and I think it's suse specific?

 -- Keir

  reply	other threads:[~2010-01-27  9:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 18:36 trying to debug xen4 & qemu-dm, Xen reports "core dump failed" 0bo0
2010-01-26 18:36 ` Konrad Rzeszutek Wilk
2010-01-26 18:55   ` 0bo0
2010-01-26 21:10 ` Keir Fraser
2010-01-26 21:25   ` 0bo0
2010-01-26 21:38     ` Keir Fraser
2010-01-26 22:12       ` 0bo0
2010-01-26 22:30         ` Keir Fraser
2010-01-26 22:47           ` 0bo0
2010-01-27  0:25             ` 0bo0
2010-01-27  0:59               ` 0bo0
2010-01-27  8:27                 ` Keir Fraser
2010-01-27  9:10                   ` Keir Fraser [this message]
2010-01-27 15:41                     ` 0bo0
2010-01-27 15:46                       ` Keir Fraser
2010-01-27 16:19                         ` Sander Eikelenboom
2010-01-27 16:22                           ` 0bo0
2010-01-27 16:40                             ` 0bo0
2010-01-28 22:08                               ` 0bo0
2010-01-27 16:20                         ` 0bo0
2010-01-27  8:27               ` Keir Fraser
2010-01-29  0:21 ` Justin T. Gibbs
2010-01-29  0:42   ` 0bo0
2010-01-29  0:44     ` Justin T. Gibbs
2010-01-29  0:54       ` 0bo0

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=C785B377.7830%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=0.bugs.only.0@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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).