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

[Xen-users] Networking through dummy0 isnt possible


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Sanjay Upadhyay <glowfriend@xxxxxxxxx>
  • Date: Wed, 14 Dec 2005 20:42:30 +0530
  • Delivery-date: Wed, 14 Dec 2005 15:14:22 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=UlEv5uEobdnhmeg4w0A3Lg4YYuJtM8YbKKUhDZFIvSrvpNhzb6zrgvH27SsWvx4M6qKw5E0sQ6oPxbSi6sFvcMCt8u6JTbUD9L0sg4vJxTX83ikhh3867caJR5gDpSv/Vf1tfRCl971avOVyETdpLkVarIx485UTVPODvnw46lQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,
referreing the docs on
http://www.howtoforge.com/perfect_xen_setup_debian_ubuntu_p6 I had set
up my networking in Xen 2.0.7, and which used to work. However After
updating the Xen to 3.0.0, the same configuration doesnt work any
more..

SU-debian:~# xm create -c debian-1
Using config file "debian-1".
Error: Device 0 (vif) could not be connected. Backend device not found.

When viewed under 'xm list' I can see that the domU is paused. I can
unpause it and run, however network never comes up. I cannot ping the
dummy0 IP from the DomU console.

SU-debian:~# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      376     1 r-----  6523.0
Tarooza                            3      216     1 ------   452.8
suxen-1Deb                         4       64     1 --p---     0.0


Booting the Domu generates the following error (xend.log)
======
[2005-12-14 20:42:02 xend] DEBUG (DevController:133) Waiting for devices vif.
[2005-12-14 20:42:02 xend] DEBUG (DevController:139) Waiting for 0.
[2005-12-14 20:42:02 xend] DEBUG (DevController:409)
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2005-12-14 20:42:03 xend] DEBUG (DevController:409)
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2005-12-14 20:42:03 xend] DEBUG (DevController:426) hotplugStatusCallback 3.
[2005-12-14 20:42:03 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
Traceback (most recent call last):
  File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 72, in
op_wait_for_devices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1344, in
waitForDevices
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 973, in
waitForDevices_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 135,
in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 151,
in waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Backend device not found.

====

My Configuration
==========
kernel = "/boot/boot/vmlinuz-2.6-xenU"
memory = 64
vmid=3
name = "suxen-1Deb"
nics=1
vif = [ 'bridge=dummy0' ]
disk = 
['file:/usr/xen-images/debian-root,sda1,rw','file:/usr/xen-images/debian-swap,sda2,rw']
ip="192.168.11.156"
netmask="255.255.255.0"
gateway="192.168.11.1"
hostname="suxen-1.qcd.in"
root="/dev/sda1 ro"
extra="3"
==========

thanks

Sanjay Upadhyay
_______________________________________________
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®.