Results 1 to 45 of 45

Thread: New 2.6.32 Kernel for Proxmox VE 2.1 stable

  1. #1
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    380

    Default New 2.6.32 Kernel for Proxmox VE 2.1 stable

    We just moved our latest kernel to the stable repository. This one is based on the latest stable OpenVZ kernel.

    Release notes

    - pve-kernel-2.6.32-12-pve: 2.6.32-68


    • update to vzkernel-2.6.32-042stab055.10.src.rpm
    • increase API version to 12-pve
    • remove megaraid_sas-mask-off-flags-in-ioctl-path.patch (now upstream)
    • update e1000e to 1.11.3
    • update igb to 3.4.7
    • update ixgbe to 3.9.15
    Best regards,
    Martin

    Do you have already a Commercial Support Subscription? - If not, Buy now

  2. #2
    Join Date
    Mar 2010
    Location
    Stuttgart / Germany
    Posts
    342

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    hi martin,

    is it possible to use this kernel on an updated pve 1.9 ?

    thank you

  3. #3
    Join Date
    Aug 2006
    Posts
    9,742

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    no. 1.9 is outdated, plan the upgrade.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  4. #4
    Join Date
    May 2012
    Posts
    6

    Thumbs up Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by martin View Post
    We just moved our latest kernel to the stable repository. This one is based on the latest stable OpenVZ kernel.

    Release notes

    - pve-kernel-2.6.32-12-pve: 2.6.32-68


    • update to vzkernel-2.6.32-042stab055.10.src.rpm
    • increase API version to 12-pve
    • remove megaraid_sas-mask-off-flags-in-ioctl-path.patch (now upstream)
    • update e1000e to 1.11.3
    • update igb to 3.4.7
    • update ixgbe to 3.9.15
    Thanks very much, but where can I find the sources?
    The repository @ https://git.proxmox.com/?o=age seems to be outdated...

    Best regards,
    Soal

  5. #5
    Join Date
    May 2012
    Location
    Jakarta, Indonesia
    Posts
    180

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    1. How to update? I have run apt-get update and upgrade but still 2.6.32-11-pve listed
    2. Do you provide this Update in Web Interface? Such as tick to automatically update
    3. Do you provide which update list selected? Such as, update to: latest or stable version? So admin can choose latest version for their dev server while stable was choosen for production server

  6. #6
    Join Date
    Apr 2012
    Location
    Copenhagen, Denmark
    Posts
    1,621

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by kotakomputer View Post
    1. How to update? I have run apt-get update and upgrade but still 2.6.32-11-pve listed
    apt-get dist-upgrade

  7. #7
    Join Date
    May 2012
    Location
    Clermont-Ferrand, France
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by martin View Post
    We just moved our latest kernel to the stable repository. This one is based on the latest stable OpenVZ kernel.

    Release notes

    - pve-kernel-2.6.32-12-pve: 2.6.32-68


    • update to vzkernel-2.6.32-042stab055.10.src.rpm
    • increase API version to 12-pve
    • remove megaraid_sas-mask-off-flags-in-ioctl-path.patch (now upstream)
    • update e1000e to 1.11.3
    • update igb to 3.4.7
    • update ixgbe to 3.9.15
    Hello,

    I just did the upgrade from 1.9 to 2.1 and now we are having seemingly random TCP connection issues.
    While most users access network resources without any problem, others are experiencing timeouts on various services such as proxy, http, smtp, etc.
    Tcpdump shows that the TCP SYN packets are going unanswered.
    Any ideas ?

    Thank you in advance.

  8. #8
    Join Date
    May 2011
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Hello

    Today I made ​​a fresh install of Proxmox 2.0 on a Intel Modular Server, and when I upgraded the kernel to version 2.6.32-12 the network has stopped working.

    I restarted with the 2.6.32-11 kernel and the network has become operational. I think it's a bug.

    Someone with an IMS could confirm this?

  9. #9
    Join Date
    May 2012
    Location
    Clermont-Ferrand, France
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by j5boot View Post
    Hello

    Today I made ​​a fresh install of Proxmox 2.0 on a Intel Modular Server, and when I upgraded the kernel to version 2.6.32-12 the network has stopped working.

    I restarted with the 2.6.32-11 kernel and the network has become operational. I think it's a bug.

    Someone with an IMS could confirm this?
    Faced with the same problem on a Dell R610 server, I tried ALL the 2.6.32 kernels (including the 2.6.32-11) with no luck at all. I had to downgrade to Proxmox 1.9 to get the darned thing working again !

  10. #10
    Join Date
    Aug 2006
    Posts
    9,742

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    We test all releases also on our IMS in the test lab, no issues here.

    we have this here:
    http://pve.proxmox.com/wiki/Intel_Mo...ompute_Modules

    any details about your IMS?
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  11. #11
    Join Date
    Dec 2011
    Posts
    8

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    About 4 weeks ago I posted about Problems with flapping Network Link on IMS.
    http://forum.proxmox.com/threads/939...3213#post53213

    I tried to Update the e1000e to 1.11.3 and the Kernel crashed. Now this Version is integrated in pve-kernel-2.6.32-12-pve with the same Result. The Kernel seems to crashed somewhere beetween megasas and e1000e.
    I try to get a whole Crashdump.
    Last edited by bbaumer; 05-24-2012 at 05:06 PM.

  12. #12
    Join Date
    Dec 2011
    Posts
    8

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Here's the Output from
    - Remote Serial Console
    - Remote KVM

    ---
    Code:
    Build 086 (WfM 2                                                                                                                                                        
                                                                                                                                                                                                                                                    Initializing cgroup subsys cpuset                                                               
     node 0 0000000000000000-0000000460000000                                                                                                                               
                                                                                                                                                                                                            Initializing cgroup subsys cpuset                                                                                                       
    Hierarchical RCU implementation..                                                                                                                                       NR_IRQS:33024 nr_irqs:880                                                                                                                                               
    Extended CMOS year: 2000ODUCT          REVISION   SIZE \ NV                                                                                                             
    Console: colour VGA+ 80x25------------ ---------- ---------                                                                                                             console [tty0] enabledMulti-Flex0GHz st0308ng 0a      10 GB                                                                                                             
    console [ttyS0] enabledulti-FlexCore2 e0308           10 GB                                                                                                             hpet clockevent registered064E-IR      1.30.00.00  NV 2D:00                                                                                                             
    Fast TSC calibration using PIT                                                                                                                                          
    Detected 2493.691 MHz processor.                                                                                                                                        Calibrating delay loop (skipped), value calculated using timer frequency.. 4987.38 BogoMIPS (lpj=2493691)                                                               
    pid_max: default: 1048576 minimum: 301ff                                                                                                                                Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)                                                                                                    
    Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)                                                                                                      
    Mount-cache hash table entries: 256                                                                                                                                     Initializing cgroup subsys cpuacct2 #3 #4 #5 #6 #7 Ok.                                                                                                                  
    Initializing cgroup subs counter.                                                                                                                                       Booting Node   0, Processors  #1 #2 #3 #4 #5 #6 #7 Ok.                                                                                                                  
    Brought up 8 CPUsytes                                                                                                                                                   
    Total of 8 processors activated (39900.14 BogoMIPS).                                                                                                                    
    sizeof(vma)=200 byteses                                                                                                                                                 
    sizeof(page)=64 bytestes                                                                                                                                                
    sizeof(inode)=664 bytes515)                                                                                                                                             
    sizeof(dentry)=216 bytesst length (0x6) larger than NumEl]                                                                                                              
    sizeof(ext3inode)=872 bytes mmio: [0xb8b00000-0xb8b0ffff]ff]                                                                                                            
    sizeof(buffer_head)=104 bytes80 MHz counter                                                                                                                             
    sizeof(skbuff)=264 bytes                                                                                                                                                
    sizeof(task_struct)=2744 bytesdow [io  d entries: 65536 (order: 8, 1048576 bytes)                                                                                       
    devtmpfs: initializedigured (established 524288 bind 65536)                                                                                                             
    regulatorrning: Package List length (0x6) larger than NumElements count (f]                                                                                             
    pci 0000:04:00.0: supports D1 D21                                                                                                                                       
    pci 0000:04:00.0: disablin PCI Interrupt Link [LNKB] (IRQs 5 7 10 *11)                                                                                                  
    ACPI: PCI Interrupf]ot video device                                                                                                                                     
    pci 0000:08:00.0: BAR 6: no parent found for of device [0xff88 bind 65536)                                                                                              
    TCP reno registeredry: 15728k freed                                                                                                                                     
    NET: Registered protocol family 1t (disabled)                                                                                                                           
    pci 0000:00:1f.0: rerouting interrupts for [8086:2670]                                                                                                                  
    pci 0000:0c:0c.0: Boot video devicecooling_device1                                                                                                                      
    Trying to unpack rootfs image as initramfs...vice2                                                                                                                      
    Freeing initrd memory: 15728k freedcooling_device3                                                                                                                      
    audit: initializing netlink socket (disabled)vice4                                                                                                                      
    type=2000 audit(1ered as cooling_device0ng_device5                                                                                                                      
    processor LNXCPU:01: registered as cooling_device1                                                                                                                      
    processor LNXCPU:02: registered as cooling_device2                                                                                                                      
    processor LNXCPU:03: registered as cooling_device3                                                                                                                      
    processor LNXCPU:04: registered as cooling_device4ort is initialized.                                                                                                   
    processor LNXCPU:05: registered as cooling_device5_OSC.                                                                                                                 
    processor LNXCPU:06: registered as cooling_device6                                                                                                                      
    processor LNXCPU:07: registered as cooling_device7                                                                                                                      
    ERST: Could not register with persistent store                                                                                                                          
    ERST: Error Record Serialization Table (ERST) support is initialized.                                                                                                   
    GHES: APEI firmware first mode is enabled by WHEA _OSC.                                                                                                                 
    Non-volatile memory driver v1.3                                                                                                                                         
    Linux agpgart interface v0.103                                                                                                                                          
    crash memory driver: version 1.1hosen from 1 choice                                                                                                                     
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled                                                                                                                 
    �serial8250: ttyS0 at I/O 0x3f8 (irq = 0) is a 16550A                                                                                                                   
    brd: modub usb4: SerialNumber: 0000:00:1d.2(level, low) -> IRQ 22                                                                                                       
    usb usb4: configuration #1 chosen from 1 choice 64                                                                                                                      
    hub 4-0:1.0: USB hub foundI Host Controller                                                                                                                             
    hub 4-0:1.0: 2 ports detectediver hiddev                                                                                                                                
    uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 22 (level, low) -> IRQ 22                                                                                                       
    uhci_hcd 0000:00:1d.3: setting latency timer vernor ladder                                                                                                              
    cpuidle: using governor menu                                                                                                                                            
    usbcore: registered new interface driver hiddev                                                                                                                         
    usbcore: registered new interface driver usbhid                                                                                                                         
    usbhid: v2.6:USB HID core driver                                                                                                                                        
    TCP cubic registered                                                                                                                                                    
    Initializing XFRM netlink socketgister_driver+0x56/0xd0                                                                                                                 
    NET: Registered protocoDR7: 00000000000004000/0x43 [e1000e]                                                                                                             
    Process modprobe (pid: 221, veid: 0, thre1/0x4a0x43 [e1000e]                                                                                                            
     [<ffffffff812880f6>] ? __pci_register_driver+0x56/0xd0                                                                                                                 
     [<ffffffffa0041000>] ? e1000_init_module+0x0/0x43 [e1000e]                                                                                                             
     [<ffffffffa0041041>] ? e1000_init_module+0x41/0x43 [e1000e]                                                                                                            
     [<ffffffff8100204c>] ? do_one_initcall+0x3c/0x1d0                                                                                                                      
     [<ffffffff810bd89f>] ? sys_init_module+0xdf/0x260                                                                                                                      
     [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b
    IMS-e1000e-kernel-panic1.png

  13. #13
    Join Date
    May 2011
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I have a Chasis MFSYS25V2 with two MFS5520VI Compute Module. Each module have two Xeon CPU E5645 at 2.40GHz with 32GB of RAM (4x8GB) and with Dual Gigabit Ethernet I/O Expansion Mezzanine Card

    With the kernel 2.6.32-11 I have problems with flapping network.

    Details of network configuration:
    BOND Type: 802.3ad - Each card to a diferent switch
    bond0 -> eth0 and eth2
    bond1 -> eth1 and eth3

    bond0 have one private IP to access Proxmox VE Web.
    bond1 have various VLANs

    Each VLAN is in a vmbr bridge.

    The problem with the network is only in the bond1 interface that have VLAN configuration. bond0 always work.

  14. #14
    Join Date
    Aug 2006
    Posts
    9,742

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  15. #15
    Join Date
    May 2011
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Does not apply for me. I haven't 82574 network card. I have 82575.

    01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    05:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    05:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)

    I have the following line in all ethernet cards and in all compute module.

    0x0010 60 10 ff ff 6f 24 e8 34 86 80 a7 10 86 80 4b b7
    ^^

    I haven't "58" or "5a" at offset 0x001e.

  16. #16
    Join Date
    Nov 2011
    Posts
    22

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I can confirm this bug on 2.6.31-12.
    Downgrade to 2.6.31-11 solve the issue. Seems like the it won't propagage the vlan tagged traffic to the bond sub-inteface (bondx.y).
    It can be tested with tcp dump:

    tcpdump -i bond0 vlan X (show traffic)

    tcpdump -i bond0.X (don't show traffic)

    I've a Fujitsu-Siemens Blade Server populated with BX920 S2 with mezzanine cards (4+4 GbE).

    01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    02:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    02:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    10:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    10:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    20:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)
    20:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Backplane Connection (rev 02)

    Quote Originally Posted by j5boot View Post
    I have a Chasis MFSYS25V2 with two MFS5520VI Compute Module. Each module have two Xeon CPU E5645 at 2.40GHz with 32GB of RAM (4x8GB) and with Dual Gigabit Ethernet I/O Expansion Mezzanine Card

    With the kernel 2.6.32-11 I have problems with flapping network.

    Details of network configuration:
    BOND Type: 802.3ad - Each card to a diferent switch
    bond0 -> eth0 and eth2
    bond1 -> eth1 and eth3

    bond0 have one private IP to access Proxmox VE Web.
    bond1 have various VLANs

    Each VLAN is in a vmbr bridge.

    The problem with the network is only in the bond1 interface that have VLAN configuration. bond0 always work.
    Last edited by robynhub; 05-25-2012 at 10:42 AM.

  17. #17
    Join Date
    Dec 2011
    Posts
    8

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    No, does not apply for me. Stumpled at this patch at my Investigantion 4 weeks ago too. At my site is 82571EB

    05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01)
    05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01)
    08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
    08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)

  18. #18
    Join Date
    Sep 2011
    Location
    New Jersey
    Posts
    30

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Hello,
    I upgraded yesterday:

    pveversion -v
    pve-manager: 2.1-5 (pve-manager/2.1/0fa60f36)
    running kernel: 2.6.32-12-pve
    proxmox-ve-2.6.32: 2.1-68
    pve-kernel-2.6.32-12-pve: 2.6.32-68
    pve-kernel-2.6.32-7-pve: 2.6.32-60
    lvm2: 2.02.95-1pve2
    clvm: 2.02.95-1pve2
    corosync-pve: 1.4.3-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-2
    pve-cluster: 1.0-27
    qemu-server: 2.0-40
    pve-firmware: 1.0-16
    libpve-common-perl: 1.0-28
    libpve-access-control: 1.0-22
    libpve-storage-perl: 2.0-20
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve5
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.1-2
    ksm-control-daemon: 1.1-1

    And I began receiving kernel oops this morning (attached). Please advise. Thanks.
    Richard
    Attached Files Attached Files

  19. #19
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    11,785

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by rpuglisi View Post
    And I began receiving kernel oops this morning (attached). Please advise. Thanks.
    Richard
    Seems you run out of memory?
    Best regards,
    Dietmar

    Do you have already a Commercial Support Subscription? - If not, Buy now

  20. #20
    Join Date
    Aug 2006
    Posts
    9,742

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    pls report this issue to the driver maintainer, see http://sourceforge.net/p/e1000/bugs/
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  21. #21
    Join Date
    Dec 2011
    Posts
    8

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable


  22. #22
    Join Date
    Jun 2012
    Posts
    1

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by j5boot View Post
    I have a Chasis MFSYS25V2 with two MFS5520VI Compute Module. Each module have two Xeon CPU E5645 at 2.40GHz with 32GB of RAM (4x8GB) and with Dual Gigabit Ethernet I/O Expansion Mezzanine Card

    With the kernel 2.6.32-11 I have problems with flapping network.

    The problem with the network is only in the bond1 interface that have VLAN configuration. bond0 always work.
    Hi!

    Which controller? Anything like this?

    01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
    it's an issue within igb drivers in version 3.4.7. Downgrading to 3.3.6 resolves the problem.
    install (with dpkg -i filename) http://uploaded.to/file/673acyyl and update initrd (update-initramfs -k all -u)

    regards,
    patrick
    Last edited by netbuild; 06-19-2012 at 05:12 PM.

  23. #23
    Join Date
    Jun 2012
    Posts
    1

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I have 3x MFS5520VI Compute Module in IMS .
    Replacing the driver from version 3.4.7 to 3.3.6 igb.ko solves this problem.

    The problem exists only in the Linux kernel proxmox2-1 2.6.32-12-pve and IGB driver 3.4.7 and bridged vlans.

  24. #24
    Join Date
    Aug 2006
    Posts
    9,742

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    3.4.7 is the latest. pls report it to the driver developer - http://sourceforge.net/p/e1000/bugs/
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  25. #25
    Join Date
    Jun 2010
    Posts
    101

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Filled but so fare no response...

    http://sourceforge.net/p/e1000/bugs/344/

  26. #26
    Join Date
    May 2009
    Posts
    77

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I tried to upgrade but no luck:

    apt-get dist-upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

    Here is my version:

    pveversion -v
    pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
    running kernel: 2.6.32-11-pve
    proxmox-ve-2.6.32: 2.0-66
    pve-kernel-2.6.32-11-pve: 2.6.32-66
    lvm2: 2.02.95-1pve2
    clvm: 2.02.95-1pve2
    corosync-pve: 1.4.3-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-2
    pve-cluster: 1.0-26
    qemu-server: 2.0-39
    pve-firmware: 1.0-15
    libpve-common-perl: 1.0-27
    libpve-access-control: 1.0-21
    libpve-storage-perl: 2.0-18
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve5
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-9
    ksm-control-daemon: 1.1-1

  27. #27
    Join Date
    May 2009
    Posts
    77

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by webservio View Post
    I tried to upgrade but no luck:

    apt-get dist-upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

    Here is my version:

    pveversion -v
    pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
    running kernel: 2.6.32-11-pve
    proxmox-ve-2.6.32: 2.0-66
    pve-kernel-2.6.32-11-pve: 2.6.32-66
    lvm2: 2.02.95-1pve2
    clvm: 2.02.95-1pve2
    corosync-pve: 1.4.3-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-2
    pve-cluster: 1.0-26
    qemu-server: 2.0-39
    pve-firmware: 1.0-15
    libpve-common-perl: 1.0-27
    libpve-access-control: 1.0-21
    libpve-storage-perl: 2.0-18
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve5
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-9
    ksm-control-daemon: 1.1-1

    I managed to upgrade howver I am seeing two kernels (see below). How do I enable the latest Kernel?
    I am sorry in advance that it seems like a simple question but the wiki pages and how to 's do not explain clearly.

    pveversion -v
    pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
    running kernel: 2.6.32-12-pve
    proxmox-ve-2.6.32: 2.1-68
    pve-kernel-2.6.32-11-pve: 2.6.32-66
    pve-kernel-2.6.32-12-pve: 2.6.32-68
    lvm2: 2.02.95-1pve2
    clvm: 2.02.95-1pve2
    corosync-pve: 1.4.3-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-2
    pve-cluster: 1.0-26
    qemu-server: 2.0-39
    pve-firmware: 1.0-16
    libpve-common-perl: 1.0-27
    libpve-access-control: 1.0-21
    libpve-storage-perl: 2.0-18
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve5
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-9
    ksm-control-daemon: 1.1-1

  28. #28
    Join Date
    Sep 2010
    Posts
    38

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I've strange behaviour of Proxmox 2.1 kernel 2.6.32-12. I'm using this version of Proxmox since Thursday last week. I've got Kernel Panic, detailed message looks like: Kernel Panic! Kernel not support with 'relatime'. In dmesg and syslog there is no info about this event.

    pveversion -v:
    pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
    running kernel: 2.6.32-12-pve
    proxmox-ve-2.6.32: 2.1-68
    pve-kernel-2.6.32-11-pve: 2.6.32-66
    pve-kernel-2.6.32-12-pve: 2.6.32-68
    lvm2: 2.02.95-1pve2
    clvm: 2.02.95-1pve2
    corosync-pve: 1.4.3-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-2
    pve-cluster: 1.0-26
    qemu-server: 2.0-39
    pve-firmware: 1.0-16
    libpve-common-perl: 1.0-27
    libpve-access-control: 1.0-21
    libpve-storage-perl: 2.0-18
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve5
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-9
    ksm-control-daemon: 1.1-1


    On the server are working few OpenVZ containers a one KVM VM with linux Debian Squeeze.

  29. #29
    Join Date
    Mar 2010
    Location
    Stuttgart / Germany
    Posts
    342

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Same to me. Glad to hear Im not the only one. I had kernel panic on 2 prod servers. Should I try the 2.6.32-13-pve ?

  30. #30
    Join Date
    Sep 2010
    Location
    Austria
    Posts
    76

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    maybe the kernel panic was triggered by the leap second in the last days
    i've read some reports that linux had problems with that

  31. #31
    Join Date
    Mar 2010
    Location
    Stuttgart / Germany
    Posts
    342

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    thank you. that might be the cause.

  32. #32
    Join Date
    Dec 2009
    Posts
    62

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I am getting random freezes with pve-kernel-2.6.32-12-pve every couple of hours requiring a reboot. It's a 3 year old MSI MS-9232 1 RU server (e1000 nic Intel 82573L) which I use for testing. I reinstalled with pve-kernel-2.6.32-11-pve and it seems stable again. With the pve-kernel-2.6.32-12-pve kernel it will eventually lock up just sitting there doing nothing. When I do lsmod I don't see the igb.lo loaded.
    Last edited by Erk; 07-03-2012 at 01:06 AM.

  33. #33
    Join Date
    Nov 2011
    Posts
    10

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    I am also having problems with Intel NIC, in my case a Quad Port ET based on 82576.

    On POST link led is on and it remains on up until GRUB passes the stick to the kernel to boot. Immediately after the kernel starts to load the link goes off and I cannot get the NIC back (rmmod igb followed by modprobe igb do not help).

    No evidence of problems on dmesg. This issue has been reported on other platforms as well as with other Intel NICs here (description of the problem matches exactly what I am seeing):
    https://sourceforge.net/mailarchive/...sg_id=29316891

    I see a lot of users reporting problems with Intel NICs here. Maybe these issues are all related.

  34. #34
    Join Date
    Jan 2012
    Location
    Germany
    Posts
    6

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    A user reported that downgrading to the 3.3.6 release solved his problems. Maybe it works for you too. Have a look here, post #22

  35. #35
    Join Date
    Jul 2012
    Posts
    1

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Just want to say that proxmox rox my sox (first post).

    I had two Proxmox servers experience a kernel panic on Saturday as well. They were both older Dell 2950's and I originally thought it may be due to a needed bios update, but again only 2 out of 10 servers panicked. All of my servers are running the 2.6.32-12 kernel. These servers have been humming along perfectly for weeks on 2.1 until the leap second event...

    IMAG0064.jpg

  36. #36
    Join Date
    Nov 2011
    Posts
    10

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    3.3.6 did not work for me either. I am in touch with Intel, seems to be a known (although rare) problem.

    Quote Originally Posted by DirkZ View Post
    A user reported that downgrading to the 3.3.6 release solved his problems. Maybe it works for you too. Have a look here, post #22

  37. #37
    Join Date
    Jan 2012
    Posts
    4

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by j5boot View Post
    Hello

    Today I made ​​a fresh install of Proxmox 2.0 on a Intel Modular Server, and when I upgraded the kernel to version 2.6.32-12 the network has stopped working.

    I restarted with the 2.6.32-11 kernel and the network has become operational. I think it's a bug.

    Someone with an IMS could confirm this?
    Same here. Networking is working in principle, but not with tagged vlans under kernel 2.6.32-12. With version 2.6.32-11 everything works just fine on the IMS.

  38. #38
    Join Date
    Jul 2012
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Hi,

    I experience a similar effect of up to 72% package loss on a direct link between two proxmox nodes with kernel 2.6.32-12-pve after upgrading today (previous kernel was 2.6.32-11-pve). The two machines are directly linked via bonded (rr) 10 Gb ethernet cards, two Intel Corporation 82599EB 10 Gigabit TN Network Connection per machine. The cards use the ixgbe driver.

    After reading this thread I tried unloading the ixgbe module and force-loading the ixgbe.ko from kernel 2.6.32-11-pve on both machines and after ifup-ing the corresponding bond interfaces, there were no more package losses.

    This may be related to what was observed with the ixbge in this thread https://bugzilla.redhat.com/show_bug.cgi?id=696337 (for a RedHat based system).

    My question is: Will there be a new proxmox 2.6.32-xx-pve kernel package which fixes this issue by patching this driver, ie importing an upstream version or backporting it to what was used in 2.6.32-11-pve? I know that I can manually force it to load the older ixgbe.ko which is still on the system, but even symlinks to the old version of ixbge.ko from /lib/modules/2.6.32-12-pve/kernel/drivers/net/ixgbe to /lib/modules/2.6.32-11-pve/kernel/drivers/net/ixgbe won't help since the module won't be inserted unless forced by modprobe -f. Any advise on how to handle this in an automatic manner?

    Thanks for your help.

  39. #39
    Join Date
    Jul 2012
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Hi,

    just for the record: I solved the problem the following way:
    a) Get ixgbe-3.9.17.tar.gz from sourceforge and unpack it somewhere
    b) Obtain the patch named ixgbe_fix_mac_flush.patch from an attachment in the following thread:
    http://sourceforge.net/mailarchive/f...me=e1000-devel
    c) Compile and install the kernel module (follow instructions in the ixgbe-3.9.17/README file.
    Note: We need the appropriate kernel source package being installed, ie pve-headers-2.6.32-12-pve.
    Then the Intel 82599EB 10 Gb card with ixgbe as driver module works again as part of of bonding device without any package losses, even after rebooting the machines.

    Maybe it would be possible to introduce such a fix in the proxmox kernel package. I also tried the ixbge-3.10.16 driver, but it showed the same symptoms.
    (The patch for 3.9.17 mentioned above was posted later than the 3.10.16 driver's release date.)

    Thanks again.

    Quote Originally Posted by woawa21 View Post
    Hi,

    I experience a similar effect of up to 72% package loss on a direct link between two proxmox nodes with kernel 2.6.32-12-pve after upgrading today (previous kernel was 2.6.32-11-pve). The two machines are directly linked via bonded (rr) 10 Gb ethernet cards, two Intel Corporation 82599EB 10 Gigabit TN Network Connection per machine. The cards use the ixgbe driver.

    After reading this thread I tried unloading the ixgbe module and force-loading the ixgbe.ko from kernel 2.6.32-11-pve on both machines and after ifup-ing the corresponding bond interfaces, there were no more package losses.

    This may be related to what was observed with the ixbge in this thread https://bugzilla.redhat.com/show_bug.cgi?id=696337 (for a RedHat based system).

    My question is: Will there be a new proxmox 2.6.32-xx-pve kernel package which fixes this issue by patching this driver, ie importing an upstream version or backporting it to what was used in 2.6.32-11-pve? I know that I can manually force it to load the older ixgbe.ko which is still on the system, but even symlinks to the old version of ixbge.ko from /lib/modules/2.6.32-12-pve/kernel/drivers/net/ixgbe to /lib/modules/2.6.32-11-pve/kernel/drivers/net/ixgbe won't help since the module won't be inserted unless forced by modprobe -f. Any advise on how to handle this in an automatic manner?

    Thanks for your help.

  40. #40
    Join Date
    Mar 2010
    Location
    Stuttgart / Germany
    Posts
    342

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    How does it work with the 2.6.32-13 from pvetest ?

  41. #41
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    11,785

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Best regards,
    Dietmar

    Do you have already a Commercial Support Subscription? - If not, Buy now

  42. #42
    Join Date
    Jul 2012
    Posts
    3

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Thanks. I installed it on both nodes and there are no packet losses when I try to ping between the two nodes.
    I see that you use ixgbe version 3.10.16, presumably with a patch.
    Do you plan to release it in the stable branch soon?

    By the way, I see messages at boot time like
    Jul 19 09:43:10 monetbase dlm_controld[2431]: dlm_controld 1324544458 started
    Jul 19 09:43:11 monetbase kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
    Jul 19 09:43:11 monetbase kernel: dlm: Using TCP for communications
    Jul 19 09:43:11 monetbase kernel: dlm: rgmanager: group join failed -1 -1
    Jul 19 09:43:11 monetbase dlm_controld[2431]: dlm_join_lockspace no fence domain
    Jul 19 09:43:11 monetbase dlm_controld[2431]: process_uevent online@ error -1 er

    They also occur with kernel 2.6.32-12-pve. I suspect this is related to fencing which I haven't set up yet. The web interface runs fine and I can properly live-migrate my test client.

    Quote Originally Posted by dietmar View Post

  43. #43
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    11,785

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by woawa21 View Post
    Do you plan to release it in the stable branch soon?
    yes

    Quote Originally Posted by woawa21 View Post
    I suspect this is related to fencing which I haven't set up yet.
    yes
    Best regards,
    Dietmar

    Do you have already a Commercial Support Subscription? - If not, Buy now

  44. #44
    Join Date
    Dec 2011
    Posts
    8

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Kernel Crashes are gone with pve-kernel-2.6.32-14-pve 2.6.32-73. Thanks to the updated e1000e Driver.

    The Problems with flapping Network Link on IMS are still happening.
    http://forum.proxmox.com/threads/939...Link-with-Bond

  45. #45
    Join Date
    Dec 2009
    Posts
    62

    Default Re: New 2.6.32 Kernel for Proxmox VE 2.1 stable

    Quote Originally Posted by Erk View Post
    I am getting random freezes with pve-kernel-2.6.32-12-pve every couple of hours requiring a reboot. It's a 3 year old MSI MS-9232 1 RU server (e1000 nic Intel 82573L) which I use for testing. I reinstalled with pve-kernel-2.6.32-11-pve and it seems stable again. With the pve-kernel-2.6.32-12-pve kernel it will eventually lock up just sitting there doing nothing. When I do lsmod I don't see the igb.lo loaded.

    Finally found out what my problem was:

    http://serverfault.com/questions/193...ere-do-i-start

    Several adapters with the 82573 chipset display "TX unit hang" messages during normal operation with the e1000 driver. The issue appears both with TSO enabled and disabled, and is caused by a power management function that is enabled in the EEPROM. Early releases of the chipsets to vendors had the EEPROM bit that enabled the feature. After the issue was discovered newer adapters were released with the feature disabled in the EEPROM.
    The fix is at the bottom of the linked page, and what a difference it made!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •