From: 0bo0 <0.bugs.only.0@gmail.com>
To: Keir Fraser <keir.fraser@eu.citrix.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: Tue, 26 Jan 2010 16:59:43 -0800 [thread overview]
Message-ID: <c67eed301001261659l70e94964odfeb2db39e1c5958@mail.gmail.com> (raw)
In-Reply-To: <c67eed301001261625p22470fdagb2c41aa45a950882@mail.gmail.com>
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' ]
then the DomU launches OK,
xm list
Name ID Mem VCPUs
State Time(s)
Domain-0 0 1022 1 r----- 119.5
test 8 4096 4
-b---- 17.1
@ DomU ...
uname -a
Linux test 2.6.31.8-0.1-xen #1 SMP 2009-12-15 23:55:40 +0100 x86_64
x86_64 x86_64 GNU/Linux
so, is the parser broken, or has something changed in allowed vfb specification?
next prev parent reply other threads:[~2010-01-27 0:59 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 [this message]
2010-01-27 8:27 ` Keir Fraser
2010-01-27 9:10 ` Keir Fraser
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=c67eed301001261659l70e94964odfeb2db39e1c5958@mail.gmail.com \
--to=0.bugs.only.0@gmail.com \
--cc=keir.fraser@eu.citrix.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).