WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump f

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump failed"
From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Date: Wed, 27 Jan 2010 17:19:39 +0100
Cc: 0bo0 <0.bugs.only.0@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 27 Jan 2010 08:20:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7861060.78F9%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Eikelenboom IT services
References: <c67eed301001270741i4870c87ey478f152ec90bc289@xxxxxxxxxxxxxx> <C7861060.78F9%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hmm I could suspect parsing errors for the last comma in the disk option, or 
the empty vif ?


cat /etc/xen/vm/test.cfg
---------------------------------
name         = 'test'
builder      = 'linux'
bootloader   = '/usr/lib/xen/boot/domUloader.py'
bootargs     = '--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'
disk         = [
'phy:/dev/VG0/boot,xvda,w','phy:/dev/VG0/swap,xvdb,w','phy:/dev/VG0/root,xvdc,w',]
boot         = 'c'   #d is cdrom boot, c is disk boot
root         = '/dev/xvdc1'
vif          = ['']
vfb          = [ 'type=vnc, vncdisplay=102, vnclisten=127.0.0.1' ]
extra        = 'textmode=1 xencons=xvc0 elevator=noop'
maxmem       = 4096
memory       = 4096
vcpus        = 4
cpu_cap      = 100
cpu_weight   = 256
localtime    = 0
netif        = 'yes'
on_shutdown  = 'destroy'
on_reboot    = 'restart'
on_crash     = 'destroy'
---------------------------------




Wednesday, January 27, 2010, 4:46:40 PM, you wrote:

> On 27/01/2010 15:41, "0bo0" <0.bugs.only.0@xxxxxxxxx> 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







-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>