From: ChristianEhrhardt <1711602@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1711602] Re: --copy-storage-all failing with qemu 2.10
Date: Tue, 22 Aug 2017 08:58:52 -0000 [thread overview]
Message-ID: <150339233236.8725.2618271632756711348.malone@soybean.canonical.com> (raw)
In-Reply-To: 150305905460.11582.12289718300820278863.malonedeb@wampee.canonical.com
So this is failing I/O that iterates over a channel.
I was tracking down the len, pending and pos used.
I found that this is not completely broken (like no access or generla I/O error)
It starts at pos 0 and iterated with varying offsets, but works for quite some time.
Example:
[...]
Thread 1 "qemu-system-x86" hit Breakpoint 2, qemu_fill_buffer (f=f@entry=0xd3b66f3c00) at ./migration/qemu-file.c:295
295 if (len > 0) {
$11183 = 28728
$11184 = 4040
$11185 = {ops = 0xd3b3d740a0 <channel_input_ops>, hooks = 0x0, opaque = 0xd3b75ee490, bytes_xfer = 0, xfer_limit = 0, pos = 107130146,
buf_index = 0, buf_size = 4040,
buf = "\v\327\a\000\021\000\[...]\000"...,
may_free = {0}, iov = {{iov_base = 0x0, iov_len = 0} <repeats 64 times>}, iovcnt = 0, last_error = 0}
[...]
Well you could see the whole file read passing by one by one buffer
Yet this isn't particularly fast, so track the one that has len==0
(gdb) b ./migration/qemu-file.c:295 if len == 0
And I got it as:
(gdb) p *f
$11195 = {ops = 0xd3b3d740a0 <channel_input_ops>, hooks = 0x0, opaque = 0xd3b75ee490, bytes_xfer = 0, xfer_limit = 0, pos = 319638837,
buf_index = 0, buf_size = 0, buf = '\000' <repeats 5504 times>..., may_free = {0}, iov = {{iov_base = 0x0, iov_len = 0} <repeats 64 times>},
iovcnt = 0, last_error = 0}
Here pending == 0 so buf_size = 0 as well also pos is further down
incremented to 319638837.
Checking in detail I found that I had pending=0 and buf_size=0 as well as non aligned pos entried, but they worked.
So I excluded the buf_size=0/pending=0 as well as the alignment as reasons.
Maybe it just iterates pos out of the range that is working?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu 2.10
Status in QEMU:
New
Status in libvirt package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
Confirmed
Bug description:
We fixed an issue around disk locking already in regard to qemu-nbd
[1], but there still seem to be issues.
$ virsh migrate --live --copy-storage-all kvmguest-artful-normal qemu+ssh://10.22.69.196/system
error: internal error: qemu unexpectedly closed the monitor: 2017-08-18T12:10:29.800397Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2017-08-18T12:10:48.545776Z qemu-system-x86_64: load of migration failed: Input/output error
Source libvirt log for the guest:
2017-08-18 12:09:08.251+0000: initiating migration
2017-08-18T12:09:08.809023Z qemu-system-x86_64: Unable to read from socket: Connection reset by peer
2017-08-18T12:09:08.809481Z qemu-system-x86_64: Unable to read from socket: Connection reset by peer
Target libvirt log for the guest:
2017-08-18T12:09:08.730911Z qemu-system-x86_64: load of migration failed: Input/output error
2017-08-18 12:09:09.010+0000: shutting down, reason=crashed
Given the timing it seems that the actual copy now works (it is busy ~10 seconds on my environment which would be the copy).
Also we don't see the old errors we saw before, but afterwards on the actual take-over it fails.
Dmesg has no related denials as often apparmor is in the mix.
Need to check libvirt logs of source [2] and target [3] in Detail.
[1]: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02200.html
[2]: http://paste.ubuntu.com/25339356/
[3]: http://paste.ubuntu.com/25339358/
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1711602/+subscriptions
next prev parent reply other threads:[~2017-08-22 9:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <150305905460.11582.12289718300820278863.malonedeb@wampee.canonical.com>
2017-08-18 14:15 ` [Qemu-devel] [Bug 1711602] Re: --copy-storage-all failing with qemu 2.10 ChristianEhrhardt
2017-08-18 14:22 ` ChristianEhrhardt
2017-08-18 15:03 ` ChristianEhrhardt
2017-08-18 15:03 ` ChristianEhrhardt
2017-08-18 15:04 ` ChristianEhrhardt
2017-08-18 15:04 ` ChristianEhrhardt
2017-08-18 15:06 ` ChristianEhrhardt
2017-08-18 15:09 ` ChristianEhrhardt
2017-08-18 17:56 ` Dr. David Alan Gilbert
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:56 ` ChristianEhrhardt
2017-08-21 15:46 ` Dr. David Alan Gilbert
2017-08-22 8:51 ` ChristianEhrhardt
2017-08-22 8:54 ` ChristianEhrhardt
2017-08-22 8:58 ` ChristianEhrhardt [this message]
2017-08-22 9:01 ` ChristianEhrhardt
2017-08-22 9:08 ` ChristianEhrhardt
2017-08-22 9:26 ` Dr. David Alan Gilbert
2017-08-22 9:51 ` Dr. David Alan Gilbert
2017-08-22 10:20 ` ChristianEhrhardt
2017-08-22 10:57 ` Dr. David Alan Gilbert
2017-08-22 11:13 ` Dr. David Alan Gilbert
2017-08-22 11:14 ` ChristianEhrhardt
2017-08-22 11:18 ` ChristianEhrhardt
2017-08-22 11:23 ` Dr. David Alan Gilbert
2017-08-22 11:33 ` ChristianEhrhardt
2017-08-22 11:44 ` Dr. David Alan Gilbert
2017-08-22 11:46 ` Dr. David Alan Gilbert
2017-08-22 11:50 ` ChristianEhrhardt
2017-08-22 15:05 ` Dr. David Alan Gilbert
2017-08-22 15:47 ` ChristianEhrhardt
2017-08-22 17:57 ` ChristianEhrhardt
2017-08-22 19:21 ` ChristianEhrhardt
2017-08-23 8:02 ` Dr. David Alan Gilbert
2017-08-23 14:14 ` Stefan Hajnoczi
2017-08-23 14:41 ` Dr. David Alan Gilbert
2017-08-23 14:46 ` ChristianEhrhardt
2017-08-23 14:55 ` ChristianEhrhardt
2017-08-23 15:13 ` Eric Blake
2017-08-23 16:56 ` ChristianEhrhardt
2017-08-23 17:01 ` ChristianEhrhardt
2017-08-23 18:10 ` Dr. David Alan Gilbert
2017-08-23 18:55 ` Dr. David Alan Gilbert
2017-08-23 19:06 ` Dr. David Alan Gilbert
2017-08-23 19:10 ` ChristianEhrhardt
2017-08-23 21:02 ` ChristianEhrhardt
2017-09-02 8:04 ` Launchpad Bug Tracker
2017-12-15 16:10 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=150339233236.8725.2618271632756711348.malone@soybean.canonical.com \
--to=1711602@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.