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.
Created attachment 1646 [details] + .fs_flags = FS_VIRTUALIZED a hack
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
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.
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).
Patch added to kernel-feat-core-openvz-026test019-alt1.
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).
