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

[Xen-users] network-detach broken?


  • To: "xen-users@xxxxxxxxxxxxxxxxxxx" <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Arie Goldfeld" <arik.goldfeld@xxxxxxxxx>
  • Date: Wed, 16 Jan 2008 16:43:42 +0200
  • Delivery-date: Wed, 16 Jan 2008 06:44:17 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=uyGAAc68GXZXLgRjFvIWW+lBeYRL75j17ZSDL2IWQDib7X94nVNALK2Yk4f6a6aYjIV/LgI7+6mXr7E8rfDxRAhnBIHdCwplbCF++j7N4twNioFG01vttctPwc2o1J7GN0z/4P9Y1AVK6zhLncU1y1o0PYXMNZxj+eDO7+Ugkvw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi all,
 
I use xm network-detach <domain> <devid> to delete domU's network interfaces. But it seems to be broken, as the vifs are not really deleted. For example, if I detach device 0, and then attach a device to that domain again, its number is 1, as if 0 is still exists. Even more strange, after reboot all the detached devices are somehow resurrected and show up again in both domU as eth0, eth1, ..., and dom0 as vif/0, vif/1, ...!
Any ideas?
 
Thanks
_______________________________________________
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®.