OpenVZ live migration, qemu-kvm-1.0, new kernel and a lot of bugfixes!

[martin]

Hi all!

We just released a bunch of updates for our Proxmox VE 2.0 beta. Just run "aptitude update && aptitude full-upgrade" to update from a previous beta.

Make sure you re-load the management GUI to eliminate issues with the browser cache. E.g. If you run Firefox, hold the shift-key and reload the page.

New Features

- OpenVZ live migration
- Qemu-kvm-1.0
- New Kernel, based on vzkernel-2.6.32-042stab044.5.src.rpm
- Countless small bug fixes

Get involved (incl. links to the public Git repository and Bugzilla bug tracker):
http://www.proxmox.com/products/proxmox-ve/get-involved

Happy testing, waiting for feedback!
__________________
Best regards,

Martin Maurer
Proxmox VE project leader

 

[t.bloo]

trying to install from scratch but don't get far...

# aptitude install proxmox-ve-2.6.32
...
Unpacking vzctl (from .../vzctl_3.0.29-3pve6_amd64.deb) ...
unable to backup existing configuration
dpkg: error processing /var/cache/apt/archives/vzctl_3.0.29-3pve6_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
configured to not write apport reports
Selecting previously deselected package proxmox-ve-2.6.32.
Unpacking proxmox-ve-2.6.32 (from .../proxmox-ve-2.6.32_2.0-54_all.deb) ...
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/vzctl_3.0.29-3pve6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
...

etcetera

 

[willy1009]

i get the same errors with aptitude full-upgrade.

 

[dietmar]

There seems to be a stale vzctl backup from a previous installation. Please try to remove that with:

# mv /etc/vz/conf.org /root/old-vz-conf.org

Then try again.

I assume there are no old containers on that system? If so you can safely remove /root/old-vz-conf.org

 

[willy1009]

i confirm it works

 

[t.bloo]

after a new, fresh install of debian squeeze, the errors change to:

...
Setting up pve-cluster (1.0-12) ...
Starting pve cluster filesystem : pve-cluster (warning).
invoke-rc.d: initscript pve-cluster, action "start" failed.
dpkg: error processing pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 255
Setting up apache2.2-common (2.2.16-6+squeeze4) ...
...



any ideas?

 

[dietmar]

any ideas?

Maybe hostname issues. Check if the name used in /etc/hostname has an entry in /etc/hosts?

 

[t.bloo]

thanks! something was indeed wrong in the /etc/hosts file

new beta is working now