Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 5/10/19 6:23 PM, lejeczek wrote: On 10/05/2019 14:44, Michal Privoznik wrote: On 5/10/19 3:26 PM, lejeczek wrote: hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you share your configuration and the network XML? Michal so if your libvirt's net is like this: ovs-br0 e5129e76-1576-4866-97e1-42f14263cfc2 then you need extra(extra for ovs tools create both for us at bridge creation time and nmcli(you) need to create those explicitly) port+iface so this: $ ovs-vsctl show output will contain this: ... Port "ovsbr0" Interface "ovsbr0" type: internal That is expected. is document like so: https://libvirt.org/formatnetwork.html#elementsConnect Michal ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 10/05/2019 14:44, Michal Privoznik wrote: > On 5/10/19 3:26 PM, lejeczek wrote: >> hi guys >> >> I have a qemu guest and openvswitch bridge and the guest fails to start: >> >> $ virsh start work8 >> error: Failed to start domain work8-vm-win2016 >> error: Cannot get interface MTU on 'ovsbr0': No such device > > Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you > share your configuration and the network XML? > > Michal so if your libvirt's net is like this: ovs-br0 e5129e76-1576-4866-97e1-42f14263cfc2 then you need extra(extra for ovs tools create both for us at bridge creation time and nmcli(you) need to create those explicitly) port+iface so this: $ ovs-vsctl show output will contain this: ... Port "ovsbr0" Interface "ovsbr0" type: internal ... pEpkey.asc Description: application/pgp-keys ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 10/05/2019 14:44, Michal Privoznik wrote: > On 5/10/19 3:26 PM, lejeczek wrote: >> hi guys >> >> I have a qemu guest and openvswitch bridge and the guest fails to start: >> >> $ virsh start work8 >> error: Failed to start domain work8-vm-win2016 >> error: Cannot get interface MTU on 'ovsbr0': No such device > > Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you > share your configuration and the network XML? > > Michal and OVS' bits: $ ovs-vsctl show 79bc7faa-a7cd-482c-95ad-8b0e8f89a6f1 Bridge "ovsbr0" Port "ovsbr0-port0" tag: 55 Interface "ovsbr0-int0" type: internal Port "vnet16" tag: 55 Interface "vnet16" Port "ovsbr0-p3p1" Interface "p3p1" type: system Port "vnet18" tag: 54 Interface "vnet18" ovs_version: "2.9.0" created with/by NM. pEpkey.asc Description: application/pgp-keys ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 10/05/2019 14:44, Michal Privoznik wrote: > On 5/10/19 3:26 PM, lejeczek wrote: >> hi guys >> >> I have a qemu guest and openvswitch bridge and the guest fails to start: >> >> $ virsh start work8 >> error: Failed to start domain work8-vm-win2016 >> error: Cannot get interface MTU on 'ovsbr0': No such device > > Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you > share your configuration and the network XML? > > Michal network: ovs-br0 e5129e76-1576-4866-97e1-42f14263cfc2 pEpkey.asc Description: application/pgp-keys ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 10/05/2019 14:44, Michal Privoznik wrote: > On 5/10/19 3:26 PM, lejeczek wrote: >> hi guys >> >> I have a qemu guest and openvswitch bridge and the guest fails to start: >> >> $ virsh start work8 >> error: Failed to start domain work8-vm-win2016 >> error: Cannot get interface MTU on 'ovsbr0': No such device > > Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you > share your configuration and the network XML? > > Michal qemu's: (fails to start) LXC's: (starts) This is Openvswitch' bridge thus does not exits as "iface" per say, but this is how it should be used in libvirt, I think, no? LXC works okey. How is it different for Qemu? thanks, L pEpkey.asc Description: application/pgp-keys ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 5/10/19 3:26 PM, lejeczek wrote: hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device Well, this means that 'ovsbr0' doesn't exist. Is that so? Can you share your configuration and the network XML? Michal ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
[libvirt-users] Cannot get interface MTU - qemu quest fails to start off OpenVswitch
hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and libvirt-4.5.0-10.el7_6.7.x86_64. Would anybody care to suggest a possible reson(s) causing the failure? many thanks, L. pEpkey.asc Description: application/pgp-keys ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
