Hi!
AFAIK, virt-install has no method of specifying the <virtualport> parameters for an interface. What you're asking for here is an interface definition of:
Yes, up to version 0.10. there's not.
You need to change you virt-install commandline so that the --network argument is something like this:
--network network=databr0,model=virtio,mac=00:00:00:00:00:03
Great! It works! I used '--network=bridge:databr0....' because I was using this reference: http://www.siliconloons.com/?p=277 More precisely: http://www.siliconloons.com/wp-content/uploads/2012/08/Screen-Shot-2012-08-0... And there the author has used interface type 'bridge'. So I thought I should use it too.
As long as the OVS service is running this should do what you want (although you'll later probably want to add a "<virtualport type='openvswitch'> element to the domain's <interface> element, so that libvirt generates/stores a permanent interface-id for the domain rather than generating a new one each time the domain is started).
Maybe should be a good idea to add a support of defining "<virtualport type='openvswitch'>" using the API, shouldn't it ?
Well, I read elsewhere that openvswitch bridging isn't fully supported. Is it the case or I'm facing another kind of problem ?
It certainly is supported to the level that you're trying to use it. Libvirt can define networks that use existing ovs switches, and connect guest interfaces either via the aforementioned networks, or directly using type='bridge'.
Ok, Thanks! regards -- Att Lucas Brasilino MSc Student @ Federal University of Pernambuco (UFPE) twitter: @lucas_brasilino