And libosinfo is just telling us that the guest supports
'virio-1.0-net'. There are two ways to provide that: the
"virtio-transitional" vs. "virtio-non-transitional" devices.
Where "virtio-transitional" provides a device that will auto-negotiate
virtio 1.0 support; while "virtio-non-transitional" provoides a device
that is fixed to always use virtio 1.0 support.
- - -
The recomendation for all CentOS 7.0 devices is to go with 'virtio'.
- - -
Documentation on "virtio-transitional" vs. "virtio-non-transitional":
Based on a chat with Dan Berrangé (thank you), there are two problems
here:
(1) Nova's validation of network models is incomplete, i.e. the method vif_model_ valid_for_ virt() has an incomplete list of hardware
is_
models
(2) The "model names returned by libosinfo are *NOT* required to be 1.0-net" model name in libvirt, if we see here: /libvirt. org/git/ ?p=libvirt. git;a=blob; f=src/conf/ domain_ conf.c# l515
valid libvirt network model names". I.e. there is no such
"virtio-
https:/
And libosinfo is just telling us that the guest supports transitional" vs. "virtio- non-transitiona l" devices.
'virio-1.0-net'. There are two ways to provide that: the
"virtio-
Where "virtio- transitional" provides a device that will auto-negotiate non-transitiona l" provoides a device
virtio 1.0 support; while "virtio-
that is fixed to always use virtio 1.0 support.
- - -
The recomendation for all CentOS 7.0 devices is to go with 'virtio'.
- - -
Documentation on "virtio- transitional" vs. "virtio- non-transitiona l":
https:/ /libvirt. org/formatdomai n.html# elementsVirtioT ransitional)