[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 1018530] Re: No write access in a 9p/virtfs shared
Re: [Qemu-devel] [Bug 1018530] Re: No write access in a 9p/virtfs shared folder
Tue, 10 Jul 2012 14:24:26 -0000
Quoting M. Mohan Kumar (address@hidden):
> No, commit daf0b9aca9f67323266af1a92e8ea06f9d7bf408 added create
> support proxy FS driver model. Local FS had support for creating files
> much before.
Yes, but that commit is not in v1.0 (according to qemu-kvm git
history at least)
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
No write access in a 9p/virtfs shared folder
Status in QEMU:
Status in “qemu-kvm” package in Ubuntu:
Ubuntu version: Ubuntu 12.04 LTS
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'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
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
Regardless of the permissions on the filesystem I cannot write or create
files and folders in the virtual machine. The original filesystem (/storage) is
In another shared folder (similar config in libvirt) which is originally NTFS
I have no problems.
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
Date: Wed Jun 27 20:15:20 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64
MachineType: To be filled by O.E.M. To be filled by O.E.M.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: American Megatrends Inc.
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.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.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: