Updates for Proxmox VE 2.2 - including QEMU 1.3

[martin]

We just moved a bunch of packages to our stable repository, including a lot of important bug fixes and code cleanups - and the stable QEMU 1.3.

Release Notes

- qemu-server 2.0-71

• show better error message if bridge does not exist
• QMPClient: support fdsets
• fix version parser for qemu 1.3
• add new cpu types: SandyBridge Haswell Opteron_G4 Opteron_G5
• remove rhel specific cpu types: cpu64-rhel6 cpu64-rhel5

- pve-qemu-kvm 1.3-7

• update to qemu 1.3 final (Note: KVM live migration between 1.2 and 1.3 are not supported)

- pve-manager 2.2-32

• add new cpu types: Haswell and Opteron_G5
• remove rhel specific cpu types: cpu64-rhel6 and cpu64-rhel5

- pve-kernel-2.6.32-17-pve 2.6.32-83

• update to vzkernel-2.6.32-042stab065.3.src.rpm

- pve-cluster 1.0-34

• implement sendfd to support qemu fdset functionality.
• fix ssh_merge_keys

- libpve-common-perl_1.0-40

• run_command: implement afterfork callback

-libiscsi1 1.7.0

• update to 1.7.0

ISO Download
http://www.proxmox.com/downloads/proxmox-ve/17-iso-images

Upgrade from any 2.x
Just run 'apt-get update && apt-get dist-upgrade'

Upgrade from 1.9 to 2.x
http://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0

__________________
Best regards,

Martin Maurer
Proxmox VE project leader

 

[bazzi]

Maybe good to say on every upgrade if you can live migrate with a VM/CT to a new version from a old version host. It looks like it isn't possible with VM.

 

[mmenaz]

I would love to have and test the new "hdsize" boot parameter, are you planning to release a new iso with it included?
(BTW, above "ISO download link" points to the release of 24.10.12, from your message seems that you instead meant an iso with those new features included, since you cite it in this announce)
Thanks a lot

 

[tom]

its clearly mentioned that KVM live migration is not possible between kvm 1.2 and 1.3. just read.

 

[tom]

we create ISO images only for major releases (2.0, 2.1, 2.2, 2.3 ...). or to fix major bugs, only in very rare cases.

(the download link to the ISO tells you that you always have to apt-get update && dist-upgrade your installation)

the next ISO image will be available as V 2.3, in Q1/2013.

 

[bazzi]

its clearly mentioned that KVM live migration is not possible between kvm 1.2 and 1.3. just read.

You are right! My excuses!

I am looking at a problem with the new version. VM greater then 8GB will not finish live migration. It will hang around:

[COLOR=#000000][FONT=tahoma]Dec 18 16:43:12 migration status: active (transferred 1887637973, remaining 1518489600), total 8598913024)[/FONT][/COLOR]

The VM will e unresponsive and is not running on the "new" node. Only possibility to get the VM running again is to cancel the migration AND unlock the VM trough qm.

old node:

root@timo:~# pveversion -vpve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-17-pve: 2.6.32-83
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.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-40
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-7
ksm-control-daemon: 1.1-1

new node:

pve-manager: 2.2-32 (pve-manager/2.2/3089a616)running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-17-pve: 2.6.32-83
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.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-40
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-7
ksm-control-daemon: 1.1-1

THIS IS INCORRECT:

Ok narrowed the problem: If the disk is LVM trough vertio then it hangs at the end. LVM trough IDE works without problem.

On our production VM's the change virtio to IDE doesn't work. It still hangs at the last point.

 

[rotanid]

Today, i tried to set up a new ProxmoxVE Node but can't complete the installation, because pve-cluster fails to get the local IP - last week i set up two nodes with exact the same configuration (like /etc/hosts and so on)
Is it possible that there is a problem with one of the updates that were pushed into stable today?

 

[mir]

off-line migration is not possible either!
Trying to migrate pvevm:117 to esx2...Temporary failure; try again

 

[tom]

you run HA? if yes, install the updated KVM and shutdown your VM. rgmanager will start it again and then you should be able to live-migrate.

 

[bazzi]

you run HA? if yes, install the updated KVM and shutdown your VM. rgmanager will start it again and then you should be able to live-migrate.

Yes, I already tried that. Also I have removed the HA flag and then it still isn't possible to live migrate. I run a HA with LVM on a Intel Modular Server with 3 nodes.

 

[mir]

Yes, I do use HA. But since I only have a 2-node cluster it seems impossible to migrate to the other node if that node has been upgraded to pve-17.

 

[macday]

Thank you for your hard work, Martin.

Is the issue with compiling DRBD 8.4 fixed now ?

Thx
macday

 

[tom]

AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

What guest OS? Post VMID.conf

 

[bazzi]

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

What guest OS? Post VMID.conf

I have opened a new thread so I don't hijack this thread. The VMID.conf and quest os is at:
http://forum.proxmox.com/threads/12239-Live-migartion-fails-in-KVM-1-3?p=66472

 

[mir]

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

kvm in this release is utterly broken!

FreeBSD 8.3 working flawlessly before now floods the console with "interrupt storm detected on "irg9:"; throttling interrupt source"
FreeBSD 9.0 working flawlessly before now is not able to boot anymore. See screen dump.



The boot sequence stops here and hangs forever.

Disabling ACPI support will enable boot until FreeBSD complains of missing features.

 

[Erk]

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

kvm in this release is utterly broken!

FreeBSD 8.3 working flawlessly before now floods the console with "interrupt storm detected on "irg9:"; throttling interrupt source"
FreeBSD 9.0 working flawlessly before now is not able to boot anymore. See screen dump.

View attachment 1234

The boot sequence stops here and hangs forever.

Disabling ACPI support will enable boot until FreeBSD complains of missing features.

I am having the same problem on FreeBSD 9.0 how can I roll back to QEMU1.2 where it was working?

- Ernie.

/EDIT mine did eventually boot, when I clicked on shutdown in the vnc console it continued the boot process from the point it froze in your screenshot, it had been sitting at that point for at least 10min before I clicked on shutdown.

 

[tom]

off-line migration is not possible either!
Trying to migrate pvevm:117 to esx2...Temporary failure; try again

what storage type do you use? and do you have already KVM live snapshots for this VM - qcow2 on NFS?
if yes, remove the snapshots and try again. if it works, create a new snapshot and try again.

if you got a "failed" VM HA status, disable the resource with:

clusvcadm -d pvevm:VMID -m NODENAME

now just enable the resource again by starting the VM via gui.

I do successful live-migration here, currently testing with NFS and also LVM (on IMS)

 

[bazzi]

Some VM will Live migrate, but if there under load or have a large sum of allocated RAM it will fail...

 

[peterx]

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

Same problem with Nas4free. Tried to reinstall, same problem. Tried to install Freenas 7 same problem. Erk's trick with shutdown worked but is to complicated for reliable use.

Peter

 

[preocupao]

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

The same problem after upgrading two servers:

Any ideas about the size of

root@nodo3:~# apt-get update && apt-get dist-upgrade
...
The following NEW packages will be installed:
pve-kernel-2.6.32-17-pve
The following packages will be upgraded:
libiscsi1 libpve-common-perl proxmox-ve-2.6.32 pve-cluster
pve-manager pve-qemu-kvm qemu-server
7 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.4 MB of archives.
After this operation, 1,491 kB of additional disk space will be used.
Do you want to continue [Y/n]?
...
unable to write '/etc/pve/priv/authorized_keys.tmp.706086' - File too large
dpkg: error processing pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 27
configured to not write apport reports
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
dpkg: error processing pve-manager (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
configured to not write apport reports
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
proxmox-ve-2.6.32 depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve-2.6.32 depends on qemu-server; however:
Package qemu-server is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
Errors were encountered while processing:
pve-cluster
qemu-server
pve-manager
proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)