Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem"

[0bo0 <0.bugs.only.0@gmail.com>]

On Sat, Jan 23, 2010 at 10:19 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 23/01/2010 17:43, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
>
>>> xm create -c /home/xen/vm/test.cfg
>>>   Using config file "/home/xen/vm/test.cfg".
>>>   Error: Domain 'test' does not exist.
>>>
>>> xend log -> http://pastebin.com/d6c5d3100.  if something 'in there' is
>>> informative, hth!
>>>
>>
>> It seems the guest crashes:
>> [2010-01-23 09:23:11 4595] WARNING (XendDomainInfo:2072) Domain has crashed:
>> name=test id=6.
>
> 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=test id=1.
[2010-01-25 22:41:11 4493] DEBUG (XendDomainInfo:3061)
XendDomainInfo.destroy: domid=1
[2010-01-25 22:41:15 4493] DEBUG (XendDomainInfo:2416) Destroying device model
...

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.