Re: [Xen-users] vifnames

["Likarpenkov Alexander" <al@xxxxxxxxxxxxxxx>]

I was completely satisfied with the current situation. I picked an arbitrary 
DomU
And how many would not have virtual systems - quickly found their interfaces
Nothing needs to be changed
Embracing reason:

# xm list | grep g3
g3                                          18   128     1     -b----  
43466.0
# ifconfig | grep -A6 vif18
vif18.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
         RX packets:5364587 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5145284 errors:0 dropped:22 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:1034242595 (1.0 GB)  TX bytes:602515830 (602.5 MB)
--
vif18.1   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
         RX packets:4935521 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5255805 errors:0 dropped:38 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:876714763 (876.7 MB)  TX bytes:1111388104 (1.1 GB)
--
vif18.2   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
         RX packets:1498125 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1950646 errors:0 dropped:11 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:526095465 (526.0 MB)  TX bytes:223020577 (223.0 MB)
--
vif18.3   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:373779 errors:0 dropped:21 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:28 (28.0 B)  TX bytes:19436508 (19.4 MB)


? ???????, ???????? ???????? ?????? 2012 ????, ? 14:21:26 ?? ??????:

??>> I agree that a list of features which xl supports would be a useful
??>> thing to have. I have just made a start on updating
??>> http://wiki.xen.org/wiki/XL with such a list (as well as some more
??>> highlevel blurb). Further contributions welcomed ;-)

MvD> I looked at this page and
MvD> 
http://xenbits.xen.org/docs/unstable/misc/xl-network-configuration.html
MvD> Quote:

??>> vifname
??>> This keyword is valid for HVM guest devices with type=ioemu only.
??>> Specifies the backend device name for an emulated device. The default
??>> is tapDOMID.DEVID where DOMID is the guest domain ID and DEVID is the
??>> device number.

MvD> Why can't this be extended to all domains?

MvD> It's important for me to properly have vifnames because if you have a
MvD> large number of hosts then arbitrary vif names are much harder to read
MvD> than custom vifnames. I know, I've been nagging about it but that's
MvD> only because I haven't seen any real response to it... other than
MvD> other users who seem to support the idea.

MvD> So can this please be added, Ian?

--
I try to select the top of the correspondence
and collected  in one location.
Come and help comments
http://lixen.ua-ohosting.com/ 

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