<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
2012-01-20 00:38, John Knight skrev:
<blockquote cite="mid:4F18A958.5000508@classiccitytelco.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<tt></tt><br>
<blockquote type="cite"><tt>Why doesn't Debian use the
rhel6-openvz-kernel if that is the one that is maintained? <br>
Are you sure they use an outdated kernel? </tt></blockquote>
<br>
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 (<a moz-do-not-send="true"
href="http://wiki.openvz.org/Download/kernel/2.6.32">http://wiki.openvz.org/Download/kernel/2.6.32</a>).
The el6 version (<a moz-do-not-send="true"
href="http://wiki.openvz.org/Download/kernel/rhel6">http://wiki.openvz.org/Download/kernel/rhel6</a>)
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. <br>
</blockquote>
I did some reading on the openvz forum / wiki. They seems to also
update and fix the debian branch from what I found. Anyway I don't
have the time to build this server from scratch anyway so it will
have to stay the way it is unless it's seriously broken.<br>
<br>
For the next server I will research will further, and test out lxc
to see if it can replace openvz. I found some posts to this
mailinglist about lxc that seems to indicate that it works well, and
the methods are quite similar to openvz.<br>
<br>
<blockquote cite="mid:4F18A958.5000508@classiccitytelco.com"
type="cite"> <br>
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. <br>
<br>
<blockquote type="cite"><tt>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. </tt></blockquote>
<br>
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).<br>
<br>
Also, sorry to anyone if I've veered too far offtopic, I'm quite
interested and invested in openvz/asterisk/dahdi interoperability.<br>
</blockquote>
<br>
I'll keep you updated! Thanks for you input!<br>
<pre class="moz-signature" cols="72">--
Johan Wilfer email: <a class="moz-txt-link-abbreviated" href="mailto:johan@jttech.se">johan@jttech.se</a>
JT Tech | Developer webb: <a class="moz-txt-link-freetext" href="http://jttech.se">http://jttech.se</a></pre>
</body>
</html>