xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 27 Jan 2010 07:41:19 -0800	[thread overview]
Message-ID: <c67eed301001270741i4870c87ey478f152ec90bc289@mail.gmail.com> (raw)
In-Reply-To: <C785B377.7830%keir.fraser@eu.citrix.com>

hi

On Wed, Jan 27, 2010 at 1:10 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> 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?

yes, it's suse-specific (it's already been requested that they support
pvgrub ...)

but, doesn't seem like the issue :-/

removing the use of the domUloader.py bootloader

     builder      = 'linux'
-    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.

thanks.

  reply	other threads:[~2010-01-27 15:41 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 [this message]
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=c67eed301001270741i4870c87ey478f152ec90bc289@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).