I've been quite happy with Debian. Previously I was using BSD, and it was almost impossible to upgrade the system. And apt / dpkg have never failed me, very impressive. I guess rhel works well also, but I've little experience with it.

Debian is a great distribution as well.  I still use it as the container os to host web vps.  I think for OpenVZ usage though, it would be best to at least run your node software on the same distribution that is targeted via OpenVZ dev staff.  You shouldn't really be doing anything else on your node anyway, so the os type shouldn't really interfere I would think.  Though this argument breaks down when I suggest it to my Debian-using friends who seem to have a knee-jerk right hook coming my way when I mention rhel/centos.  :D

Why doesn't Debian use the rhel6-openvz-kernel if that is the one that is maintained?
Are you sure they use an outdated kernel?

I didn't see an "el6" tag on your kernel version that you first posted which means it's probably based on the 2.6.32 vanilla branch (http://wiki.openvz.org/Download/kernel/2.6.32).  The el6 version (http://wiki.openvz.org/Download/kernel/rhel6) is the only known actively developed branch of 2.6.32 that I know of.  I can't imagine Debian not packaging it up correctly by not reflecting the correct branch information.  Though it's only been a year and half since 2.6.32-el6 has been around, I've already seen quite a bit of bug fixes, security fixes and backports added to it so it's already diverging quite heavily from the vanilla branch.  Something that works flawlessly on 2.6.32-el6 might not work the same way on 2.6.32, and I'm wondering if this might be a cause of issues. 

To Digium: Does Digium test dahdi against a specific set of kernels such as 2.6.18-el5 and 2.6.32-el6 or do they only test against the vanilla upstream branches or a mixture?  Dahdi target platforms would be interesting to know in relation to the context of Johan's dahdi problem.

Maybe I will try switch to lxc instead of openvz as it is in the mainline kernel now. After all I need two things: Isolation, and the possibility to run multiple asterisk VEs on the same physical machine.

Hmm, I've never used lxc.  It definitely sounds interesting.  If you're going to implement it running Asterisk, I'd love to know if there are any issues or special methods required to get dahdi running (such as the DEVNODES feature in vz).

Also, sorry to anyone if I've veered too far offtopic, I'm quite interested and invested in openvz/asterisk/dahdi interoperability.

--

John Knight
Classic City Telco LLC
Email: j...@classiccitytelco.com | Main: (706) 995-0200
Direct: (706) 995-0201 | Mobile: (706) 255-9203


On 1/19/2012 6:17 PM, Johan Wilfer wrote:
2012-01-18 19:44, John Knight skrev:
"Have you used 64 bit kernels (amd64) in your setup? Distribution?"

Aye,  I use the current stable 64-bit rhel6 branch openvz kernel with centos 6 on the node and scientific linux 6 in the template without issue other than what I described before with res_timing_timerfd.so pegging the cpu and coring Asterisk.

Good to know that it is working! I've run i386 earlier, but thought it was time to try 64-bit.

It's never a suggestion a debian user wants to hear, but as the vanilla 2.6.32 openvz kernel has effectively been abandoned by the OpenVZ dev team in favor of the rhel6 version of 2.6.32, and since the node shouldn't really be doing anything other than hosting the templates, have you considered running centos6/rhel6-openvz kernel on the node and debian in the containers?   Just a suggestion, but no further openvz development is being done to the vanilla 2.6.32 branch and the rhel6 openvz kernel will consistently have bug fixes and and backports.

Not trying to start a distro war or anything, rather just a suggestion.

I've been quite happy with Debian. Previously I was using BSD, and it was almost impossible to upgrade the system. And apt / dpkg have never failed me, very impressive. I guess rhel works well also, but I've little experience with it.

Why doesn't Debian use the rhel6-openvz-kernel if that is the one that is maintained?
Are you sure they use an outdated kernel?

I have to read up on this, the next server maybe should use another distro for the HN.
Maybe I will try switch to lxc instead of openvz as it is in the mainline kernel now. After all I need two things: Isolation, and the possibility to run multiple asterisk VEs on the same physical machine.

-- 
Johan Wilfer                 email: jo...@jttech.se
JT Tech | Developer          webb: http://jttech.se


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to