It might be, I revisited a month back and could no longer trigger the
bug, so it's possible unrelated changes or kernel changes have fixed
the overlayfs copy-up semantics in cases where it would cause issues
with QEMU. If I ever see it again I can resubmit evidence, so it may
be better off closed.
Swamped with other work at the moment, but this hasn't been forgotten.
I might be able to take a look at it next week.
On Sat, 16 May 2020 at 12:55, Christian Schoenebeck
<1877...@bugs.launchpad.net> wrote:
>
> Yes, that compile error with QEMU + recent kernel headers is a bit
> annoying, and
I've tested it (eventually, hit
https://github.com/torvalds/linux/commit/467d12f5c7842896d2de3ced74e4147ee29e97c8
while trying to build it),
it doesn't help, since my program wasn't failing from attempting to
use O_NOATIME.
The following patch fixed the -ENOENT on file create for me. I also
Public bug reported:
QEMU Version: 3.1.0 as packaged in debian buster, but the code appears to do
the same in master.
qemu command-line: qemu-system-x86_64 -m 1G -nographic -nic
"user,model=virtio-net-pci,tftp=$(pwd),net=10.0.2.0/24,host=10.0.2.2" -fsdev
