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

[makton]

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

just updated to the 2.6.32 kernel and all looks good. Also, it seems the memory ballooning is working now. going to test the hugepages, and see if I can get memory sharing to work now.

AMD Phenom 4x 2.3gig with 6GIGs of ram
250GIG HD (For my DC and FreeNas to run)
720GIG HD (SCSI target to FreeNas "yep the VM" and sent back as NFS for other VMs and netshare)

my DC is using all virtio driver for HD and NIC
FreeNas is scsi HD and rt8139 NIC

other VMs are a mix.

 

[makton]

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

Wanted to update. I have the ballooning and hugepages working, which solves a thread I started earlier, but the result was not what I expected. Instead of not letting the memory go in the main space, not the VM won't let it go in hugepages. I still end up with memory not returning to the host to assist with other VMs. Do we not have memory sharing?

I'l be trying KSM laster next week. but that isn't exactly what I'm after either as I work with mix linux and windows.

 

[dietmar]

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.

So the "NetXtreme II BCM5708 Gigabit" is not detected? Any hints in the kernel logs (dmesg)?

 

[chopeta]

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

So the "NetXtreme II BCM5708 Gigabit" is not detected? Any hints in the kernel logs (dmesg)?

The server is on production now. I will have to reboot the machine and select new kernel to be able to copy dmesg output (manually since network is not working)... I will try to do that during the weekend. Thanks!

 

[online24]

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

Hello my friends.

does 2.6.18 kernel works with cpulimit setting?

 

[dietmar]

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

Hello my friends.

does 2.6.18 kernel works with cpulimit setting?

AFAIK yes - but I had no time to test it.

 

[rugby]

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

I upgraded to 2.6.32 and after rebooting I cannot remove a KVM:


Dec 28 15:21:12 pvedaemon 28189 destroying VM 114 on node 0 (localhost)
Dec 28 15:21:12 pvedaemon 28189 VM 114 destroy failed -

 

[tom]

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

I upgraded to 2.6.32 and after rebooting I cannot remove a KVM:


Dec 28 15:21:12 pvedaemon 28189 destroying VM 114 on node 0 (localhost)
Dec 28 15:21:12 pvedaemon 28189 VM 114 destroy failed -

do you run the latest version, pls post the output of

pveversion -v

 

[rugby]

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

do you run the latest version, pls post the output of

pveversion -v

pm01:~# pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-10
pve-firmware: 1.0-2
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-1

 

[tom]

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

pm01:~# pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-10
pve-firmware: 1.0-2
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-1

Is your VM 114 really a KVM guest - or is it a container?

 

[rugby]

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

Is your VM 114 really a KVM guest - or is it a container?

Sorry, 114 is a container. This is weird, I had 3 KVM's I could not remove before I posted but they remove just fine now.

I still can't get rid of the OpenVZ container however. It was a test container and I don't need or want it anymore.

 

[tom]

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

Sorry, 114 is a container. This is weird, I had 3 KVM's I could not remove before I posted but they remove just fine now.

I still can't get rid of the OpenVZ container however. It was a test container and I don't need or want it anymore.

boot a openvz kernel again (2.6.18 or 2.6.24) and remove it. or remove manually (remove config files and the data).

 

[adis]

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

So the "NetXtreme II BCM5708 Gigabit" is not detected? Any hints in the kernel logs (dmesg)?

Dietmar, maybe this can help, initramfs output after installing 2.6.32 kernel

update-initramfs: Generating /boot/initrd.img-2.6.32-1-pve
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw for module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-09-5.0.0.j3.fw for module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-mips-09-5.0.0.j3.fw for module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-06-5.0.0.j3.fw for module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw for module bnx2

 

[rugby]

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

boot a openvz kernel again (2.6.18 or 2.6.24) and remove it. or remove manually (remove config files and the data).

Okay, I'll have to manually remove the the containers. Maybe in the 1.5 upgrade somewhere along the line this could be automated?

 

[dietmar]

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

Dietmar, maybe this can help, initramfs output after installing 2.6.32 kernel

Any hints in the kernel logs (dmesg)?

 

[adis]

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

To shorten output, I've filtered kernel log with 'grep eth'

This is an IBM x3650 M2 with integrated 'Broadcom NetXtreme II BCM5709' and additional, Dual port Intel(R) PRO/1000 NIC.

2.6.24 kernel

Dec 29 09:45:16 kvm5 kernel: eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem 92000000, IRQ 28, node addr 00:21:5e:dc:b3:3c
Dec 29 09:45:16 kvm5 kernel: eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem 94000000, IRQ 40, node addr 00:21:5e:dc:b3:3e
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.0: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:ab:b6:8e
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.0: eth2: Intel(R) PRO/1000 Network Connection
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.0: eth2: MAC: 1, PHY: 4, PBA No: d56146-003
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.1: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:ab:b6:8f
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.1: eth3: Intel(R) PRO/1000 Network Connection
Dec 29 09:45:16 kvm5 kernel: 0000:15:00.1: eth3: MAC: 1, PHY: 4, PBA No: d56146-003
Dec 29 09:45:16 kvm5 kernel: Driver 'sd' needs updating - please use bus_type methods
Dec 29 09:45:16 kvm5 kernel: Driver 'sr' needs updating - please use bus_type methods
Dec 29 09:45:16 kvm5 kernel: usb0: register 'cdc_ether' at usb-0000:00:1d.0-2, CDC Ethernet Device, 02:21:5e:df:33:3f
Dec 29 09:45:16 kvm5 kernel: usbcore: registered new interface driver cdc_ether
Dec 29 09:45:16 kvm5 kernel: device eth0 entered promiscuous mode
Dec 29 09:45:16 kvm5 kernel: audit(1262076308.556:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
Dec 29 09:45:16 kvm5 kernel: bnx2: eth0: using MSIX
Dec 29 09:45:16 kvm5 kernel: bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex
Dec 29 09:45:16 kvm5 kernel: vmbr0: port 1(eth0) entering learning state
Dec 29 09:45:16 kvm5 kernel: vmbr0: port 1(eth0) entering forwarding state
Dec 29 09:45:16 kvm5 kernel: device eth1 entered promiscuous mode
Dec 29 09:45:16 kvm5 kernel: audit(1262076310.997:3): dev=eth1 prom=256 old_prom=0 auid=4294967295
Dec 29 09:45:16 kvm5 kernel: bnx2: eth1: using MSIX
Dec 29 09:45:16 kvm5 kernel: device eth2 entered promiscuous mode
Dec 29 09:45:16 kvm5 kernel: audit(1262076313.212:4): dev=eth2 prom=256 old_prom=0 auid=4294967295
Dec 29 09:45:16 kvm5 kernel: bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
Dec 29 09:45:16 kvm5 kernel: vmbr1: port 1(eth1) entering learning state
Dec 29 09:45:16 kvm5 kernel: vmbr1: port 1(eth1) entering forwarding state
Dec 29 09:45:16 kvm5 kernel: e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dec 29 09:45:16 kvm5 kernel: vmbr2: port 1(eth2) entering learning state
Dec 29 09:45:16 kvm5 kernel: vmbr2: port 1(eth2) entering forwarding state
Dec 29 09:45:26 kvm5 kernel: eth2: no IPv6 routers present
Dec 29 09:45:27 kvm5 kernel: eth1: no IPv6 routers present
Dec 29 09:45:27 kvm5 kernel: eth0: no IPv6 routers present

2.6.32 kernel

Dec 29 09:33:37 kvm5 kernel: Driver 'rtc_cmos' needs updating - please use bus_type methods
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.0: eth0: (PCI Express:2.5GB/s:Width x4) 00:15:17:ab:b6:8e
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.0: eth0: Intel(R) PRO/1000 Network Connection
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.0: eth0: MAC: 0, PHY: 4, PBA No: d56146-003
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.1: eth1: (PCI Express:2.5GB/s:Width x4) 00:15:17:ab:b6:8f
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.1: eth1: Intel(R) PRO/1000 Network Connection
Dec 29 09:33:37 kvm5 kernel: 0000:15:00.1: eth1: MAC: 0, PHY: 4, PBA No: d56146-003
Dec 29 09:33:37 kvm5 kernel: udev: renamed network interface eth0 to eth2
Dec 29 09:33:37 kvm5 kernel: udev: renamed network interface eth1 to eth3
Dec 29 09:33:37 kvm5 kernel: usb0: register 'cdc_ether' at usb-0000:00:1d.0-2, CDC Ethernet Device, 02:21:5e:df:33:3f
Dec 29 09:33:37 kvm5 kernel: usbcore: registered new interface driver cdc_ether
Dec 29 09:33:37 kvm5 kernel: device eth2 entered promiscuous mode
Dec 29 09:33:37 kvm5 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
Dec 29 09:33:37 kvm5 kernel: e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dec 29 09:33:37 kvm5 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Dec 29 09:33:37 kvm5 kernel: vmbr2: port 1(eth2) entering forwarding state
Dec 29 09:33:47 kvm5 kernel: eth2: no IPv6 routers present

 

[chopeta]

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

Any hints in the kernel logs (dmesg)?

I think our friend adis is right...

Can you give me something more specific? What hints are you expecting?

I will try to put something here...

BTW: The server is a Dell PowerEdge 1950.

After boot into 2.6.32, there is a lot of msgs. on dmesg... to mention a few:

...
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
bnx2 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Fusion MPT base driver 3.04.12
...
usb ...
Dell DRAC5 ...
usbcore: ...
usbhid: ...
bnx2 0000:04:00.0: firmware: requesting bnx2/bnx2-mips-06-5.0.0.j3.fw
bnx2: Can't load firmware file "bnx2/bnx2-mips-06-5.0.0.j3.fw"
bnx2 0000:04:00:0 PCI INT A disabled
bnx2: probe of 0000:04:00:0 failed with error -2
bnx2 0000:08:00:0 PCI INT A -> GSI 16 (level, low) -> IRQ 16
usb 1-1.2: ....
...
USB Mass Storage support registered.
bnx2 0000:08:00.0: firmware: requesting bnx2/bnx2-mips-06-5.0.0.j3.fw
bnx2: Can't load firmware file "bnx2/bnx2-mips-06-5.0.0.j3.fw"
bnx2 0000:08:00:0 PCI INT A disabled
bnx2: probe of 0000:04:00:0 failed with error -2
...

Still no network...

Any idea now?

Thanks for your help.

Regards,
chopeta

 

[dietmar]

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

please can you send me the whole 'dmesg' output (to dietmar@proxmox.com). Also send me the output of

# lspci -n

 

[chopeta]

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

Roger that, capturing the outputs right now...

Mail sent

 

[tom]

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

Okay, I'll have to manually remove the the containers. Maybe in the 1.5 upgrade somewhere along the line this could be automated?

thanks for feedback. its no good idea to remove automatically containers, just think of people just want to try 2.6.32 and then go back.