I can confirm this does not work in precise, however it looks like
creating files (and directories etc) was not implemented in qemu-kvm
1.0. File creation was added with commit
daf0b9aca9f67323266af1a92e8ea06f9d7bf408 .
This should work in quantal - if it does not, then that is a new bug.
However adding a new feature in an SRU (especially to LTS) would be hard
to justify.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => 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/1018530
Title:
No write access in a 9p/virtfs shared folder
Status in QEMU:
New
Status in “qemu-kvm” package in Ubuntu:
Fix Released
Bug description:
Ubuntu version: Ubuntu 12.04 LTS
Kernel: 3.2.0-25-generic
Version of qemu-kvm: 1.0+noroms-0ubuntu13
I have created an shared folder for an virtual machine which is
managed by libvirt.
<filesystem type='mount' accessmode='passthrough'>
<source dir='/storage/data'/>
<target dir='data'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</filesystem>
I mounted it in the virtual machine with this command: mount -t 9p -o
trans=virtio,version=9p2000.L data /data
The filesystem permissions of all files an folders in the shared folder are
set to 777. I expected that I have the full permissions also in the virtual
machine.
Regardless of the permissions on the filesystem I cannot write or create
files and folders in the virtual machine. The original filesystem (/storage) is
XFS.
In another shared folder (similar config in libvirt) which is originally NTFS
I have no problems.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu13
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Wed Jun 27 20:15:20 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64
(20120409)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
TERM=xterm
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic
root=/dev/mapper/system-root ro
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1208
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1018530/+subscriptions
