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 09:10:15 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable 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 08:27, "Keir Fraser" wrote: >> On Tue, Jan 26, 2010 at 4:25 PM, 0bo0 <0.bugs.only.0@gmail.com> wrote: >>> #1 =A00x0000000000464082 in xenstore_parse_domain_config () >>=20 >> making note of the 'domain_config' ... >>=20 >> if in test.cfg i change, >>=20 >> - vfb =3D [ 'type=3Dvnc, vncdisplay=3D102, vnclisten=3D127.0.0.1' ] >> + #vfb =3D [ 'type=3Dvnc, vncdisplay=3D102, vnclisten=3D127.0.0.1' ] >=20 > Maybe I can repro the crash. I had a go but couldn't reproduce the qemu crash. I did note however that your PV guest only gets a qemu-dm process when you include the vfb config line above. Hence the crash is not really related to vfb directly, but simply the fact that qemu starts up and then crashes for some other bizarre reason. I tried reproducing a vbd config similar to yours (since your crash backtrace indicated crashing in blockdevice-parsing code), but that caused no problems for me. 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? -- Keir