Proxmox VE 0.9beta2 released!

Status
Not open for further replies.

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
651
393
83
We are announcing the release of Proxmox VE 0.9beta2.

Release notes

  • Improved web interface
  • New templates availabe. Fixed firefox template upload bug.
  • OpenVZ kernel updates
  • Update to KVM-71
  • New qemu-server, now supports most KVM features
  • New network model with up to 10 bridges
  • Bonding and VLAN support
  • Installer: show hard drive labels and size, added 'swapsize' and 'maxroot' boot parameters.
  • Vzctl update: support new bridged network model
  • Many bug fixes
Download

HowTo upgrade a running Proxmox VE 0.9

  1. Stop all running VM´s
  2. Review and correct /etc/apt/sources.list, should look like this:
    Code:
    deb ftp://ftp.debian.org/debian etch main
    # PVE packages provided by proxmox.com
    deb ftp://pve.proxmox.com/debian etch pve
    # security updates
    deb http://security.debian.org/ etch/updates main
  3. Update your apt repository:
    Code:
    apt-get update
  4. Download and install the new packages:
    Code:
    apt-get dist-upgrade
  5. Reboot
    Code:
    reboot
  6. Review the settings of all your VM´s
HowTo upgrade a running Proxmox VE 0.9 Cluster

  1. If the described update process above updates SSH keys, the Cluster cannot sync anymore.
  2. Remove the cluster config on the master and all nodes:
    Code:
    rm /etc/pve/cluster.cfg
  3. On the master, recreate the cluster:
    Code:
    pveca -c
  4. On the nodes, remove the known-hosts file:
    Code:
    rm /root/.ssh/known-hosts
  5. Join the nodes to the master:
    Code:
    pveca -a -h master-IP

Best Regards,

Martin Maurer

Proxmox Server Solutions GmbH
www.proxmox.com
 
Last edited by a moderator:

r.fluttaz

New Member
Apr 18, 2008
9
0
1
Just for information, if you're on an ovh server ... don't upgrade !!
All my vm doesn't start ! :(
 

kro

New Member
Apr 30, 2008
21
0
1
Just for information, if you're on an ovh server ... don't upgrade !!
All my vm doesn't start ! :(
That is, don't upgrade the kernel. You should still be able to upgrade pve-manager, but I'm testing it by myself.

Best Regards,
Felix Krohn
 

diaolin

Member
Jul 7, 2008
220
0
16
Trentino Italy
Fantastic, just upgraded but it does not resolve the vlan dependencies
Installed vlan through testing (debian testing i mean) and the pve-manager istallation
is ok.

Consideration:
1) smp rotext instead of number (tested with number into the code and it works correctly)
Why "rotext"????
2) beautiful disk management with the scsi and virtio...
3) networking is a charme, multiple bridges and a vlan foreach bridge.
4) if possible adding even the smb server as shared disk would be very interesting (for me)
5) the mac adresses given to the interfaces are not in the range of the assigned IANA's
addresses for the qemu interfaces.... Or may be i'm confusing something...
6) the interface is very very usable
7) thanks for the install parameters

In september i'll make a course with 20 persons and i will use 20 machines with 2 4core
processors with VT enabled for simulating a real environment....

Using Proxmox of course

Big work, thanks
Diaolin
 

zccopwrx

New Member
Jul 18, 2008
17
0
1
So, which release can we expect the VZ live migration to function? I noticed its completely disabled now.
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
1) smp rotext instead of number (tested with number into the code and it works correctly)
Why "rotext"????
its unstable with kvm, and unsupported by openvz 2.6.24
5) the mac adresses given to the interfaces are not in the range of the assigned IANA's
Those are local macs.

In september i'll make a course with 20 persons and i will use 20 machines with 2 4core
processors with VT enabled for simulating a real environment....

Using Proxmox of course
great :)
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
So, which release can we expect the VZ live migration to function? I noticed its completely disabled now.
We decided to disable it becaues it is still not 100% stable.

We will enable it again wen the openvz kernel is more stable.

- Dietmar
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
You can alway use the command line to set the -smp option:

Code:
qm set VMID --smp 2
Its only disabled on the web interface.

- Dietmar
 

diaolin

Member
Jul 7, 2008
220
0
16
Trentino Italy
Why?????

You can alway use the command line to set the -smp option:

Code:
qm set VMID --smp 2
Its only disabled on the web interface.

- Dietmar
I just put
smp: 2
into qemu-server/WMID.conf
and it works.

Why not permit to change the CPUs if creating/modifying a KVM-machine?

I think that when we have a good interface available... usign the
interface should not be only an option.
ProxMox is a good interface.

And then... command line BLEAH!

I use always command line, and when i say always is even for driving a car
but in this case...

I don't find the difference, via cmd line or in the config i can use smp
but from interface is not possible due to ...

Anyway tx,

Diaolin
 

diaolin

Member
Jul 7, 2008
220
0
16
Trentino Italy
Ok, it's unstable but the parameter exists and you cannot
remove parameters every day it becomes unstable or???

I think that the interface should do it's work: interface.

For avoiding convulsion (confusion) i think it's better to set
an
Unsupported section
with the "unstable parameters"

the use of this parameters will be only choosed by administrators
that knows what they are doing.

But, i repeat, the interface i s the interface and not the "parameter"
blocker.

The good administrator can choose whenever use it or not.

But probably my vision is too much different.

In any case, ok.
With or without smp parameter Proxmox is a great product.

Any news for the language file????

Diaolin
 

snesreviews

New Member
Jul 7, 2008
26
0
1
Though now I am getting problems adding a new VM :(

/usr/bin/pvectl qmcreate 107 --mem 512 --disk 32 --onboot yes --name bslert1064-01 --cdrom cdrom --network model=rtl8139,tap --disktype ide --ostype l26
Unknown option: disk
Unknown option: network
Unknown option: disktype
unable to apply VM settings -


Yet:

proxmox:/etc# pvectl --help
pvectl <command> <vmid> [parameters]
pvectl [vzcreate|vzset] <vmid> (openvz commands)
--ostemplate NAME specify OS template
--mem MBYTES memory in MB (64 - 8192)
--disk GBYTE disk space in GB (0.5 - 1024)
--cpus N cpus (1 - 4)
--cpuunits N cpu units (8 - 500000)
--onboot [yes|no] start at boot
pvectl [qmcreate|qmset] <vmid> (qemu-server commands)
--media NAME installation media
--mem MBYTES memory in MB (64 - 8192)
--disk GBYTE disk space in GB (0.5 - 1024)
--cpuunits N cpu units (8 - 500000)
--onboot [yes|no] start at boot
--ostype NAME specify OS type
pvectl print <vmid>
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
If i extract all the labels should i put the translation
into a .po file and then recompile it with with the locales
commands? Like msgfmt???
Basically yes. I have the complete framework here, but currently no time to include it. I will release it as soon as the web interface is more stable (before 1.0).

- Dietmar
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,910
462
103
Though now I am getting problems adding a new VM :(

/usr/bin/pvectl qmcreate 107 --mem 512 --disk 32 --onboot yes --name bslert1064-01 --cdrom cdrom --network model=rtl8139,tap --disktype ide --ostype l26
Unknown option: disk
Unknown option: network
Unknown option: disktype
unable to apply VM settings -


Yet:

proxmox:/etc# pvectl --help
pvectl <command> <vmid> [parameters]
pvectl [vzcreate|vzset] <vmid> (openvz commands)
--ostemplate NAME specify OS template
--mem MBYTES memory in MB (64 - 8192)
--disk GBYTE disk space in GB (0.5 - 1024)
--cpus N cpus (1 - 4)
--cpuunits N cpu units (8 - 500000)
--onboot [yes|no] start at boot
pvectl [qmcreate|qmset] <vmid> (qemu-server commands)
--media NAME installation media
--mem MBYTES memory in MB (64 - 8192)
--disk GBYTE disk space in GB (0.5 - 1024)
--cpuunits N cpu units (8 - 500000)
--onboot [yes|no] start at boot
--ostype NAME specify OS type
pvectl print <vmid>
we changed a lot in KVM.
see

Code:
man qemu-server
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
/usr/bin/pvectl qmcreate 107 --mem 512 --disk 32 --onboot yes --name bslert1064-01 --cdrom cdrom --network model=rtl8139,tap --disktype ide --ostype l26
That command uses old syntax, that is no longer supported.

use the qm command instead.

qm create 107 --mem 512 --ide0 32 --onboot yes --name bslert1064-01 --cdrom cdrom --vlan0=rtl8139 --ostype l26
see the manual page for the new options:

# man qemu-server
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,529
328
103
Austria
www.proxmox.com
Also, you seem to have an old version of pvectl.

# dpkg -l pve-manager

should show "pve-manager 0.9-4"

What version do you use?

- Dietmar
 
Status
Not open for further replies.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!