New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) [UPDATE]

[martin]

Hi all,

We just released three new kernel branches, each one with minor feature differences.

For details see:
http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

We appreciate all feedback and bug reports in this forum.

Best regards,

Martin

 

[Ninjix]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Excellent news. Are there any specific test cases or environments the Proxmox Team is particularly interested in for the 2.6.32 branch? I'm looking forward to testing it tonight.

 

[obrienmd]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Fantastic! Looking forward to testing 2.6.32 on our staging whitebox... KSM would be huge for us (brings KVM memory footprint closer to OpenVZ territory).

 

[tom]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Excellent news. Are there any specific test cases or environments the Proxmox Team is particularly interested in for the 2.6.32 branch? I'm looking forward to testing it tonight.

no specific tests. the more you can do the better.

 

[tdi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

ok first test reboot.

See the attachement. On old kernel, as well as custom 2.6.31 works ok

 

[Nemesiz]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

ok first test reboot.

See the attachement. On old kernel, as well as custom 2.6.31 works ok

Edit fstab for /boot mount

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

See the attachement. On old kernel, as well as custom 2.6.31 works ok

Is that a standard installation? What kernel does not work? Whats the output of:

# pveversion -v

 

[mmenaz]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Since I've hardware that does not boot with current Proxmox 1.4 kernel, will it be possible have a new iso that asks what kernel use to boot and install?

 

[tom]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Since I've hardware that does not boot with current Proxmox 1.4 kernel, will it be possible have a new iso that asks what kernel use to boot and install?

yes, this is the plan.

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

See the attachement. On old kernel, as well as custom 2.6.31 works ok

Seems that initrd does not have the driver for /dev/sdb. What kind of hardware is that disk on? For testing, please can you try the following:

- boot with the new 2.6.32 kernel
- then update the initrd image with

# update-initramfs -c -t -k 2.6.24-10-pve

Can you boot the new 2.6.24 kernel afterwards?

If that does not help, try to add the lowlevel drivers to /etc/modules (and run update-initramfs).

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Or wait - what is the content of /dev/sdb on your system? Why is it required for boot?

 

[vpurger]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Similar problem, only with / dev / hdc, the additional disk mounted as / backup. It seems that the new kernel does not recognize the device.
If I remove the disk from the fstab, everything is ok.

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Similar problem, only with / dev / hdc, the additional disk mounted as / backup. It seems that the new kernel does not recognize the device.
If I remove the disk from the fstab, everything is ok.

Maybe the kernel just use another name for the device?

# ls /sys/block/

 

[tdi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Yes it was the problem, that the fstab had /dev/sdb1 as /boot but really it was /dev/sda1, i changed it.

I think the old pve kernel ignored it, the new one does not, so maybe installer has a bug and assigns wrong device.


Ive got one more bug, that is present in 1.4 and 1.5. When you have cluster like mine: node1, node2... node10 and you take down node2 and restart node1, which is master, the rest is out of sync, until you switch on node2. The problem is that master checks the nodes in order and after one node is down it does not go further.

 

[tom]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Yes it was the problem, that the fstab had /dev/sdb1 as /boot but really it was /dev/sda1, i changed it.

I think the old pve kernel ignored it, the new one does not, so maybe installer has a bug and assigns wrong device.


Ive got one more bug, that is present in 1.4 and 1.5. When you have cluster like mine: node1, node2... node10 and you take down node2 and restart node1, which is master, the rest is out of sync, until you switch on node2. The problem is that master checks the nodes in order and after one node is down it does not go further.

thanks, we will take a look on this. but the new cluster model is already under heavy development, so I hope you could live with this issue til the new version is out.

 

[mjoconr]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

2.6.32 is working well on the test Intel Modular Server I have here.

The multicpu migration issue while using linux seems to be better as long as virtio is not used (ie use e1000)

Mike

 

[tdi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

If can advice somthing, a clutering solution based on group communication or distributed concensus (like Paxos) would be best. Then there could be no master nad SPOF.

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

If can advice somthing, a clutering solution based on group communication or distributed concensus (like Paxos) would be best. Then there could be no master nad SPOF.

We will use 'corosync'.

 

[tdi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Great I can see it has concensus property and total ordering, so more or less the same, but even better as it has smaller communication footpront than Paxos.

Can't wait to test it

 

[chopeta]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

I was able to install 2.6.32 following the wiki procedures, but after reboot, I don't have network access.

Looking at the logs, looks like my network cards are not being detected by 2.6.32.

I had to boot up using the prev. kernel version (latest stable).

Any ideas?

Some info from my server:

w-pve7:~# pveversion -v
pve-manager: 1.4-10 (pve-manager/1.4/4403)
qemu-server: 1.1-8
pve-kernel: not correctly installed
pve-qemu-kvm: 0.11.0-2
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
w-pve7:~#

w-pve7:~# lspci
00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 4 (rev 12)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 12)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 12)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 12)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 12)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09)
02:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01)
03:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
05:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
06:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
06:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
07:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
0a:01.0 Multimedia audio controller: Creative Labs CA0106 Soundblaster
0b:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09)
10:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
w-pve7:~#