Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=979411.
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
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is there still something left to do here, or could we close this ticket
nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192499
Title:
migrate -b tcp :destination-ip:1234
There should be no space between tcp and the rest of the connection
details:
migrate -b tcp:destination-ip:1234
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 07/05/2013 01:52 PM, Stefan Hajnoczi wrote:
The destination VM's log says:
qemu: warning: error while loading state section id 1
This indicates that either there was an error on the destination while
loading state or the migration stream got out of sync.
Please check that QEMU on
** Attachment added: source guest logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725328/+files/source.log.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Source Libvirtd logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725330/+files/source_libvirtd.logs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Destination guest logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725329/+files/dest.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Destination Libvirtd logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725331/+files/destination_libvirtd.logs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The destination VM's log says:
qemu: warning: error while loading state section id 1
This indicates that either there was an error on the destination while
loading state or the migration stream got out of sync.
Please check that QEMU on source and destination are identical. If you
are
Thanks, I ll work on this and update it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192499
Title:
virsh migration copy-storage-all fails with Unable to read from
monitor: Connection reset by
Moving to qemu component as qemu is crashing based on the inputs from
Michal Privoznik
Bugzilla : Bug 979411 - virsh migration copy-storage-all fails with
Unable to read from monitor: Connection reset by peer
** Project changed: libvirt = qemu
** Bug watch added: Red Hat Bugzilla #979411
I am sorry.
Host Kernel : 3.10.0-rc5+ [upstream kernel fedora base], both the source
and destination host are the same.
We test the upstream kernel, qemu and libvirt. We don't have ubuntu.
Oh, I see - then please see http://libvirt.org/bugs.html (specifically
General libvirt bug reports)
** Attachment added: Source sosreport
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3720183/+files/sosreport-source.1192499-20130701151939-cc68.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We tried with emulator/usr/bin/qemu-system-x86_64/emulator and we
are facing the same issue.
For both source and destination the fs is ext4.
We are using fedora base, hence I have attached the sosreport of both
source and destination.
** Attachment added: Destination sosreport
On 06/29/2013 12:15 AM, Serge Hallyn wrote:
Thanks for submitting this bug. I can' t reproduce it with an empty
image (sitting at cd boot menu).
What is the underlying fs (/home/images) on both source and destination?
For both source and destination the fs is ext4.
Could you run
Hi,
I'm confused - what do you mean by you are using a fedora base? Are you
talking about the VM, or the destination host? If the destination host,
then (a) is it identical to the source host, and either way (b) exactly
how did you set up the hosts with ubuntu packages?
--
You received this
I am sorry.
Host Kernel : 3.10.0-rc5+ [upstream kernel fedora base], both the source
and destination host are the same.
We test the upstream kernel, qemu and libvirt. We don't have ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am sorry.
Host Kernel : 3.10.0-rc5+ [upstream kernel fedora base], both the source
and destination host are the same.
We test the upstream kernel, qemu and libvirt. We don't have ubuntu.
Oh, I see - then please see http://libvirt.org/bugs.html (specifically
General libvirt bug reports)
Thanks for submitting this bug. I can' t reproduce it with an empty
image (sitting at cd boot menu).
What is the underlying fs (/home/images) on both source and destination?
Could you run 'apport-collect 1192499' on the destination host?
Oh, actually I notice you have
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192499
Title:
virsh migration copy-storage-all fails with Unable to read from
21 matches
Mail list logo
