Changes

Jump to: navigation, search

Migration from Linux-VServer to OpenVZ

78 bytes added, 10:50, 24 September 2008
m
Issues: put pararaphs instead of a list
== Issues ==
1. === Starting networking === The vserver-originating containers do not initialize network at all. Thus one needs to use following command to enable networking start (inside of the migrated container):
cd /etc/rcS.d
ln -s ../init.d/networking S40networking
2. === Disk space information === Disk space information is empty. Do the following to fix:
rm /etc/mtab
ln -s /proc/mounts /etc/mtab
3. === /dev === Vserver mounts /dev/pts filesystem for container transparently, whereas openvz does not. To compensate the ommission, you need to move aside /dev directory in the vserver-originating container and copy /dev directory from openvz based container. === /proc ===
4. The /proc filesystem is not automatically mounted by openvz. So the vserver needs to mount it itself. The simplests (not the best) way it can be done, is by sticking following command at the end of /etc/init.d/bootmisc.sh:
mount /proc
[[Category:HOWTO]]
2
edits

Navigation menu