Proxmox OpenVZ 64-bit 'rasterisk' not running?

[vanDivX]

Hi there, I jumped into it and got PIAF v1.4.0-3 - OpenVZ (64 bit) running in Proxmox which I installed as VM in VMware 7.0.1 (I will have dedicated Dell T310 server for Proxmox in July )

I had all over me when it went smoothly until I couldn't log into FPBX where I get database error. The initial FPBX interface loads but when I clicked on Administration button I got to log in panel (maint, passwd-master pass) which ended in database error, subsequent times even the login panel wouldn't show when clicking the FPBX Administration button and I would get page saying

FATAL ERROR

DB Error: connect failed

When I followed the WIKI page guide (http://pve.proxmox.com/wiki/PBX_in_a_Flash) I got to where in console you set up paswd-master which ran ok, then I ran 'rasterisk' command that you mention there and on the last line of the 'message' it generates, I get the following message: Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

I logged in via WinSCP and indeed there is no such file (asterisk.ctl) in asterisk directory

It could be why I can't log into FPBX (btw its easy now to specify static IP for your asterisk (also there is Network tab where it shows the IP and you can change it too), maybe because of newer Proxmox version than that which you were using when making the guide?)

I am gonna upload pictures of my * CLI so you see what I have running and what not

ftp://mir2.pointclark.net/OpenVZ-PIAF64-bit-console.jpg

ftp://mir2.pointclark.net/OpenVZ-PIAF64-bit-console-rasterisk.jpg

of course these two could be unrelated and when I sleep on it I will run orgasmatron or incredible installation and see what happens, it might just mean nothing. When I did installs from CD, I didn't do anything between initial install and the orgasmatron installation script running and I ran paswd-master at CLI and logged into FPBX at the end of running this script.

I have little question regarding Proxmox, I found when I installed it in VMware that I am not allowed to install KVMs since supposedly I do not have CPU with VT-x support. But I have i7-860 which it says on Intel site that it does support that. Only thing I can think of is that when Proxmox is run as VM in VMware, it can't access those features of the CPU regardless whether it is capable of those instructions or not. Or perhaps that is because the VMware Workstation v7.0.1 that I use is only 32-bit program?

And second question, I suppose your OpenVZ container wouldn't run on VMware ESXi platform? Not by any chance in hell? I ask because I am looking at ESX because I believe I should be able to gain access to my hardware Intel NIC which is otherwise not visible in VMware Workstation, nor in Proxmox, at least not when Proxmox runs in VM in VMware. I would like to run router/firewall as VMs and for that I need that access to my dual port NIC which I believe now I could get in ESXi installation (I found guide how to inject NIC drivers into ESX)
I suppose I could run VMware-Proxmox-PIAF_OpenVZ_64-bit AND VMware-ESXi_4.0-PointClark (now ClearCenter) but that gets all a bit too involved for my taste.
I should also mention that I know next to nothing about ESXi except that it is something very much like Proxmox but I don't know much about Proxmox either when it comes to it, I am quite amazed it lets itself be installed as VM and that one can install VMs inside that, rminds one of elephants standing on turtles backs or something like that

 

[wardmundy]

Proxmox 1.5 broke some of our OpenVZ stuff (not sure what or why). We just don't have time (nor the desire) to wrestle with. If anyone else wants to tackle it, by all means jump in.

KVM builds on Proxmox (and other VM platforms) still work just fine and yes we know this requires a special VM-compatible processor. The KVM approach provides an identical platform to a stand-alone machine so it has always been our first choice anyway.

 

[vanDivX]

I will try to back off to Proxmox v1.3 as what your guide was using --- I got as far as "Installing DAHDI on the Proxmox Server" and apt-get command 'is not found', I suppose there is some simple replacement for this command?

It looks like not only CPU but motherboard has to be VT-x compatible and I am not sure yet about the second (Gigabyte P55M-UD4)

Actually couldn't the reason for Proxmox reporting my CPU as not VT compatible because during VM setup in VMware (to install Proxmox into it) I accepted default CPU settings (1CPU, 1Core if I remember it right) for Debian 64-bit VMachine? Perhaps if I chose 2 or 4 Core CPU it might allow Proxmox to see my CPU as VT compatible?

BTW to bite you Proxmox with new kernel was announced just yesterday but download links weren't active yet last time I looked

 

[wardmundy]

Cores aren't the problem. VT-compatible is an entirely different chip design.

 

[TheShniz]

Proxmox with new kernel was announced just yesterday but download links weren't active yet last time I looked

There's not a new ISO for download, but you can simply upgrade new & existing installs with the current ISO... reboot IS required.

::edited::
Just follow the wiki, very easy

 

[TheShniz]

I think it's worth the bump to mention that:

1.) Kernel 2.6.32 does NOT support OpenVZ... but it DOES support KSM (for the first time, which is huge). Therefore, KVM-only.

2.) Kernel 2.6.24 DOES support OpenVZ... but it does NOT support KSM (nor do all previous kernels, 2.6.32 is the first).

There's currently alot of work going on to get OpenVZ into the 2.6.32 kernel; it is infact already available as developmental/unstable; and, the last ETA I saw was 'in a couple months'... which is a big step up from 'sometime next year'. KSM has alot of people giddy w/ container folks wondering 'when'.

::updated::
You can search for KSM; basically (in a nutshell), it's very efficient memory management for virtualized systems... whereas you can fit two to three times as many VM's in the same amount of memory as before (especially if those VM's are all linux/asterisk-based systems).

 

[wardmundy]

Any kernel above proxmox-ve-2.6.24 blows our OpenVZ setups completely out of the water. Now I see why!

 

[vanDivX]

I sorted all the above problems I had (went back to Proxmox 1.3) except getting my NIC recognized under Proxmox but its a hollow victory as the IncrediblePBX seems seriously messed up

Can't access extensions in FPBX and admin modules can't be downloaded, memory indicator in FPBX status shows yellow warning of high levels of memory being used and asterisk is indicated red with error (but shows running in console (Proxmox java console or Putty)...

I decided to call it quits but don't see it as a lost time, especially the comments by others that this thread sparked was enlightening

 

[wardmundy]

Hope these Proxmox developments clarify why we're not putting any more time into OpenVZ at least in the short term. Pretty sad, really. It was a terrific product!