On Tue, Jun 06, 2017 at 01:36:27PM +0200, Ján Tomko wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1283251 > --- > docs/formatdomain.html.in | 13 +++++++++++++ > docs/schemas/domaincommon.rng | 5 +++++ > src/conf/domain_conf.c | 15 +++++++++++++++ > src/conf/domain_conf.h | 1 + > tests/qemuxml2argvdata/qemuxml2argv-virtio-options.xml | 4 ++++ > .../qemuxml2xmloutdata/qemuxml2xmlout-virtio-options.xml | 4 ++++ > 6 files changed, 42 insertions(+) > > diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in > index 5c0f3bf..c9c3592 100644 > --- a/docs/formatdomain.html.in > +++ b/docs/formatdomain.html.in > @@ -5715,6 +5715,19 @@ qemu-kvm -net nic,model=? /dev/null > event device passed through to guests. (KVM only) > </p> > > + <p> > + The subelement <code>driver</code> can be used to tune the virtio > + options of the device: > + <a href="#elementsVirtio">Virtio-specific options</a> can also be > + set. (<span class="since">Since 3.5.0</span>) > + </p> > + <p> > + The <code>compatibility</code> attribute of the <code>driver</code> element > + can be used to specify the compatibility of virtio devices. Allowed values > + are <code>legacy</code>, <code>transitional</code> and <code>modern</code>. > + <span class="since">Since 2.2.0</span>. > + </p> So there is a documentation for the driver compatibility but there is no code to handle these attributes, so I guess that it's really some leftover. Reviewed-by: Pavel Hrdina <phrdina@xxxxxxxxxx>
Attachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
