[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] virtual interface problems



Hi Everyone,

Hope you are all well..

I have some problems to configure bandwidth monitoring for domains in an xen vps......

Suppose we have three domains..... The ifconfig entry will something like this

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:3691 errors:0 dropped:0 overruns:0 frame:0
        TX packets:412527 errors:0 dropped:776 overruns:0 carrier:0
        collisions:0 txqueuelen:0
        RX bytes:435348 (425.1 Kb)  TX bytes:24588202 (23.4 Mb)

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:4894 errors:0 dropped:0 overruns:0 frame:0
        TX packets:412178 errors:0 dropped:667 overruns:0 carrier:0
        collisions:0 txqueuelen:0
        RX bytes:477402 (466.2 Kb)  TX bytes:25068366 (23.9 Mb)

vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:64606 errors:0 dropped:0 overruns:0 frame:0
        TX packets:376113 errors:0 dropped:610 overruns:0 carrier:0
        collisions:0 txqueuelen:0
        RX bytes:18405141 (17.5 Mb)  TX bytes:73257575 (69.8 Mb)

Only the specific part taken.... When we stop and start all these domains it will be vif4.0, vif5.0, vif6.0 and if we restrat once again it would take the next three digits and will be going up. Only a system reboot would bring this to its first stage...

So really bandwidth monitoring seems to be a horrible task... I use the contents of /proc/net/dev as mrtg collects data from there... So if i restart a domain i must make related changes in mrtg config files....

I submitted this earlier to mailing list and got this reply..


With recent 2.0-testing you can put vifname in the config file:

vif=[ 'mac=aa:00:00:4b:a0:c1, bridge=xen-br0, vifname=vif-example.0' ]

So then it would have a device always called vif-example.0.

Seems good.. But since we are using xen in a production environment 
xen-2.0-testing shouldn't be an alternative for us. Let me know whether this 
feature will be included in xen-3.0 stable or not?

Thanks Sadique



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.