[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992530
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9925
Also please post /var/log/libvirt/qemu/Test-vm1.log from both
192.168.2.48 and 192.168.2.250
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992530
Title:
Live Migration failing
To manage notificatio
Are you able to do
virsh -c qemu+ssh://192.168.2.48/system list
What happens when you simply do:
ssh 192.168.2.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992530
Title:
Live Migration f
stack@system-1:~$ virsh migrate --live --p2p Test-vm-1
qemu+ssh://192.168.2.48/system
error: operation failed: Failed to connect to remote libvirt URI (null)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
The kernel and qemu versions in both systems are same.
stack@system-1:~$ virsh migrate --live --tunnelled Test-vm-1
qemu+ssh://192.168.2.48/system --verbose
stack@192.168.2.48's password:
error: Requested operation is not valid: cannot perform tunnelled migration
without using peer2peer flag
Please also provide the qemu-kvm and libvirt versions on System2
(192.168.2.48)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992530
Title:
Live Migration failing
To manage notifications about this
Hi,
It looks like you are using virt-manager to do the migration.
In order to help make sure virt-manager isn't causing the problem, could
you manually do the migration using libvirt?
If you run virt-manager on 192.168.2.250 itself, then log into
192.168.2.250 and do
virsh migrate --live --tunn
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992530
Title:
Live Migration failing
To manage notifications about this b
