From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core dump failed" Date: Wed, 27 Jan 2010 15:46:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: 0bo0 <0.bugs.only.0@gmail.com> Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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