Thanks for updating us on this issue, which turned out not to be a QEMU
bug.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1842787
Title:
Writes
Apologies, it looks like I ran into two separate bugs, one with XFS, and
one with BTRFS, that had the same symptom, initially making me to think
this must be a QEMU issue.
Using blktrace, I was able to see within the VM, that the virtio block
device wasn't getting the writes that were going into
On Thu, Sep 05, 2019 at 03:42:03AM -, James Harvey wrote:
> ** Description changed:
>
> Up to date Arch Linux on host and guest. linux 5.2.11. QEMU 4.1.0.
> Full command line at bottom.
>
> Host gives QEMU two thin LVM volumes. The first is the root filesystem,
> and the second
** Description changed:
Up to date Arch Linux on host and guest. linux 5.2.11. QEMU 4.1.0.
Full command line at bottom.
Host gives QEMU two thin LVM volumes. The first is the root filesystem,
and the second is for heavy I/O, on a Samsung 970 Evo 1TB.
When maxing out the I/O on
** Description changed:
Up to date Arch Linux on host and guest. linux 5.2.11. QEMU 4.1.0.
Full command line at bottom.
Host gives QEMU two thin LVM volumes. The first is the root filesystem,
and the second is for heavy I/O, on a Samsung 970 Evo 1TB.
When maxing out the I/O on
