Xen project Mailing List

Re: [Xen-users] network-detach broken?

To: "Arie Goldfeld" <arik.goldfeld@xxxxxxxxx>

From: "Todd Deshane" <deshantm@xxxxxxxxx>

Date: Wed, 16 Jan 2008 10:37:21 -0500

Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <Xen-users@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Wed, 16 Jan 2008 07:37:54 -0800

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dLR6vmTIO2Lz9duoMftl47WFYXgANi+jHJ+O1is9wDucrkem2I1Y/uYGEE0B5jVpiSEr7NoQGEgCLXuOcYU7jYVTs5IEf5GLRp5d/o7nnb2m9MVSleczI/iopw26JiLXMHdFv67dtIscEJSvFNlUwiwfJ++2cM1YKR+XSFKte8k=

List-id: Xen user discussion <xen-users.lists.xensource.com>

On Jan 16, 2008 9:43 AM, Arie Goldfeld <arik.goldfeld@xxxxxxxxx> wrote:

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?

First, when you detach, the guest probably already has an entry for eth0 that udev or hotplug is naming eth0 and not releasing when the device is detached. This might just be a bug with udev or possibly a kernel problem.

Second, detaching a device doesn't remove it from the config, once you re-create the guest whatever vifs were originally assigned will show up.

Does that help?

Regards,
Todd

Thanks

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

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