Sounds like this was an Ubuntu- or libvirt-specific bug ... so closing
this in the upstream QEMU bug tracker.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
With passthrough security model creation files in guest still doesn't
work in Raring.
QEMU version is 1.4.0,
AppArmor folder rules added to libvirt profile of tested VM,
Permissions on testing folder is 777.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Please file a new bug using 'ubuntu-bug libvirt-bin', providing details
on the setup and how it is failing.
--
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
Okay, it is working now. I am using the mapped security model but I wanted to
avoid it at first.
I hope proxy FS will be supported in quantal.
But I am still wondering why passthrough security is working smoothly
with NTFS-3G.
--
You received this bug notification because you are a member of
Georg,
pass-through security model needs root privilege, if you want to run
qemu as non-root user either you have to use mapped security model or
proxy fs driver. But libvirt does not have support for proxy FS driver.
I posted a patch few months ago to libvirt for enabling the same. I will
do the
qemu is running with user libvirt-qemu, not root.
--
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
Quoting M. Mohan Kumar (1018...@bugs.launchpad.net):
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
No, commit daf0b9aca9f67323266af1a92e8ea06f9d7bf408 added create
support proxy FS driver model. Local FS had support for creating files
much before.
Georg, is qemu running with root user privileges?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
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.
Thanks for reporting this bug. Could you check your /var/log/syslog for
apparmor messages relating to libvirt accessing /data? The command
sudo grep DENIED /var/log/syslog | grep libvirt
should return interesting results.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
No, there are no results relating /data. I would have wondered about it,
because I already configured apparmor to allow access to /data. The current
rules in the profile of the virtual machine are
/storage/data/ rw,
/storage/data/** rw,
I also disabled the apparmor profile but it didn't
** Also affects: qemu
Importance: Undecided
Status: New
--
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
12 matches
Mail list logo
