From: Max Reitz <mreitz@redhat.com>
To: "Lukáš Doktor" <ldoktor@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-block@nongnu.org,
"Anton Nefedov" <anton.nefedov@virtuozzo.com>,
"Andrew Jones" <drjones@redhat.com>
Subject: Re: [Qemu-devel] Broken aarch64 by qcow2: skip writing zero buffers to empty COW areas [v2]
Date: Wed, 21 Aug 2019 19:51:19 +0200 [thread overview]
Message-ID: <b0b27c5c-c07a-527b-294a-c4e7ec6d4204@redhat.com> (raw)
In-Reply-To: <db672a84-0f30-bb82-ef94-c543e444372e@redhat.com>
On 21.08.19 16:14, Lukáš Doktor wrote:
> Hello guys,
>
> First attempt was rejected due to zip attachment, let's try it again with just Avocado-vt debug.log and serial console log files attached.
>
> I bisected a regression on aarch64 all the way to this commit: "qcow2: skip writing zero buffers to empty COW areas" c8bb23cbdbe32f5c326365e0a82e1b0e68cdcd8a. Would you please have a look at it?
I think I can see the issue on my x64 system (I don’t see the XFS
corruption, but the installation fails because of some segfaults).
I haven’t found a simpler way to reproduce the problem yet, though,
which is a pain... :-/
It looks like the problem disappears when I configure qemu with
“--disable-xfsctl”. Can you try that?
Max
next prev parent reply other threads:[~2019-08-21 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 14:14 [Qemu-devel] Broken aarch64 by qcow2: skip writing zero buffers to empty COW areas [v2] Lukáš Doktor
2019-08-21 15:49 ` Anton Nefedov
2019-08-21 16:23 ` Lukáš Doktor
2019-08-21 17:51 ` Max Reitz [this message]
2019-08-22 11:27 ` Lukáš Doktor
2019-08-22 12:09 ` Max Reitz
2019-08-22 15:25 ` Max Reitz
2019-08-22 15:40 ` Max Reitz
2019-08-22 16:32 ` Max Reitz
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=b0b27c5c-c07a-527b-294a-c4e7ec6d4204@redhat.com \
--to=mreitz@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=drjones@redhat.com \
--cc=ldoktor@redhat.com \
--cc=qemu-block@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).