Can't seem to reproduce if I convert the qcow2 image to raw+sparse.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1846427
Title:
4.1.0: qcow2 corruption on savevm/quit/loadvm cycle
Status in
Not sure if i have exactly the same problem, as my qcow2 corruption
seems to be limited to windows10 guests - win2019 and debian10 guests
with the same virtio-scsi setup are fine (as are various virtio-blk or
ide/sata images from linux/solaris/macos guests).
I find that i randomly have disk image
i've seen guest data corruption and qcow2 corruption on ext4.
i've seen one case where the guest (win10) reports corruption but qemu-
img check does not, but that's the outlier, usually both guest and qemu-
img report corruption.
for me the issue seems to only be win10 guests using virtio-scsi,
,
.valid.min_access_size = 2,
.valid.max_access_size = 4,
.endianness = DEVICE_LITTLE_ENDIAN,
};
regards.
On 13/07/2020 12:14, Michael S. Tsirkin wrote:
On Mon, Jul 13, 2020 at 10:20:12AM +0300, Michael Tokarev wrote:
12.07.2020 15:00, Simon John wrote:
macos guests no longer boot
,
.valid.min_access_size = 2,
.valid.max_access_size = 4,
.impl.min_access_size = 4,
.impl.max_access_size = 4,
.endianness = DEVICE_LITTLE_ENDIAN,
};
Regards.
--
Simon John
-By: Simon John
Signed-off-by: Michael Tokarev
Simon's explanation about the history is good to have here,
and I guess Fixes tags (both what you found and what Simon found)
can't hurt either. I would CC stable too.
Simon do you have the time to iterate on this patch or would
you rather have
Hi Mark,
Yes I am getting the emails from qemu-devel thanks (seems pretty slow
though - the website is faster) I replied to a couple but its over my
head mostly now!
I didn't notice Michael had done a v2 patch for 5.1, that's fine with
me.
I wonder if we can get the debian 5.0 package updated
Public bug reported:
The Debian Sid 5.0-6 qemu-kvm package can no longer get further than the
Clover bootloader whereas 5.0-6 and earlier worked fine.
So I built qemu master from github and it has the same problem, whereas
git tag v5.0.0 (or 4.2.1) does not, so something between v5.0.0 release
the debian patch is:
revert-memory-accept-mismatching-sizes-in-memory_region_access_valid-
CVE-2020-13754.patch
i'm currently building a deb package without it.
mailserver has a geoip block and doesn't use ipv6, synapticconsulting at
gmail dot com should work.
--
You received this bug
yup, building debian 5.0-6 package minus that single patch gives me
working macos catalina again.
now just got to figure out why any kernel newer than 5.5 crashes the
host when using pci passthrough - i don't fancy bisecting a whole
kernel!
--
You received this bug notification because you are
Hi Mark, no that doesn't work sorry, same error.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu after v5.0.0 breaks macos guests
Status in QEMU:
New
Bug description:
The
No that doesn't make any difference either, nor does combining the two
patches :-(
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu after v5.0.0 breaks macos guests
Status in
i get this over and over (and only this):
invalid size: acpi-tmr addr 0 size: 2
which seems to reside in hw/acpi/core.c
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu after
urgh, that was complicated, think i got it right!
need to look for "[PATCH] Allow acpi-tmr size=2" to show up in qemu-
devel
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu
ink: https://bugs.launchpad.net/qemu/+bug/1886318
Signed-off-by: Simon John
---
hw/acpi/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/acpi/core.c b/hw/acpi/core.c
index f6d9ec4f13..05ff29b9d7 100644
--- a/hw/acpi/core.c
+++ b/hw/acpi/core.c
@@ -527,7 +527,7 @@ s
on a hunch, i applied this, and now macos boots (as 2 from acpi-tmr fits
in the 1-4 range):
diff --git a/hw/acpi/core.c b/hw/acpi/core.c
index f6d9ec4f13..05ff29b9d7 100644
--- a/hw/acpi/core.c
+++ b/hw/acpi/core.c
@@ -527,7 +527,7 @@ static void acpi_pm_tmr_write(void *opaque, hwaddr addr,
all i get on stderr with my patch is:
invalid accepts: (null) addr fe03601c size: 4
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu after v5.0.0 breaks macos guests
Status in
Is this not the place to report qemu bugs?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1886318
Title:
Qemu after v5.0.0 breaks macos guests
Status in QEMU:
New
Bug description:
The Debian
qemu console screenshot, this is as far as it gets after clover:
https://i.imgur.com/HWY96Kq.png
same result with or without usb/pci passthrough, qxl/vnc, git master
HEAD or debian 5.0-6
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Thanks Mark, what an interesting exercise that was - and sorry, didn't
know 5.1 was due.
So the git bisect revealed this:
$ git bisect good
5d971f9e672507210e77d020d89e0e89165c8fc9 is the first bad commit
commit 5d971f9e672507210e77d020d89e0e89165c8fc9
Author: Michael S. Tsirkin
Date: Wed Jun
Woohoo! Simply reverting that one commit
5d971f9e672507210e77d020d89e0e89165c8fc9 from today's master gets me
running again.
Not sure where that leaves us though?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
21 matches
Mail list logo
