From mboxrd@z Thu Jan 1 00:00:00 1970 From: 0bo0 <0.bugs.only.0@gmail.com> Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem" Date: Mon, 25 Jan 2010 22:50:07 -0800 Message-ID: References: <20100123174333.GW2861@reaktio.net> 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: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Sat, Jan 23, 2010 at 10:19 AM, Keir Fraser w= rote: > On 23/01/2010 17:43, "Pasi K=E4rkk=E4inen" wrote: > >>> xm create -c /home/xen/vm/test.cfg >>> =A0 Using config file "/home/xen/vm/test.cfg". >>> =A0 Error: Domain 'test' does not exist. >>> >>> xend log -> http://pastebin.com/d6c5d3100. =A0if something 'in there' i= s >>> informative, hth! >>> >> >> It seems the guest crashes: >> [2010-01-23 09:23:11 4595] WARNING (XendDomainInfo:2072) Domain has cras= hed: >> name=3Dtest id=3D6. > > Qemu-dm dies on SIGSEGV. Seems like I may have not much choice but to start diving into 4.0. That siad, where do I look to get a handle on this? ... [2010-01-25 22:41:11 4493] DEBUG (XendDomainInfo:1892) XendDomainInfo.handleShutdownWatch [2010-01-25 22:41:11 4493] WARNING (image:561) domain test: device model failure: pid 5288: malfunctioning (closed sentinel), killed; see /var/log/xen/qemu-dm-nas.log [2010-01-25 22:41:11 4493] WARNING (XendDomainInfo:2072) Domain has crashed: name=3Dtest id=3D1. [2010-01-25 22:41:11 4493] DEBUG (XendDomainInfo:3061) XendDomainInfo.destroy: domid=3D1 [2010-01-25 22:41:15 4493] DEBUG (XendDomainInfo:2416) Destroying device mo= del ... checking, cat /var/log/xen/qemu-dm-nas.log domid: 1 Warning: vlan 0 is not connected to host network Using xvda for guest's hda doesn't tell me much of what to do. any suggestions, or further info I can provide here? thanks.