From mboxrd@z Thu Jan 1 00:00:00 1970 From: 0bo0 <0.bugs.only.0@gmail.com> Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core dump failed" Date: Wed, 27 Jan 2010 07:41:19 -0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 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: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org hi On Wed, Jan 27, 2010 at 1:10 AM, Keir Fraser 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.