vvfat core dump when enabling RW
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
[Impact]
* enabling vvfat with rw set breaks qemu once it writes something
* Fix is a backport of a small upstream fix
[Test Case]
* 1. get a guest that works (via uvtoools-libvirt or whatever you prever)
* 2. get the qemu commandline that it is started with, in my case:
$ sudo kvm -m 1024 -drive file=/dev/
* 3. create a dir and add a file to check to share in vvfat mode later
$ mkdir /tmp/sharevvfat
$ echo host > /tmp/sharevvfat
* 4. shutdown guest and start it again with the path as vvfat set to share rw mode, to do so append
-drive format=
* in the guest mount the block device and write to it
$ mount /dev/vdc1 /mnt
$ echo guest > /mnt/guestfoo
$ sync
Currently crashes:
qemu-system-x86_64: /build/
Expected: work to write files from guest and getting no fails/crashes
[Regression Potential]
* I'd consider the potential next-to-none for general qemu/kvm use cases
and low for cases using vvfat for the following reasons:
* The fix is local and only executed in vvfat code, so affecting other
qemu use cases should be next to impossible
* code is upstream and in further Ubuntu Releases quite a while without
issues showing up
* General regression checks showed no issue
[Other Info]
* n/a
---
Hi guys,
I'm getting this qemu crash message:
>>> qemu-system-x86_64: /build/
>>> Aborted (core dumped)
when launching qemu with this options for a VVFAT drive:
>>> -drive file=fat:
(same happens when using cache=none and/or if=ide)
"uname -a" system info is:
>>> Linux RJZ-WRK-LNX 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
and "qemu --version" is:
>>> QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-
Not sure what logs to attach but I'll be glad to upload whatever needed.
Thanks in advance for you help,
Rolando
description: | updated |
Moving to QEMU-Ubuntu since you're not using upstream QEMU (and the bug should have been fixed there as pointed out by Hervé on the qemu-devel mailing list).