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

[Xen-users] network-detach broken?

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] network-detach broken?
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=wtz10TH07fLEiRFDWec/idsUWXNB8/vncQsOJStHUcA=; b=gxc1j3xgK6j5ofOSdF4j3pxf6cSKRwyvbJbwLXD7nL+WkS+rOBP71Qj6jJmcpMVOYLpHsAtIe8JQLjZ8pnu8HgmZLZFCPzq/zHg+1XrWvEuoXEtMquIDu3hWDKdyM4LL+cZdbp+aGynWEOkPF7VFtksihBBlnfJ8HDar9VkIJ/8=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>