Fixed in QEMU 5.1 release.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877688
Title:
9p virtfs device reports error when
Fix is now committed on master as SHA-1
cf45183b718f02b1369e18c795dc51bc1821245d, which actually just reverted the
mentioned commit that was leading to this broken behavior:
https://github.com/qemu/qemu/commit/cf45183b718f02b1369e18c795dc51bc1821245d
The original Xen transport bug that
Thanks, it works.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877688
Title:
9p virtfs device reports error when opening certain files
Status in QEMU:
In Progress
Bug description:
Reading
The following patch should fix this bug for the kvm backend (not for the
XEN backend yet).
Please let me know if it fixes this bug for you.
** Patch added: "bug1877688_kvm_fix.patch"
https://bugs.launchpad.net/qemu/+bug/1877688/+attachment/5369130/+files/bug1877688_kvm_fix.patch
** Changed
Looks like being introduced by this change:
https://patchwork.kernel.org/patch/11319993/
More specifically this one exactly:
-if (buf_size < size) {
+if (buf_size < P9_IOHDRSZ) {
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Here's a C program to trigger this behavior. I don't think it matters
what the contents of "file" or its size is.
** Description changed:
Reading certain files on a 9p mounted FS produces this error message:
qemu-system-x86_64: VirtFS reply type 117 needs 12 bytes, buffer has 12,
less
** Description changed:
Reading certain files on a 9p mounted FS produces this error message:
qemu-system-x86_64: VirtFS reply type 117 needs 12 bytes, buffer has 12,
less than minimum
After this error message is generated, further accesses to the 9p FS
hangs whatever tries to
