On 09/04/2012 11:14 AM, Laine Stump wrote: > On 09/04/2012 04:29 AM, Martin Kletzander wrote: >> There should be one more option in case the <virtualport> is specified >> in the guest's <interface>. According to the docs [2], when no "type=" >> is specified for the <virtualport> element, this should be >> auto-completed on the domain startup, but that's most probably not >> applicable for your situation (migration). > That is only the case for 1) very new libvirt (0.10.0+) and 2) > <interface type='network'>. It's purpose is to allow specifying, for > example, both an openvswitch interfaceid and an 802.11Qbh profileid at > the same time (for cases when the guest doesn't know whether the network > it connects to will be openvswitch or 802.1Qbh, and wants to specify the > appropriate setting for both possibilities). I picked a bad example (Open vSwitch also uses profileid). Think instead of the case where you didn't know if the host was going to be openvswitch (which uses interfaceid) or 802.1Qbg (which uses instanceid). -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list