Proxmox VE 2.1 released!

hoppel118

Member
Apr 5, 2012
55
1
8
Hey guys,

great work, I love proxmox! ;)

But I don't really know which version I have. There are shown two different versions:


  • on the right side from the proxmox logo of the webui --> version 2.0-54/4b59ea39
  • node pve manager version --> 2.1-1/f9b0f63a

Are the webui and the pve manager two different developed parts of proxmox?

ragards
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,686
434
83
reload your browser.

to get a full info about your version, run 'pveversion -v' on the commandline.
 

valshare

Member
Jun 2, 2009
252
2
18
Germany
Hi Proxmox Staff,

is there a chance to get an 2.6.18 Kernel for the 2.1 Proxmox release? Why?! Because i have an older VM Machine, that use a Sentinel SuperPro Dongle. The Software, that needs the dongle, didn´t find the dongle and works only with the 2.6.18 kernel but not with newer kernels. The dongle isn´t the problem. For the software there isn´t an update :(

Regards, Valle
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,686
434
83
no, there is no 2.6.18 for 2.x series. try to find the reason why it does not work on 2.1
 

valshare

Member
Jun 2, 2009
252
2
18
Germany
Hi Tom,

thanx for the answer. I have tried a lot to finde the reason. The problem must in the kernel over 2.6.18. The software for the dongle isn´t compatible with kernel over 2.6.18. I have tried different cpu mode, os modes, software compatiblity mode. Do you have any hint, that i can try, that the software works?

Thanx for help,

Valle
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,686
434
83
as I do not know your software and dongle, no. but in any case, pls open a new thread for this.
 

MeneM

New Member
Dec 21, 2008
16
0
1
I don't come here often. Which is because your software simply ROCKS! I must thank you so much for making my life so much more simple! (IT-wise)
 

Don Daniello

Member
Jan 28, 2012
46
3
8
Hi,
I'd like to ask if there are plans to implement ALL functionality of command-line vzctl tool into the PVE API?
There are many things that are missing in the web interface and the API (obviously), like vzctl exec, setting noatime, changing userpassword, changing I/O priority or adjusting UBC.
I know I can start hacking in the GIT repository and do it myself, but I prefer to stick to the official and stable versions of Proxmox and I believe these features will be much appreciated by many users.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,686
434
83
the plan is implement all feature without any bugs.

but we live in world with limited resources and if you need something special you can either try to implement it by your own or convince others to do it. most times developers works for cash.

or did I still not understand your question?
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,503
320
83
Austria
www.proxmox.com
I'd like to ask if there are plans to implement ALL functionality of command-line vzctl tool into the PVE API?
No, we do not really want ALL.

There are many things that are missing in the web interface and the API (obviously), like vzctl exec,
yes, there is already a patch for that in the bug tracker.

setting noatime, changing userpassword, changing I/O priority or
yes

adjusting UBC.
No, I only want to control vswap settings.
 

ericmachine

New Member
Aug 16, 2012
15
0
1
hi everyone,

like to check. currently i am using proxmox 1.9 and it works fine. however, i like to know whether the v2.1 is stable for production to install on my new server?

any help? thanks.
 

cirroz

Member
Nov 13, 2010
58
0
6
It works since v2.0 well.
7 containers and more than 10 HVMs over iSCSI.
Everything works fine.
 

valshare

Member
Jun 2, 2009
252
2
18
Germany
same here. Running Proxmox 2.1 on an Dell PowerEdge R800 with 10 Openvz and 5 KVM machines on an iscsi storage. Very stable.
 

chewbaccus

New Member
Jan 24, 2012
16
0
1
I have a problem after update to 2.1

The new kernel is set in the grub.cfg but the boot menu shows me only the older kernels.
Even older kernels which i have uninstall.
update-grub didn't helped.
I can't boot the new kernel !!
Here is my grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-14-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-14-pve ...'
linux /boot/vmlinuz-2.6.32-14-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-14-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-14-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-14-pve ...'
linux /boot/vmlinuz-2.6.32-14-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-14-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-12-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-12-pve ...'
linux /boot/vmlinuz-2.6.32-12-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-12-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-12-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-12-pve ...'
linux /boot/vmlinuz-2.6.32-12-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-12-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-10-pve' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-10-pve ...'
linux /boot/vmlinuz-2.6.32-10-pve root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-10-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-10-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-10-pve ...'
linux /boot/vmlinuz-2.6.32-10-pve root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-10-pve
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/pve-root ro quiet irqpoll
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(pve-root)'
search --no-floppy --fs-uuid --set 99d0da87-77f9-4eea-afe0-76a767bf0b29
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/pve-root ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1
 

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!