setting the txqueuelen on vnetX devices to 2500 we can increase the network throughput by a factor of almost 10. On an eth device it can be set by hand/rc.local with the following instructions http://www.cyberciti.biz/faq/gentoo-centos-rhel-debian-fedora-increasing-txqueuelen/ . Because vnetX devices are named on a 'first free' basis and they come and go with the guests, the rc.local method is not going to work.
Ideally I would like to be able to set this automatically for all vnetX devices when they are created or even better, on a per guest basis.
the proposed solution works fine, but I guess all the VMs/vnets will have the same txqueuelen as configured in /etc/udev/...?
What happens if I want to customize different VMs/vnet with different txqueuelen.
The proper solution would be to be able to specify the txquelen in the xml description instead on a per vnet basis
Is there still an interest in this enhancement?
We have dropped virtualization for all our production systems. The solution above works for us in because we use puppet to manage it on any system that requires it so unless anyone else is after the feature then I would put it at the bottom of the list or drop it.
Okay, closing per comment 3. If anybody find out that they need this, please feel free to reopen.