This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/117
** Changed in: qemu
Status: Triaged => Expired
** Bug w
** Changed in: qemu
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1500265
Title:
nested 9p filesystem with security_model=mapped-xattr
Status in QEMU:
Triage
The status of this issue is unchanged in QEMU, i.e. user.virtfs.* is
still filtered out.
If someone wants to see this changed, please use the common way for sending the
patch via ML:
https://wiki.qemu.org/Contribute/SubmitAPatch
--
You received this bug notification because you are a member of
Looking through old bug tickets... is this still an issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
h
Interesting approach. But maybe it should be configurable (eg. specify
the mapping prefix).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1500265
Title:
nested 9p filesystem with security_model=map
After looking at the code, it seems that disabling the user.virtfs
namespace was the intended behaviour. I have created a patch
implementing nesting instead of disabling.
I do not know if this is the right way to do it, but I did some limited
testing and it seemed ok.
** Patch added: "nested-virt
