On Wed, Jan 05, 2011 at 09:57:42AM -0500, Laine Stump wrote:
On 01/05/2011 05:19 AM, Daniel P. Berrange wrote:
We should try to keep terminology matching the diskdriver
so I think
driver name='qemu|vhost'/
with omission ofdriver resulting in us automatically
adding either 'qemu' or
On 01/07/2011 10:55 AM, Daniel P. Berrange wrote:
On Wed, Jan 05, 2011 at 09:57:42AM -0500, Laine Stump wrote:
On 01/05/2011 05:19 AM, Daniel P. Berrange wrote:
We should try to keep terminology matching the diskdriver
so I think
driver name='qemu|vhost'/
with omission ofdriver
On Tue, Jan 04, 2011 at 02:37:15PM -0500, Laine Stump wrote:
There's a request to allow libvirt to explicitly turn on/off the new
vhost-net feature of virtio network cards. I see a few ways to do
it, and am looking for opinions on which is best.
(For the uninitiated, vhost-net is a new
On 01/05/2011 05:19 AM, Daniel P. Berrange wrote:
We should try to keep terminology matching the diskdriver
so I think
driver name='qemu|vhost'/
with omission ofdriver resulting in us automatically
adding either 'qemu' or 'vhost' to the XML. We don't
want to have an explicit 'default'
There's a request to allow libvirt to explicitly turn on/off the new
vhost-net feature of virtio network cards. I see a few ways to do it,
and am looking for opinions on which is best.
(For the uninitiated, vhost-net is a new kernel-based virtio
implementation that saves the overhead of
On 01/04/2011 12:37 PM, Laine Stump wrote:
It's simple enough to put a bit of extra logic at the point where we
make that decision. I see 3 possibilities:
1) default - use vhost-net if it's loaded, don't if it isn't (current
behavior)
2) require - use vhost-net if it's loaded, and refuse
