[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Network problem


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
  • Date: Mon, 18 Jan 2010 15:15:31 -0000
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 18 Jan 2010 07:16:51 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcqYRint6Eh3wLA3SCWqP7pr465S3gACtQag
  • Thread-topic: [Xen-users] Network problem

This is the log from the qemu file

domid: 1
qemu: the number of cpus is 1
/etc/xen/qemu-ifup: could not launch network script
Could not initialize device 'tap'

Ian

-----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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.