vif naming? also halting a VM

vif naming? also halting a VM

[Derek Glidden]

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?

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?

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?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"I think that's what they mean by   |
"nickels a day can feed a child."   |       http://www.eff.org/
I thought, "How can food be so      | http://www.anti-dmca.org/
cheap over there?"  It's not, they  |--------------------------
just eat the nickels." -- Peter Nguyen



-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: vif naming? also halting a VM

[Mike Wray]

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?

Mike


-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: vif naming? also halting a VM

[Derek Glidden]

On Jul 19, 2004, at 9:37 AM, Mike Wray wrote:

> 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.

Ok, just checking.  I want to try to write a script that brings up 
aliases and sets up iptables rules for NAT and such, and I wondered 
what the options for managing vif names were.  Your rationale all makes 
perfect sense, so I won't argue.  :)

>> 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?

That particular example was from code checked out sunday afternoon.

xend debug output shows "shutdown" and "destroy domain 7" or somesuch 
messages after the halt, yet "xm list" shows it still in state "s" 
afterward.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"I think that's what they mean by   |
"nickels a day can feed a child."   |       http://www.eff.org/
I thought, "How can food be so      | http://www.anti-dmca.org/
cheap over there?"  It's not, they  |--------------------------
just eat the nickels." -- Peter Nguyen



-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: vif naming? also halting a VM

[Mike Wray]

Derek Glidden wrote:

> 
> On Jul 19, 2004, at 9:37 AM, Mike Wray wrote:
> 
>> 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.
> 
> 
> Ok, just checking.  I want to try to write a script that brings up 
> aliases and sets up iptables rules for NAT and such, and I wondered what 
> the options for managing vif names were.  Your rationale all makes 
> perfect sense, so I won't argue.  :)
> 
>>> 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?
> 
> 
> That particular example was from code checked out sunday afternoon.
> 
> xend debug output shows "shutdown" and "destroy domain 7" or somesuch 
> messages after the halt, yet "xm list" shows it still in state "s" 
> afterward.

OK, I'll need some more info. Can you send the output from xend, and
also the output from 'xm list -l'?
Does this always happen or only with some domain configs?

Mike


-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click