I agree that this still is the case:
xml:
<interface type='network'>
<source network='ovsbr0'/>
<model type='virtio'/>
<driver name='vhost' queues='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</interface>
dumpxml from defined guest:
<interface type='bridge'>
<mac address='52:54:00:a5:a6:eb'/>
<source network='ovsbr0' bridge='ovsbr0'/>
<virtualport type='openvswitch'>
<parameters interfaceid='f221387d-859a-4e2a-b159-6cdc75b92597'/>
</virtualport>
<target dev='vnet1'/>
<model type='virtio'/>
<driver name='vhost' queues='4'/>
<alias name='net1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</interface>
So far I've only seen this with OVS bridges.
E.g. a usual type network virtio device stays type network.
Per [1] it seems that type bridge is actually correct to attach to OVS.
That said I'd think it is a compat that cleans up for both of us and fixes it
when instantiating the OVS attachment.
If you "virsh destroy" the guest it will be back to a type network.
I think this is all as it should be, in the moment it is attached it is
considered a bridge then.
Otherwise I think we should discuss this with upstream instead of here.
If you report something there please add a link to the upstream discussion in
the mail archive here.
[1]: https://libvirt.org/formatdomain.html
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766888
Title:
interfaces of type "network" are reported as type "bridge"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1766888/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
