Migration from Linux-VServer to OpenVZ - Revision history

213.23.91.98: /* Issues */

2010-08-04T09:34:43Z

‎Issues

213.23.91.98: Remarks on Lenny as host

2010-08-04T09:26:50Z

Remarks on Lenny as host

213.252.4.92: correct syntax error in example

2010-07-08T15:08:16Z

correct syntax error in example

64.26.171.99: /* Starting networking in VEs */

2010-05-06T15:16:14Z

‎Starting networking in VEs

Jasond: /* Ubuntu udev */ formatting chages

2009-12-21T23:58:20Z

‎Ubuntu udev: formatting chages

Jasond: /* /dev */

2009-12-21T23:52:53Z

‎/dev

Jasond: Added note to remove udev from ubuntu guest

2009-12-21T23:51:23Z

Added note to remove udev from ubuntu guest

Niol: /* Issues */ more networking tips (Shorewall, routing)

2008-09-24T12:18:06Z

‎Issues: more networking tips (Shorewall, routing)

Niol: /* Issues */ put pararaphs instead of a list

2008-09-24T10:50:49Z

‎Issues: put pararaphs instead of a list

Skliarie: Issues: mount /proc filesystem

2008-08-25T11:07:40Z

Issues: mount /proc filesystem

← Older revision		Revision as of 09:34, 4 August 2010
Line 178:		Line 178:

	== Issues ==		== Issues ==
		+
		+	=== Starting ===
		+
		+	If starting fails with a message '''Unable to start init, probably incorrect template''' either the /sbin/init file is missing in the guest file system, or just not executable. Or the guest file system is completely absent or dislocated. The proper path where you must place is specified in the vz.conf file, namely the parameter VE_PRIVATE. For Debian this file can be found in /etc/vz.

	=== Networking ===		=== Networking ===

@@ Line 113: / Line 113: @@
 === Updating different configurations  ===
-Move the existing guest OSs to the right place:
+Get the existing guest OSs to the right place:
    # cd /vz
@@ Line 119: / Line 119: @@
    # mkdir private/345
    # mv /vservers/v345 /vz/private/345
 Now it is time for creating configuration files for OpenVZ container. Use the basic sample
@@ Line 125: / Line 130: @@
    # cd /etc/sysconfig/vz-scripts
    # cp ve-vps.basic.conf-sample 345.conf
 Now, let's set some parameters for the new container.
@@ Line 130: / Line 138: @@
 First, we need to tell which distro the container is running:
    # echo "OSTEMPLATE=\"fedora-core-4\"" >> 345.conf
 Then we set a few more parameters:

@@ Line 129: / Line 129: @@
 First, we need to tell which distro the container is running:
-   # echo "OSTEMPLATE="fedora-core-4" >> 345.conf
+   # echo "OSTEMPLATE=\"fedora-core-4\"" >> 345.conf
 Then we set a few more parameters:

@@ Line 175: / Line 175: @@
 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
+  update-rc.d networking defaults
 ==== Migrating your VServer Shorewall setup ====

@@ Line 203: / Line 203: @@
 Additionally, Ubuntu based vservers have the udev package installed which prevents access to the console in openvz. This error message is an example of the problem:
-<code>
+ # vzctl enter 345
-# vzctl enter 101
+ enter into CT 345 failed
-enter into CT 101 failed
+ Unable to open pty: No such file or directory
 The fix is to remove the udev package from the guest:
-<code>
-# vzctl exec 101 'dpkg --force-depends --purge udev'
+ # vzctl exec 345 'dpkg --force-depends --purge udev'
-(Reading database ... dpkg: udev: dependency problems, but removing anyway as you request:
+ (Reading database ... dpkg: udev: dependency problems, but removing anyway as you request:
- initramfs-tools depends on udev (>= 117-5).
+  initramfs-tools depends on udev (>= 117-5).
 files and directories currently installed.)
-Removing udev ...
+ Removing udev ...
-Purging configuration files for udev ...
+ Purging configuration files for udev ...
-dpkg - warning: while removing udev, directory `/lib/udev/devices/net' not empty so not removed.
+ dpkg - warning: while removing udev, directory `/lib/udev/devices/net' not empty so not removed.
-dpkg - warning: while removing udev, directory `/lib/udev/devices' not empty so not removed.
+ dpkg - warning: while removing udev, directory `/lib/udev/devices' not empty so not removed.
-</code>
 Now restart the container, you should now be able to use the console.
-# vzctl enter 101
+ # vzctl restart 345
-entered into CT 101
+ Restarting container
-root@test:/#
+ ...
-</code>
+  <SNIP>
 === /proc ===

← Older revision		Revision as of 23:51, 21 December 2009
Line 198:		Line 198:

	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.		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.
		+
		+	Additionally, Ubuntu based vservers have the udev package installed which prevents access to the console in openvz. This error message is an example of the problem:
		+
		+	<code>
		+	# vzctl enter 101
		+	enter into CT 101 failed
		+	Unable to open pty: No such file or directory
		+	</code>
		+
		+	The fix is to remove the udev package from the guest:
		+
		+	<code>
		+	# vzctl exec 101 'dpkg --force-depends --purge udev'
		+	(Reading database ... dpkg: udev: dependency problems, but removing anyway as you request:
		+	initramfs-tools depends on udev (>= 117-5).
		+	15227 files and directories currently installed.)
		+	Removing udev ...
		+	Purging configuration files for udev ...
		+	dpkg - warning: while removing udev, directory `/lib/udev/devices/net' not empty so not removed.
		+	dpkg - warning: while removing udev, directory `/lib/udev/devices' not empty so not removed.
		+	</code>
		+
		+	Now restart the container, you should now be able to use the console.
		+
		+	<code>
		+	# vzctl restart 101
		+	Restarting container
		+	...
		+	<SNIP>
		+	...
		+	Container start in progress...
		+
		+	# vzctl enter 101
		+	entered into CT 101
		+	root@test:/#
		+	</code>
		+

	=== /proc ===		=== /proc ===

@@ Line 170: / Line 170: @@
 == Issues ==
-=== Starting networking ===
+=== 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
 === Disk space information ===

@@ Line 170: / Line 170: @@
 == Issues ==
-. 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):
+=== Starting networking ===
   cd /etc/rcS.d
   ln -s ../init.d/networking S40networking
-. Disk space information is empty. Do the following to fix:
+=== Disk space information ===
   rm /etc/mtab
   ln -s /proc/mounts /etc/mtab
-. 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.
+=== /dev ===
-. 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:
+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]]

← Older revision		Revision as of 11:07, 25 August 2008
Line 179:		Line 179:

	3. 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.		3. 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.
		+
		+	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]]		[[Category:HOWTO]]