New Kernel for Proxmox VE 3.0 (pvetest)

[martin]

We just uploaded a new kernel to our pvetest repository, based on latest stable OpenVZ.

Release notes

- pve-kernel-2.6.32 (2.6.32-109)

• update to vzkernel-2.6.32-042stab079.5.src.rpm
• remove fix-ipoib-add-missing-lock.patch (now upstream)
• include Highpoint 2710 RAID driver (rr272x_1x

Everybody is invited to test the new kernel and give feedback.
__________________
Best regards,

Martin Maurer
Proxmox VE project leader

 

[ebiss]

Thanks

 

[joshuah]

just a quick question, how would i install this kernel ? i have Version: 3.0-0428106c-13 and i dont know how to implement this kernel into it? because at the moment i can not install proxmox because the drives are not detected (drives are connected to raid card)

Yes, i have the highpoint 2710 raid card.

 

[tom]

Either wait for a new ISO (3.1) or connect a supported hard disk (additionally) and install proxmox ve on this. then update the kernel and dd the whole disk to your raid volume.

 

[joshuah]

thanks for the quick reply.

Is there an approximate ETA for release of 3.1 ?

 

[hk@]

hi
installed this kernel and got a hard hit (yet again) during lvm-snapshot-backup of the VEs running on this box.

after the first VE backup everything residing on the lvm couldn't get successfull write anymore and all VEs failed by hanging.

even restarting vz was not possible anymore and the only way to solve the problem was a reset of the hardware.

cheers,
hk

 

[dietmar]

hi
installed this kernel and got a hard hit (yet again) during lvm-snapshot-backup of the VEs running on this box.

Again at the 'lvremove snapshot' stage?

 

[lynchie]

Again at the 'lvremove snapshot' stage?

Dietmar, can you look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718582 and the fix around the lvm remove hang. The changes in the udev rules for lvm2 (2.02.98-5) may help resolve this issue?

 

[dietmar]

Dietmar, can you look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718582 and the fix around the lvm remove hang. The changes in the udev rules for lvm2 (2.02.98-5) may help resolve this issue?

Already working on that.

 

[hk@]

obviously so, the logfile of the first VE to backup ends with:
Aug 13 00:00:02 INFO: creating archive '/mnt/pve/backup/dump/vzdump-openvz-10003-2013_08_13-00_00_01.tar.lzo'
Aug 13 01:49:29 INFO: Total bytes written: 59048263680 (55GiB, 8.6MiB/s)
Aug 13 01:53:37 INFO: archive file size: 35.85GB
Aug 13 01:53:38 INFO: delete old backup '/mnt/pve/backup/dump/vzdump-openvz-10003-2013_08_11-00_00_01.tar.lzo'

and that's it - usually the lvremove then happens but we have no evidence as we had to hurry to reboot the system to get the VEs back to work, after the reboot we could remove the snapshot without any issues.

 

[dietmar]

I just uploaded new lvm packages to the pvetest respository.

http://download.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/

clvm_2.02.98-pve4_amd64.deb
dmeventd_1.02.77-pve4_amd64.deb
dmsetup_1.02.77-pve4_amd64.deb
libdevmapper1.02.1_1.02.77-pve4_amd64.deb
libdevmapper-event1.02.1_1.02.77-pve4_amd64.deb
liblvm2app2.2_2.02.98-pve4_amd64.deb
liblvm2cmd2.02_2.02.98-pve4_amd64.deb
lvm2_2.02.98-pve4_amd64.deb

Anybody is invited to test - this hopefully fixes the lvremove bug.

 

[informant]

thanks @dietmar, can you create a pvetest version?

regards

 

[lynchie]

I just uploaded new lvm packages to the pvetest respository.

http://download.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/

clvm_2.02.98-pve4_amd64.deb
dmeventd_1.02.77-pve4_amd64.deb
dmsetup_1.02.77-pve4_amd64.deb
libdevmapper1.02.1_1.02.77-pve4_amd64.deb
libdevmapper-event1.02.1_1.02.77-pve4_amd64.deb
liblvm2app2.2_2.02.98-pve4_amd64.deb
liblvm2cmd2.02_2.02.98-pve4_amd64.deb
lvm2_2.02.98-pve4_amd64.deb

Anybody is invited to test - this hopefully fixes the lvremove bug.

Installed the updates and running a full backup right now. It's already onto CT 3 of 15 where it failed at the end of CT 1 previously. So looks like it resolved it for me!

 

[dietmar]

thanks @dietmar, can you create a pvetest version?

Sorry, I do not understand that question?

 

[ebiss]

Sorry, I do not understand that question?

I think it's mean we can use pvetest respo "apt-get update && apt-get dist-upgrade" get the fix

 

[informant]

hi,

sorry @dietmar, misstake. we have update and would test it on auto-backup. thanks

regards

 

[hk@]

Installed the updates and running a full backup right now. It's already onto CT 3 of 15 where it failed at the end of CT 1 previously. So looks like it resolved it for me!

did you a full-upgrade or just install the specific .deb files?

for me a full-upgrade offers to install also new packages:
glusterfs-client{a} glusterfs-common{a} libibverbs1{a} liblvm2app2.2{a} librdmacm1{a} socat{a}

where I'm not sure if I want to go down this road

regards
hk

 

[informant]

Hi, use http://pve.proxmox.com/wiki/Package_repositories pvetest reporsity

did you a full-upgrade or just install the specific .deb files?

for me a full-upgrade offers to install also new packages:
glusterfs-client{a} glusterfs-common{a} libibverbs1{a} liblvm2app2.2{a} librdmacm1{a} socat{a}

where I'm not sure if I want to go down this road

regards
hk

 

[hk@]

Hi
did that - now there has been added a new repo:

cat /etc/apt/sources.list.d/pve-enterprise.list
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

which seems to break updates for now...

I guess I should have gone with the individual files.

best, hk

 

[tom]

Hi
did that - now there has been added a new repo:

cat /etc/apt/sources.list.d/pve-enterprise.list
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

which seems to break updates for now...

no, this does not break the existing repo´s, ignore it. more info about this repo will be available soon.