Bug 10054 - [FR] declare fuse fs_virtualized
: [FR] declare fuse fs_virtualized
Status: CLOSED FIXED
: Sisyphus
(All bugs in Sisyphus/kernel-feat-core-openvz)
: unstable
: all Linux
: P2 enhancement
Assigned To:
:
: http://forum.openvz.org/index.php?t=m...
:
:
:
  Show dependency tree
 
Reported: 2006-09-29 14:55 by
Modified: 2006-10-16 14:01 (History)


Attachments
+ .fs_flags = FS_VIRTUALIZED (323 bytes, patch)
2006-09-29 14:57, Michael Shigorin
no flags Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2006-09-29 14:55:29
While making LTSP installation in a VE more comfortable place, fuse was required
(for ltspfs).  Works fine on HN, but obviously not in VE.

This might just not work, but then it should be no worse (and will be reported).
 I've also suggested another filesystem testing workaround at %url.
------- Comment #1 From 2006-09-29 14:57:02 -------
Created an attachment (id=1646) [details]
+ .fs_flags = FS_VIRTUALIZED

a hack
------- Comment #2 From 2006-09-29 14:59:31 -------
this requires modprobe fuse on HN and /dev/fuse (c 10 229) also being made
available to VE (--devnodes fuse:rw), so should be reasonably safe for strangers
------- Comment #3 From 2006-10-05 15:17:31 -------
ACK: the proposed hack is safe enough, since requires explicit granting of
permissions to VE.

However, the correct way would be to virtualize FUSE correctly...
Added this to our TODO list, however this is low prio right now.
------- Comment #4 From 2006-10-13 20:51:43 -------
Thanks, Kirill.  Is there an OpenVZ FS virtualization HOWTO anywhere?

2 lakostis: would be nice to have in next ovz kernel, although maybe I'll care
myself (need local devices on terminals via ltspfs, hence the trouble).
------- Comment #5 From 2006-10-15 16:26:31 -------
Patch added to kernel-feat-core-openvz-026test019-alt1.
------- Comment #6 From 2006-10-16 14:01:05 -------
Michael, no... not yet :(
I think it will be solved by us quite soon, while working on NFS.

In general idea is simple: global variables should be analyzed and if its
meaning is about some local activity (not global one), then virtualized (i.e.
remade to be dynamic. e.g. moved to ve_struct).