qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Commit 'iomap: add support for dma aligned direct-io' causes qemu/KV


From: Paolo Bonzini
Subject: Re: Commit 'iomap: add support for dma aligned direct-io' causes qemu/KVM boot failures
Date: Thu, 29 Sep 2022 19:35:43 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1

On 9/29/22 18:39, Christoph Hellwig wrote:
On Thu, Sep 29, 2022 at 10:37:22AM -0600, Keith Busch wrote:
I am aware, and I've submitted the fix to qemu here:

  https://lists.nongnu.org/archive/html/qemu-block/2022-09/msg00398.html

I don't think so. Memory alignment and length granularity are two completely
different concepts. If anything, the kernel's ABI had been that the length
requirement was also required for the memory alignment, not the other way
around. That usage will continue working with this kernel patch.

Well, Linus does treat anything that breaks significant userspace
as a regression.  Qemu certainly is significant, but that might depend
on bit how common configurations hitting this issue are.

Seeing the QEMU patch, I agree that it's a QEMU bug though. I'm surprised it has ever worked.

It requires 4K sectors in the host but not in the guest, and can be worked around (if not migrating) by disabling O_DIRECT. I think it's not that awful, but we probably should do some extra releases of QEMU stable branches.

Paolo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]