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

[Derek Glidden <dglidden@xxxxxxxxxxxxxxx>]

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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel