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 15:46:40 +0000 [thread overview]
Message-ID: <C7861060.78F9%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <c67eed301001270741i4870c87ey478f152ec90bc289@mail.gmail.com>
On 27/01/2010 15:41, "0bo0" <0.bugs.only.0@gmail.com> wrote:
> - bootloader = '/usr/lib/xen/boot/domUloader.py'
> - bootargs = '--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'
> + kernel = '/home/xen_store/distros/opensuse112/xenboot/vmlinuz-xen'
> + ramdisk = '/home/xen_store/distros/opensuse112/xenboot/initrd-xen'
>
> still results on the same problem/crash -- as lang as
>
> vfb = ['']
>
> exists. again, simply removing the vfb spec'n allows the DomU to sanely boot.
Hm, well, can you try stripping your config file right back (but still
specifying vfb=['']) -- like removing all vbds for example? Obviously your
guest will not successfully boot, but qemu-dm crashing is no doubt
preventing your guest from even starting in the first place. So you can
strip back and see whether at any point behaviour changes from 'qemu-dm
crashes' to 'guest partially boots but then fails to find a rootfs'.
-- Keir
next prev parent reply other threads:[~2010-01-27 15:46 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
2010-01-27 15:41 ` 0bo0
2010-01-27 15:46 ` Keir Fraser [this message]
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=C7861060.78F9%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).