WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Network problem

This is what it says just before, i was tailing the log

[2010-01-18 15:08:13 2917] DEBUG (XendDomainInfo:1709) 
XendDomainInfo.handleShutdownWatch
[2010-01-18 15:08:13 2917] DEBUG (DevController:139) Waiting for devices vif.
[2010-01-18 15:08:13 2917] DEBUG (DevController:144) Waiting for 0.
[2010-01-18 15:08:13 2917] WARNING (image:493) domain testserver: device model 
failure: pid 2989: exited with nonzero status 1; see 
/var/log/xen/qemu-dm-testserver.log
[2010-01-18 15:08:13 2917] WARNING (XendDomainInfo:1886) Domain has crashed: 
name=testserver id=1.
[2010-01-18 15:08:13 2917] INFO (XendDomainInfo:2091) Preserving dead domain 
testserver (1).
[2010-01-18 15:08:13 2917] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vif/1/0/hotplug-status.



-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@xxxxxxxxx] 
Sent: 18 January 2010 13:57
To: Ian Tobin
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Network problem

On Mon, Jan 18, 2010 at 5:11 PM, Ian Tobin <itobin@xxxxxxxxxxxxx> wrote:
> I have also checked udev is running and the only error in the log that i
> can see is
>
> Traceback (most recent call last):
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 2228, in _releaseDevices
>    self.destroyDevice(true_devclass, dev, False);
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 1148, in destroyDevice
>    rc = self.getDeviceController(deviceClass).destroyDevice(devid,
> force)
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 2249, in getDeviceController
>    raise XendError("Unknown device type: %s" % name)
> XendError: Unknown device type: None
>
> Not sure if that means anything to you?
>

Go back several lines (should be less than one hundred), start looking
from the one where the domain is starting. There might be a more
useful info there, like what it was doing before it throws the error
vif not connected.

-- 
Fajar



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users