[Users] OpenVZ NFS4/IdmapD

[kevin at dubourg.info]

Hello,

Sorry to up this old message but i have the same problem.

I try to configure NFV4 on a container (CT), i used the container as client.

My configuration (Debian/Squeeze):

pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1


I would like to use Idmap with NFSV4, to synchronize my account between NFS client and server.

I enable nfs and nfsd features on CT. But i have this message on the log when i try to start nfs-common :


Apr  9 21:33:17 rez10 rpc.idmapd[1798]: nfsdopenone: Opening /proc/net/rpc/nfs4.nametoid/channel failed: errno 2 (No such file or directory)


I search on google and i don't find a solution. However, i found this => comments.gmane.org/gmane.linux.openvz.user/4640

I extracting the most important :

Quote:
Having said that, only NFS v2 and NFS v3 are supported inside CT.

We are currently working on making NFS v4 work inside containers, but we do it for mainline
kernels rather than in RHEL6 kernel. So whenever we will port OpenVZ to any of 3.3 kernels,
it will most probably have NFS v4 support. RHEL7-based OpenVZ kernel will have it, too.

I successful mount my share in the CT with NFSV4, but idmapd not works.

For your information, NFSV4 + Idmapd works on the root host...

Could you please help me ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20130409/f69cdf53/attachment.html>