Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Hey, does 2.6.18 kernel debugged? With VMs rebooting inside fix?
Hey, does 2.6.18 kernel debugged? With VMs rebooting inside fix?
New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) [UPDATE]
- Thread starter martin
- Start date
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Sorry, I do not understand that question?
Sorry, I do not understand that question?
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
I ask, or to correct any errors in that time was, for example, it was not possible to restart the VPS;or kernel sysmsgd errors;or when I try to migrate LIVE from 2.6.18 to 2.6.18, I received errors on the lo venet0 interfaces and they waited when they becomes available. They load all the text in its console
I ask, or to correct any errors in that time was, for example, it was not possible to restart the VPS;or kernel sysmsgd errors;or when I try to migrate LIVE from 2.6.18 to 2.6.18, I received errors on the lo venet0 interfaces and they waited when they becomes available. They load all the text in its console
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Ah, yes - i remember that thread. But I was never able to reproduce those errors, sorry (it works perfectly here).
Ah, yes - i remember that thread. But I was never able to reproduce those errors, sorry (it works perfectly here).
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
So bugs are fixed and i can install it without any problems?
Actually I need to do:
apt-get update
apt-get dist-upgrade
apt-get upgrade
apt-get --reinstall proxmox-ve-2.6.18
because, i had installed old one kernel
yes?
So bugs are fixed and i can install it without any problems?
Actually I need to do:
apt-get update
apt-get dist-upgrade
apt-get upgrade
apt-get --reinstall proxmox-ve-2.6.18
because, i had installed old one kernel
yes?
Last edited:
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Hi all,
I also have exactly the same problem with my freshen installed 2.6.32 kernel (KVM) + KSM.
I started an Arch Linux distrib with 2 x r8169 nic.
After few seconds, the entire network freeze : the only this that goes on working is the VNC console (thanks god !).
I tryied selecting another driver e1000 (for example), without any success.
I finally solved this problem allowing ACPI in the VM Options (before my upgrade, I ran this VM on a proxmox 1.1 with that option disallowed).
Since them, it works like a charme.
Hope this helps.
Cheers.
Hi all,
I also have exactly the same problem with my freshen installed 2.6.32 kernel (KVM) + KSM.
I started an Arch Linux distrib with 2 x r8169 nic.
After few seconds, the entire network freeze : the only this that goes on working is the VNC console (thanks god !).
I tryied selecting another driver e1000 (for example), without any success.
I finally solved this problem allowing ACPI in the VM Options (before my upgrade, I ran this VM on a proxmox 1.1 with that option disallowed).
Since them, it works like a charme.
Hope this helps.
Cheers.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Found incompatibility between the kernel 2.6.18 and Apache 2.2.12 (Debian), 64 bit, prefork. There are huge memory leaks, apache does not release memory and does not terminate child processes after the end of request serving.
With the kernel 2.6.24 everything is OK.
Found incompatibility between the kernel 2.6.18 and Apache 2.2.12 (Debian), 64 bit, prefork. There are huge memory leaks, apache does not release memory and does not terminate child processes after the end of request serving.
With the kernel 2.6.24 everything is OK.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
I think that it is very hard to reproduce, because we use a very complex set of PHP-scripts that performs lots of different operations. I have noticed the effect on the production server after its planned night migration onto Proxmox VE 1.5 (with 2.6.18 kernel) from Proxmox 1.4 (with 2.6.24 kernel). In the morning, when users began to use server actively, the memory has finished and the server failed. I have rolled everything back and the effect disappeared.
I am ready to beleive that it is a bug of Apache.
I think that it is very hard to reproduce, because we use a very complex set of PHP-scripts that performs lots of different operations. I have noticed the effect on the production server after its planned night migration onto Proxmox VE 1.5 (with 2.6.18 kernel) from Proxmox 1.4 (with 2.6.24 kernel). In the morning, when users began to use server actively, the memory has finished and the server failed. I have rolled everything back and the effect disappeared.
I am ready to beleive that it is a bug of Apache.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Where do you run that php scripts - on the host or inside an OpenVZ guest?
Where do you run that php scripts - on the host or inside an OpenVZ guest?
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Of course I run my PHP-scripts inside the OpenVZ guest.
Of course I run my PHP-scripts inside the OpenVZ guest.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
As addition to my replies. I have also noticed that some my very simple "standalone" PHP scripts after migration to 2.6.18 kernel issue segmentation faults. It is very strange, because these scripts contain only 30-40 lines of code and use nothing except MySQL database.
As addition to my replies. I have also noticed that some my very simple "standalone" PHP scripts after migration to 2.6.18 kernel issue segmentation faults. It is very strange, because these scripts contain only 30-40 lines of code and use nothing except MySQL database.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
So it is maybe a php problem. Maybe you can try to debug (strace, ...)
So it is maybe a php problem. Maybe you can try to debug (strace, ...)
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
May be, may be...
I shall try to find it out as a sporting interest. But the bug does not appear in enough stable way. I'm afraid that I'm not able simply to catch this and to understand what I'm dealing with.
May be, may be...
I shall try to find it out as a sporting interest. But the bug does not appear in enough stable way. I'm afraid that I'm not able simply to catch this and to understand what I'm dealing with.
B
baserz
Guest
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Any eta on the multikernel iso installer perhaps?
Any eta on the multikernel iso installer perhaps?
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
no, you should update to the latest 1.5 as there are also fixes in other packages, e.g. vzctl.
no, you should update to the latest 1.5 as there are also fixes in other packages, e.g. vzctl.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
is the possibility to change the kernel after installation not enough for you, why?
is the possibility to change the kernel after installation not enough for you, why?
B
baserz
Guest
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
Because my controller in my new server(will be ready for installation in a couple of days) dont seem to be supported in the default proxmox kernel as i understand, as i understand 2.6.32 is needed. As noted by ninjix earlier, installing on a single drive, upgrade kernel and then clone the drive onto the controller raid seem to have worked for him, but a installer iso with the option of the newer kernel would ofcourse be smashingly excellent
So the answer to your question using one sentence, raid controller hardware support.
Because my controller in my new server(will be ready for installation in a couple of days) dont seem to be supported in the default proxmox kernel as i understand, as i understand 2.6.32 is needed. As noted by ninjix earlier, installing on a single drive, upgrade kernel and then clone the drive onto the controller raid seem to have worked for him, but a installer iso with the option of the newer kernel would ofcourse be smashingly excellent
So the answer to your question using one sentence, raid controller hardware support.
B
baserz
Guest
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
And only asked because i got the understanding that multikernel installer was something you guys was thinking of fixing already.
And only asked because i got the understanding that multikernel installer was something you guys was thinking of fixing already.
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)
which raid controller? pls provide a link. (fyi, there was a bug in the first 1.5 ISO images, but already fixed in the current 1.5 ISO)
Because my controller in my new server(will be ready for installation in a couple of days) dont seem to be supported in the default proxmox kernel as i understand, as i understand 2.6.32 is needed. As noted by ninjix earlier, installing on a single drive, upgrade kernel and then clone the drive onto the controller raid seem to have worked for him, but a installer iso with the option of the newer kernel would ofcourse be smashingly excellent
So the answer to your question using one sentence, raid controller hardware support.
which raid controller? pls provide a link. (fyi, there was a bug in the first 1.5 ISO images, but already fixed in the current 1.5 ISO)