2.6.32-4-pve, harddisk permanent write and kernelproblems

[fireon]

Hello folks

I have the following system
2.6.32-4-pve fresh from the installdisk.

For a few weeks ago i installed the new Proxmox VE on my server. Before I installed the new Proxmox, I saved all VMs with vzdump to an external hard drive. After recovery the system worked really fine.

For about 10 Days the Harddrive of the server read and write permanently. I can't say why!
It stopped when I stopped VMs, but always with a different VM ID. Also i could not identify the bad service on iotop . If you wait longer you have to reset the server.

Then i saw on the Screen of the server an kernelmessage.
I hope you can help me with this this problem.
http://www.osit.cc/pics/kern.log.txt
http://www.osit.cc/pics/pro_screen.jpeg

greetings

 

[tom]

pls also post the output of 'pveversion -v'

 

[fireon]

pls also post the output of 'pveversion -v'

pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.35: 1.6-6
pve-kernel-2.6.32-4-pve: 2.6.32-24
pve-kernel-2.6.35-1-pve: 2.6.35-6
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

This day i testet 2.6.35, but I have seen the kernel can not vz, so i startet 2.6.32-4 again.

 

[tom]

what about 2.6.18? with stable openVZ.

 

[fireon]

what about 2.6.18? with stable openVZ.

I don't understand you, because when i download the iso, kernel 2.6.32 is on Board. But this is unstable???

greetings

 

[tom]

For details about our kernels and their features, see http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

and yes, only 2.6.18 has a stable openvz.

 

[fireon]

Would you recommend to use two servers? One for OpenVZ with 2.6.18 and one for KVM with 2.6.32?

 

[tom]

KVM in 2.6.18 is also very good (more or less the same as you can find in RHEL 5.5/CentOS 5.5).

 

[fireon]

Ok, Thank you for your answer.

Greetings