On 9/6/23 15:26, Laurent Coloby via discuss wrote: > Hello support > > I'm blocked on a basic issue > > I use libvirt / KVM with unbutu > > > I just want to launch a virtual Machine with a connection to OVS > > With command virsh edit VM , I modify to be conform to your recommendation > https://docs.openvswitch.org/en/stable/howto/libvirt/ > > [cid:[email protected]] > > > And when I start the VM , I have always same issue > > [cid:[email protected]]
I'm not sure what this list policy is, but if this were libvir-list I'd ask you to NOT take a screenshots of a text only to place them into a text later. > > On Internet , I have seen several people with same issue, but not fond any > explanation > > Please could you help me on this problem ? > Thank you in advance > If you enable libvirt debug logs [1] then you should be able to see what command is libvirt actually executing to add the TAP device into the bridge. The code that drives what arguments are passed to 'ovs-vsctl --may-exist add-port ...' depend on a lot of config knobs [2]. But in this case it should be fairly trivial command. Anyway, if you turn on libvirt debug logs you should be able to see what command was executed (and perhaps even if it reported any error - if it did libvirt should have passed on that error message, so maybe there's an improvement potential on libvirt side too). 1: https://libvirt.org/kbase/debuglogs.html 2: https://gitlab.com/libvirt/libvirt/-/blob/master/src/util/virnetdevopenvswitch.c?ref_type=heads#L130 Michal _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
