Following upstream to Won't Fix for now.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432630
Title:
libvirt tunnelled migrati
Launchpad has imported 27 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1202453.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
As far as I can tell, the reports mentioning problems only with qemu+ssh
and not qemu+tcp are unrelated. Probably best if you could verify
yourself. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Per the rh bug, does using qemu+tcp instead of qemu+ssh work around it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432630
Title:
libvirt tunnelled migration fails with "migration job: unexpected
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432630
Title:
libvirt tunnelled migration fails with "migration job: unexpectedly
failed"
To manage notification
Could you please list here the qemu bug number?
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
reopening because the upstream issue have been reopen
** Changed in: libvirt (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432630
Title:
libvirt tunnelled mi
I will raise a seperate bug for qemu.
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Changed in: qemu (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
According to the upstream (see the bug report mentioned in the previous
comment) it's not a bug in libvirt but in qemu so I have added qemu to
affected packages.
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=1202453
Importance: Unknown
Status: Unknown
** Al
I've just tested with the current upstream git master
51f9f03a4ca50b070c0fbfb29748d49f583e15e1 and ran into the same problem.
I've raised an issue against upstream libvirt here
https://bugzilla.redhat.com/show_bug.cgi?id=1202453 .
** Bug watch added: Red Hat Bugzilla #1202453
https://bugzilla.r
** Attachment added: "/var/log/libvirt/qemu/ubuntuutopic.log log on the
destination node"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432630/+attachment/4347085/+files/ubuntuutopic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "libvirtd log on the destination node"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432630/+attachment/4347084/+files/destination_libvirtd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "libvirtd log on the source node"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432630/+attachment/4347083/+files/source_libvirtd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
13 matches
Mail list logo
