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/
Home Products Support Community News


Re: [Xen-devel] vif naming? also halting a VM

To: Derek Glidden <dglidden@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] vif naming? also halting a VM
From: Mike Wray <mike.wray@xxxxxxxxxx>
Date: Mon, 19 Jul 2004 14:37:04 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 19 Jul 2004 14:43:38 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <07BD30EC-D912-11D8-86C4-000A95DBAEDE@xxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <07BD30EC-D912-11D8-86C4-000A95DBAEDE@xxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Derek Glidden wrote:

Where are the names "vif1.0", etc created in -unstable? Is that from the python tools or is the xen or dom0 kernel assigning that value somehow?

It's in both the back-end network interface driver domain
(usually dom0) and the python tools. At the moment there's no way to tell the
driver domain what name to use - it invents the name from the domain id and
vif index. So eth0 on domain 2 gets called 'vif2.0'. The python tools do the
same for consistency.

I'd like to change it so that if I'm starting "vmid=1" I get "vif1.0" and "vmid=103" gets "vif103.0" etc. as opposed to the vif getting the Dom ID. Possible?

Not at the moment, for the reasons above. Bear in mind though that the
domain name is passed to the vif control script - so if the domain name
includes the vmid you can recover it.

We're thinking about switching away from exposing xen's domain ids at all,
and using user-specified domain identifiers (and insisting on
uniqueness). At the same time we could think about changing the vif
names to use the domain identifier. One issue is the built-in
kernel limit on interface name size: IFNAMSIZ=16. Another is the effect
on migrating domains. If domain idents have to be unique, then they'll have to
be globally unique, and that will rule out simple ones like 0, 1, 2...
But long ones will be too long to fit in interface names.

Second, when I run "halt" in a VM, "xm list" shows the VM still hanging around:

# xm list
0    Domain-0              54    0  r----   2073.2
7    This is VM 1           0    1  ---s-     29.0

"xm shutdown" or "destroy" don't seem to have any effect.  Is this normal?

This sort of problem seemed to have been cured a while ago.
What version of the code are you using?


This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>