These are the steps that I followed for verification:
1) I created 2 virtual machines
$ uvt-kvm create trusty
$ uvt-kvm create trusty2
2) On the primary (trusty) I created a machine called test
$ uvt-kvm create test
3) Installed openvswitch
$ sudo apt-get install openvswitch-switch
4) Created a new openvswitch bridge
$ sudo brctl addbr br0
$ sudo ovs-vsctl add-br br0
$ sudo ifconfig br0 up
5) Edited the network
$ virsh destroy test
$ virsh edit test
<interface type='bridge'>
<mac address='52:54:00:66:99:7b'/>
<source bridge='br0'/>
<virtualport type='openvswitch'>
<parameters interfaceid='74178f6a-14bc-45d0-a54c-11aa8b907622'/>
</virtualport>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</interface>
6) Start the domain
$ virsh start test
7) Migrate between both systems:
$ virsh migrate --live --p2p --persistent --abort-on-error trusty
qemu+ssh://ubuntu@192.168.122.110/system
At this point the migration completes correctly, without the
virCommandWait:2423 exception.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540537
Title:
make ovs-vsctl not raise error if there's no portData available.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1540537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
