Proxmox VE 1.8 released!

[martin]

We just released Proxmox VE 1.8 - including a lot of fixes and updates - a big thanks to all beta testers.

This release includes the latest KVM 0.14 with a lot of performance improvements (2.6.32 and 2.6.35 Kernel branch) and also the latest stable OpenVZ (see 2.6.18 Kernel branch).

Release notes:
Roadmap

How to get the latest version:
Downloads
__________________
Best regards,
Martin Maurer

 

[naturlight]

Hello i update with success
I read : http://www.linux-kvm.org/page/KVM_Features

• QMP - Qemu Monitor Protocol
• KSM - Kernel Samepage Merging
• Kvm Paravirtual Clock - A Paravirtual timesource for KVM
• CPU Hotplug support - Adding cpus on the fly
• PCI Hotplug support - Adding pci devices on the fly

I'm using kvm, so i could add CPU without stop and start now ?

 

[tom]

Hello i update with success
I read : http://www.linux-kvm.org/page/KVM_Features

• QMP - Qemu Monitor Protocol
• KSM - Kernel Samepage Merging
• Kvm Paravirtual Clock - A Paravirtual timesource for KVM
• CPU Hotplug support - Adding cpus on the fly
• PCI Hotplug support - Adding pci devices on the fly

I'm using kvm, so i could add CPU without stop and start now ?

No, I assume this will crash your host.

 

[z33k3r]

Is it possible to do a live upgrade from 1.7 to 1.8?

 

[tom]

what is a live upgrade?

see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.8

 

[z33k3r]

As in without reboot. But the linked doc shows a required reboot.

 

[p3x-749]

....the Realease.txt in the root of the proxmox-ve_1.8-5754-4.iso is still that of pve-v1.7 ?!?

 

[tom]

....the Realease.txt in the root of the proxmox-ve_1.8-5754-4.iso is still that of pve-v1.7 ?!?

yes - its just a bug. See the release notes from the wiki.

Sent from my GT-P1000 using Tapatalk

 

[spirit]

Hi,

i had upgraded my cluster proxmox 1.8, all is runing fine but i had only one problem:

my vnc console is empty for all my linux vms. (no problem with windows).

what are the modification between 1.7 and 1.8 for the vnc console ?

 

[stef1777]

Hi!

Just to be sure. Is the Kernel 2.6.32 shipped with release 1.8 include the patch to have NFS working with openvz?

 

[tom]

yes, there were modification but already in the 1.7 releases. (minor updates). but we do not see any issues here - any details how to reproduce your issue?

 

[tom]

we moved the kernel from pvetest, so I assume if the pvetest kernel works for you it will still work.

 

[spirit]

- i had the problem on all linux vm (debian lenny and debian squeeze , 32 or 64bit).

i was working fine with last stable 1.7 updates.

i'm using "fr" keyboard, i'had see some changes in changelog, but on "fr-ca" .
but i don' t have any display (black console), when the vm is booting or when it's running.

i'll try to search in the code.

 

[Vitaly]

After apt-get update + apt-get upgrade + reboot server stopped working

Booted via hetzner rescue system, seen such messages in log:

Apr  1 03:15:30 hz kernel: button: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: pcspkr: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: snd_page_alloc: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: wmi: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: button: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: i2c_core: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: soundcore: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: i2c_i801: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: snd: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: evdev: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: evdev: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: snd_timer: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: snd_pcm: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: snd_pcsp: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: pcspkr: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: Adding 10485752k swap on /dev/mapper/vg0-swap.  Priority:-1 extents:1 across:10485752k 
Apr  1 03:15:30 hz kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Apr  1 03:15:30 hz kernel: EXT3 FS on dm-0, internal journal
Apr  1 03:15:30 hz kernel: ext2: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: crc16: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: jbd2: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: ext4: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: crc16: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: jbd2: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: ext4: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: stp: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: bridge: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: stp: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: bridge: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: cpufreq_stats: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: cpufreq_powersave: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: cpufreq_conservative: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: cpufreq_userspace: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: speedstep_centrino: disagrees about version of symbol module_layout
Apr  1 03:15:30 hz kernel: acpi_cpufreq: disagrees about version of symbol module_layout
Apr  1 03:15:31 hz postfix/master[2208]: daemon started -- version 2.5.5, configuration /etc/postfix
Apr  1 03:15:31 hz kernel: x_tables: disagrees about version of symbol module_layout
Apr  1 03:15:31 hz kernel: ip_tables: disagrees about version of symbol module_layout
Apr  1 03:15:31 hz kernel: x_tables: disagrees about version of symbol module_layout
Apr  1 03:15:31 hz kernel: ipt_REJECT: disagrees about version of symbol module_layout

Any ideas how to fix from chrooted enviroment?

 

[mdubit]

Hi,

Same problem here.

It seems my NICS and Hard drive are not seen in the same order as before, which is problematic.

Had to reboot on a 2.6.32-3 kernel to have a working server.

M.

After apt-get update + apt-get upgrade + reboot server stopped working

Booted via hetzner rescue system, seen such messages in log:

Apr  1 03:15:30 hz kernel: button: disagrees about version of symbol module_layout

Any ideas how to fix from chrooted enviroment?

 

[dietmar]

It seems my NICS and Hard drive are not seen in the same order as before, which is problematic.

Why is that problematic (that is quite normal)?

 

[mdubit]

Why is that problematic (that is quite normal)?

Well, when sda2, on which is the /boot/ partition is now sdc2, that looks kind of aproblem to me when the os quits its ramdisk.

And with 3 NICs, two of which are 1Gb/s able and one only 100Mb/s, when eth0 becomes eth2, all the virtual machine lack a bit of bandwidth. If you see what I mean.

 

[Vitaly]

Sorry for wrong report. My problem was caused by degraded mirror.

 

[mdubit]

Sorry for wrong report. My problem was caused by degraded mirror.

Can you elaborate, please ?

 

[Vitaly]

I haven't noticed, that mirror degraded, So, new kernel installed on sdb only. But machine booted from sda with old kernel. Then detected mirror and tryed to load latest modules from sdb. That faled because of different versions. Just unpleasant coincidence