Elastix KVM to OpenVZ problem

[bobdobelina]

Hi,

First let me say i am very impressed with Proxmox so far, with no previous experience creating a virtual environment i had a proxmox cluster up and running in under an hour.

I have an install of the elastix pbx system running on a KVM machine which i would like to convert to an openvz container....... is this possible?

I found these instructions http://wiki.openvz.org/Physical_to_container and tarred up the kvm image excluding:

.bash_history
/dev/*
/mnt/*
/tmp/*
/proc/*
/sys/*
/usr/src/*

and named the tar file: centos-5-elastix-pbx_2.9.7_amd64.tar.gz

this file was moved to /var/lib/vz/template/cache on the proxmox master and a new container created using the image. After the container starts i edit /var/lib/vz/private/{CTID}/etc/sysconfig/network-scripts/ifcfg-eth0 to show ONBOOT=no as shown in the instructions and restart the container.

Once the container has restarted i am unable to access it using the ip addresss assigned to the container......... took me awhile to realise the network was not starting up automatically with the container so via proxmox vnc i issue the commands:

Service network start

[root@FreshTest /]# service network start
Bringing up loopback interface:
[ OK ]
Start service venet0 (Y)es/(N)o/(C)ontinue? [Y] y
Bringing up interface venet0: [ OK ] [root@FreshTest /]#

And service httpd start

[root@FreshTest /]# service httpd start
Starting httpd: [ OK ]
[root@FreshTest /]#

Now everything seems ok and i can access the elastix web interface so i restart the container and again i need to do service network restart and service httpd start to get it working.

As elastix runs on centos i do setup>system services from the vnc and it shows network and http set to start automatically, however they obviously are not doing so for some reason.

Apart from getting the required services to start automatically with the container everything else seems to look ok if i start them up manually so if anyone can assist me by explaining why they may not be doing so i will be happy to share the final template with the community as payback.


Thanks for reading

 

[tom]

if you use venet, the network is configure OUTSIDE, means via the Proxmox VE gui. if you use veth, you need to configure it INSIDE the container.

see http://wiki.openvz.org/Differences_between_venet_and_veth

 

[bobdobelina]

Thanks for the reply Tom

Just to clarify the container is built using venet and the network does work but only after i manually start it by doing service network start in vnc... how would i go about enabling it to start with the container? I see no option in the GUI for this and other open vz templates with venet start ok, i am assuming it is something to do with th efact i have made thie template from a KVM install?

 

[tom]

I would install a basic OpenVZ container, and then I would move just the needed services, step by step.