Difference between revisions of "Porting Templates / Migrating OpenVZ Containers across PVE 1.x and PVE 2.x"
Jump to navigation
Jump to search
(Created page with "Due to recent (Jan 2013) changes in Console Access in PVE 2.x the following use cases need attention: * Backing up from PVE 1.x and restoring to PVE 2.x or vice versa * Deploying…") |
|||
| Line 4: | Line 4: | ||
== OpenVZ Template Design Issues in DAB == | == OpenVZ Template Design Issues in DAB == | ||
| + | === Startup Scripts === | ||
| + | * '''init rc''' was switched to '''insserv''' before PVE 1.9 itself and continues to be so in PVE 2.x | ||
| + | |||
| + | == /etc/inittab == | ||
| + | Recently (Jan 2013) PVE 2.2 switched to using the new Console Access method that uses a Virtualised a TTY Console. This requires the appending of the following line to the file /etc/inittab in the template and the recent versions of DAB do so without change to the DAB code - possibly through one of the debs / rpms. | ||
| + | |||
| + | 1:2345:respawn:/sbin/getty 38400 tty1 | ||
| + | |||
| + | Although [http://serverfault.com/questions/435181/entries-in-etc-inittab-below-last-line-possible-hack many hacks] have been found where code appended to the '''/etc/inittab''' have been the entry point, in this case it is intentional. | ||
| + | |||
| + | For PVE 1.x hosts, the OpenVZ containers should comment out the said line if present. | ||
== Migration Issues for OpenVZ Containers == | == Migration Issues for OpenVZ Containers == | ||
Revision as of 06:34, 30 January 2013
Due to recent (Jan 2013) changes in Console Access in PVE 2.x the following use cases need attention:
- Backing up from PVE 1.x and restoring to PVE 2.x or vice versa
- Deploying / Migrating OpenVZ containers based on OpenVZ templates designed for PVE 1.x (OpenVZ.org supplied templates and ProxmoxVE 1.x Templates) in PVE 2.x and viceversa
OpenVZ Template Design Issues in DAB
Startup Scripts
- init rc was switched to insserv before PVE 1.9 itself and continues to be so in PVE 2.x
/etc/inittab
Recently (Jan 2013) PVE 2.2 switched to using the new Console Access method that uses a Virtualised a TTY Console. This requires the appending of the following line to the file /etc/inittab in the template and the recent versions of DAB do so without change to the DAB code - possibly through one of the debs / rpms.
1:2345:respawn:/sbin/getty 38400 tty1
Although many hacks have been found where code appended to the /etc/inittab have been the entry point, in this case it is intentional.
For PVE 1.x hosts, the OpenVZ containers should comment out the said line if present.