From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: xl create crash when using stub domains
Date: Wed, 21 Sep 2011 16:06:52 -0700
Message-ID: <4E7A6E0C.80503@goop.org>
References: <4E729960.2080101@goop.org> <4E793F42.7070803@goop.org>
	<1316595394.3891.105.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1316595394.3891.105.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 09/21/2011 01:56 AM, Ian Campbell wrote:
> On Wed, 2011-09-21 at 02:34 +0100, Jeremy Fitzhardinge wrote:
>> On 09/15/2011 05:33 PM, Jeremy Fitzhardinge wrote:
>>> When I create an HVM domain with stubdom enabled, it crashes at:
>>>
>>> (gdb) run create  -c /etc/xen/f14hv64  vcpus=4 xen_platform_pci=0 'boot="d"'
>>> Starting program: /usr/sbin/xl create  -c /etc/xen/f14hv64  vcpus=4 xen_platform_pci=0 'boot="d"'
>>> [Thread debugging using libthread_db enabled]
>>> Parsing config file /etc/xen/f14hv64
>>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>   Loader:        0000000000100000->000000000017b9ec
>>>   TOTAL:         0000000000000000->000000003f800000
>>>   ENTRY ADDRESS: 0000000000100000
>>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>>   4KB PAGES: 0x0000000000000200
>>>   2MB PAGES: 0x00000000000001fb
>>>   1GB PAGES: 0x0000000000000000
>>> xc: error: panic: xc_dom_bzimageloader.c:588: xc_dom_probe_bzimage_kernel: kernel is not a bzImage: Invalid kernel
> FWIW I don't get this message. It seems unrelated to the issue here but
> makes me curious...

It's generated by xc_dom_probe_bzimage_kernel() when starting a PV
domain with pvgrub or an HVM domain with stubdoms, AFAIKT.  Do you not
see it, or just not do those things?  Seems to me that a "probe"
function shouldn't be making obnoxious noise.

    J