NFS Kernel Server in openvz container

[knireis]

Just discovered that since vzctl-3.0.24, it is possible to use a nfs-kernel-server in a container. It works quite well.

For more info: http://wiki.openvz.org/NFS_server_inside_container

 

[jmrivera]

i have a problem after apply that option

vzctl set 102 --features "nfsn" --save

WARNING: Some of the parameters could not be applied to a running container.
Please consider using --setmode option
vzctl : CT 102 : Saved parameters for CT 102

after that i tryed to shutdown the vm

Stopping container ...
vzctl : CT 102 : unable to change dir to /mnt/pve/VZContainers/102: No such file or directory

look directory and that folder of the vm it doesnt exist

when i did that the vm machine was running.


do you have any solution for this??

 

[knireis]

what version of pve do you run?

 

[udo]

...
vzctl : CT 102 : unable to change dir to /mnt/pve/VZContainers/102: No such file or directory
...

Hi,
on a pve-installation the path for openvz-vm are /var/lib/vz/private/VMID - so the question is what do you have changed?

 

[jmrivera]

My Kernel version is

2.6.32-4-pve

yes i changed to a NFS Share folder in an OPENFILER BOX :

My vz.conf look like this:

## Global parameters
VIRTUOZZO=yes
LOCKDIR=/mnt/pve/VZContainers/lock
DUMPDIR=/mnt/pve/VZContainers/dump
VE0CPUUNITS=1000

## Logging parameters
LOGGING=yes
LOGFILE=/var/log/vzctl.log
LOG_LEVEL=0
VERBOSE=0

## log output of init process to $VE_ROOT/var/log/init.log
INITLOG=yes

## Disk quota parameters
DISK_QUOTA=yes
VZFASTBOOT=no

# Disable module loading. If set, vz initscript do not load any modules.
#MODULES_DISABLED=yes

# The name of the device whose IP address will be used as source IP for CT.
# By default automatically assigned.
#VE_ROUTE_SRC_DEV="eth0"

# Controls which interfaces to send ARP requests and modify APR tables on.
NEIGHBOUR_DEVS=detect

## Fail if there is another machine in the network with the same IP
ERROR_ON_ARPFAIL="no"

## Template parameters
TEMPLATE=/var/lib/vz/template

## Defaults for containers
VE_ROOT=/mnt/pve/VZContainers/$VEID
VE_PRIVATE=/mnt/pve/VZContainers/$VEID
CONFIGFILE="basic"
DEF_OSTEMPLATE="centos-5"

## Load vzwdog module
VZWDOG="no"

## IPv4 iptables kernel modules
IPTABLES="ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length"

## Enable IPv6
IPV6="no"

## IPv6 ip6tables kernel modules
IP6TABLES="ip6_tables ip6table_filter ip6table_mangle ip6t_REJECT"

only changed LOCKDIR,DUMPDIR, VE_ROOT and VE_PRIVATE

after i change my file vz.conf, all my OpenVZ VM was created in this NFS Mounted folders, but when apply the TIP to have NFS Suport on my VM all my VM files desappear from the directory where they were initially, and my VM is broke.

 

[jmrivera]

No one have some response to know if there is a BUG or i am wrong in something ?

Thanks for your help

Best regards

 

[knireis]

for me, on a standard proxmox 1.9 it works fine, but since you changed things i don't know if it is because of the changes of because you made a mistake