Laine Stump fe053dbea7 Enable tuning of qemu network tap device "sndbuf" size ... This is in response to a request in: https://bugzilla.redhat.com/show_bug.cgi?id=665293 In short, under heavy load, it's possible for qemu's networking to lock up due to the tap device's default 1MB sndbuf being inadequate. adding "sndbuf=0" to the qemu commandline -netdevice option will alleviate this problem (sndbuf=0 actually sets it to 0xffffffff). Because we must be able to explicitly specify "0" as a value, the standard practice of "0 means not specified" won't work here. Instead, virDomainNetDef also has a sndbuf_specified, which defaults to 0, but is set to 1 if some value was given. The sndbuf value is put inside a <tune> element of each <interface> in the domain. The intent is that further tunable settings will also be placed inside this element. <interface type='network'> ... <tune> <sndbuf>0</sndbuf> ... </tune> </interface>		2011-01-14 14:46:38 -05:00
..
capability.rng	cpu: Add support for CPU vendor	2010-07-07 17:26:00 +02:00
domain.rng	Enable tuning of qemu network tap device "sndbuf" size	2011-01-14 14:46:38 -05:00
domainsnapshot.rng
interface.rng	interface.rng: Make miimon and arpmon optional for bond interfaces	2010-11-15 14:22:42 -05:00
Makefile.am
network.rng	Change virtual network XML parsing/formatting to support IPv6	2010-12-23 15:53:55 -05:00
nodedev.rng
nwfilter.rng	nwfilter: Extend schema to accept state attribute	2010-10-07 06:44:41 -04:00
secret.rng
storageencryption.rng
storagepool.rng	Fix parsing of port attribute in storage XML configuration	2010-11-23 14:55:33 +00:00
storagevol.rng