What kernel does 1.4beta use?
- Thread starter Lantizia
- Start date
Well from what I understand it's like Ubuntu's 2.6.24 or something, with KVM and OpenVZ modules...
So... unless someone has a handy guide to how it was done for 2.6.24, I don't really want to attempt to make a 2.6.26.
It doesn't matter anyway, I'll probably end up making the machine using KVM anyway.
So... unless someone has a handy guide to how it was done for 2.6.24, I don't really want to attempt to make a 2.6.26.
It doesn't matter anyway, I'll probably end up making the machine using KVM anyway.
there is no benefit using openvz 2.6.26/27. we have all relevant patches.
our current kernel from 1.4 includes the very latest drivers for Intel, Broadcom and Realtek network cards, also ICH10 works. if anybody got an issue, pls post (we just released an update today, new iso will follow soon).
so what do you miss in our Kernel or what do you expect to better in a 2.6.26/27?
I don't miss anything, what I was thinking about doing (but probably won't now) was this...
Look at Untangle (www.untangle.com)... it's like an open source network gateway appliance (UTM) that runs on Debian Lenny. They have a baremetal installer like Proxmox does (also works in VMware) but also a repository and install script to install it on an existing Debian Lenny (like a debian lenny openvz template). But they use custom kernel patches to make a lot of their magic work.
So I was thinking about patching the proxmox kernel with their patches (which are designed for 2.6.26) and then maybe these patches would trickle down into the openvz template that is running untangle for it to access.
A crazy idea? Yes probably most definitely it is.
In the end I'll most likely put Untangle in a KVM machine instead.
I'm just going to have to accept that OpenVZ templates can not boot ISO images (no virtual BIOS)... and if whatever you want to run in them require custom kernels then look to KVM.
However I am haunted by stories that people are running asterisk in openvz containers which is dead easy... only that they are also using the digium PCI ISDN cards that do require certain kernel patches to use them I believe.
So I'm not sure what to think, only that using KVM will be a damn sight easier - if only slightly less in performance.
However check out Untangle, it does look bloody good... maybe someone will know better than me how easy it would be to get it running in an openvz container.
Look at Untangle (www.untangle.com)... it's like an open source network gateway appliance (UTM) that runs on Debian Lenny. They have a baremetal installer like Proxmox does (also works in VMware) but also a repository and install script to install it on an existing Debian Lenny (like a debian lenny openvz template). But they use custom kernel patches to make a lot of their magic work.
So I was thinking about patching the proxmox kernel with their patches (which are designed for 2.6.26) and then maybe these patches would trickle down into the openvz template that is running untangle for it to access.
A crazy idea? Yes probably most definitely it is.
In the end I'll most likely put Untangle in a KVM machine instead.
I'm just going to have to accept that OpenVZ templates can not boot ISO images (no virtual BIOS)... and if whatever you want to run in them require custom kernels then look to KVM.
However I am haunted by stories that people are running asterisk in openvz containers which is dead easy... only that they are also using the digium PCI ISDN cards that do require certain kernel patches to use them I believe.
So I'm not sure what to think, only that using KVM will be a damn sight easier - if only slightly less in performance.
However check out Untangle, it does look bloody good... maybe someone will know better than me how easy it would be to get it running in an openvz container.
Sorry could you elaborate on...
"no change to have this in OpenVZ."
Are you trying to say that this will run in OpenVZ fine? (in which case if it attempts to modify the kernel - will it work?)
Or are you saying "no change" as in no change to the fact it still won't work?
"no change to have this in OpenVZ."
Are you trying to say that this will run in OpenVZ fine? (in which case if it attempts to modify the kernel - will it work?)
Or are you saying "no change" as in no change to the fact it still won't work?
untangle is a turnkey linux box, including firewall. it makes no sense to install this in a container like openvz. but I am not the total expert in untangle, maybe just contact them what they think about openvz and KVM on Proxmox VE.
They've never tried to run it in either, only in VMWare...
Earlier you said "no change"
The untangle folks have looked at this post and think you might have meant "no chance"... was that a typo?
All I was asking in my last post was if an installation program goes about patching a kernel or adding new modules etc... would such a thing be successful (whether it is untangle or not) in an OpenVZ container... or (as I think) is the kernel untouchable from within the container?
Earlier you said "no change"
The untangle folks have looked at this post and think you might have meant "no chance"... was that a typo?
All I was asking in my last post was if an installation program goes about patching a kernel or adding new modules etc... would such a thing be successful (whether it is untangle or not) in an OpenVZ container... or (as I think) is the kernel untouchable from within the container?
yes, just a typo - sorry for confusion.
a container cannot touch the Kernel, you need to do this on the host if you need something special. the voip (asterisk) guys here in the forums got some howto, just use the search function.