CentOS 7 OpenVZ template in PVE 3.4 issues

[apmuthu]

To build a CentOS VPS from scratch refer:
Coding Tony
PowerPBX

Used a precreated CentOS 7 template to create an OpenVZ container.
Yum update it fully
The Network gets broken.

It appears that initscripts is broken in the latest version.
v9.49.24 seems to introduce problems with network connectivity from my testing on CentOS 7 OpenVZ templates.
v9.49.17 works fine, though.
You may like to try downgrading initscripts to 9.49.17 and rebooting the VM. Connectivity should be restored then.

# rpm -qa | grep initscripts
initscripts-9.49.24-1.el7.x86_64

Reverted to previous version:

wget ftp://bo.mirror.garr.it/pub/1/slc/centos/7.0.1406/os/x86_64/Packages/initscripts-9.49.17-1.el7.x86_64.rpm
rpm -Uvh --force initscripts-9.49.17-1.el7.x86_64.rpm
rm -f initscripts-9.49.17-1.el7.x86_64.rpm
systemctl restart network

Now check the install:

route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.0.2.1 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
localhost.local 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
localhost 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
loopback 0.0.0.0 255.255.255.0 U 0 0 0 venet0
default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0

The following links have more information:
http://www.webhostingtalk.com/showthread.php?t=1469441
http://forum.openvz.org/index.php?t...b480b858ed6dc2f2e28d149ae&srch=rhel#msg_51927

If the venet0:0 does not start up then put in the ONBOOT=yes parameter in the /etc/sysconfig/network-scripts/ifcfg-venet0:0 file.

Affects BlueOnyx OpenVZ Template for BX5209R based on CentOS 7:

The latest Official Beta BlueOnyx 5209R OpenVZ template can be used in PVE3.4 but fails to install on the web wizard:

cd /var/lib/vz/template/cache
wget http://devel.blueonyx.it/openvz/blueonyx-5209R-CentOS7-x86_64-BX01-20150204.tar.gz
mv "blueonyx-5209R-CentOS7-x86_64-BX01-20150204.tar.gz" "blueonyx-5209R-CentOS7_BX01-20150204-1_amd64.tar.gz"
cp /etc/vz/dists/redhat-7.3.conf /etc/vz/dists/blueonyx.conf

After creating the VPS with the above template, enable the Quotas (1000) and start it.

# bzip2 already installed
yum install nano zip unzip screen yum-utils
yum update

The networking gets broken and is fixed as outlined above.

cat /etc/build

build 20150212 for a 5209R in en_US

The web install fails at wizard.php

 

[feelFKO]

About BlueOnyx 5209R;

Although I think it was going well in such way. However,
after the latest yum, nobody will be able to access the container any more.

a. If using "blueonyx-5209R-CentOS7_BX01-20150204-1_amd64.tar.gz",
after restart, we are inaccessible to the container.

b. Also it is necessary "Network Status off" in blueonyx Active Monitor.
If not, we are inaccessible to the container after restart also.

The only success way in my test was;

1. mv "blueonyx-5209R-CentOS7-x86_64-BX01-20150204.tar.gz" "centos-7-blueonyx_5209R_7.0_x86_64.tar.gz"
2. pvectl create XXX centos-7-blueonyx_5209R_7.0_...
3. yum install nano zip unzip screen yum-utils ; yum update ;
4. Active Monitor -> Settings -> Move "Network Status" to off-Monitor Area
5. wget ftp://bo.mirror.garr.it/pub/1/slc/c...Packages/initscripts-9.49.17-1.el7.x86_64.rpm
6. rpm -Uvh --force initscripts-9.49.17-1.el7.x86_64.rpm
7. nano /etc/yum.conf; ## add "exclude=initscripts*" at last line.
8. yum update
9. reboot