[PVE-User] New 2.6.32 Kernel (pvetest)

[Charles Bijon]

I am forced to stay with a previous version of the kernel, because I 
have a kernel panik at boot time.

pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.9-50
pve-kernel-2.6.32-4-pve: 2.6.32-33 ( before )
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

if I put the latest version. The container loading machine kills the 
master. Do you have a way to make a log at startup if you want to track?

I also have another problem with the network portion. I use the 
libraries MICO for exchanges between services on OpenVZ containers. And 
this crash all time. What makes the use of cluster useless.

What can I do as a test to help you make the product better?

Sincerely,

Charles


Le 09/11/2011 14:24, Charles Bijon a écrit :
> Hi,
>
> It's correct kernel panik when we using cpu limit in OpenVZ contener ?
>
> Regards,
>
> Charles
>
> Le 09/11/2011 14:16, Martin Maurer a écrit :
>> Hi all,
>>
>> We just released a new kernel to the pvetest repository.
>>
>> Everybody is encouraged to test and give feedback before we move it 
>> to the stable repository.
>>
>> Release notes:
>>
>> - pve-kernel-2.6.32-6-pve (2.6.32-51)
>>
>>      update to vzkernel-2.6.32-042stab040.1.src.rpm
>>      removed fix-initlog-vzrst.diff (in upstream now)
>>
>> __________________
>> Best regards,
>> Martin Maurer
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user