Bug with cpuunits?

[twister988]

Hello together.

EDIT: First of all my PVEVERSION -V:

root@proxmox:~# pveversion -v
pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

In Proxmox 1.9 there was an ability to set the CPUUNITS in the WebUI.
Well, i didnt´t found it in 2.0, so i decided to set them via the config files.

Output of VZCPUCHECK before change:

root@proxmox:~# vzcpucheck
Current CPU utilization: 4000
Power of the node: 658424

So i editet "cpuunits: xxxxxx" in every KVM config file.

My Astaro Firewall got 100000, my two 2008 R2 Enterprise DC´s 200000 each, and my backup server (2008 R2 Std) 100000.
Edited config-file, saved.
Stop/Start each VM ...

Last Output VZCPUCHECK -V:

root@proxmox:~# vzcpucheck -v
VEID CPUUNITS
-------------------------
0 1000
104 1000
103 1000
102 1000
Current CPU utilization: 4000
Power of the node: 658424

The CPUUNITS are not applied?
And my VM 101 is marked as VM 0 ?

Is that a bug?
Or am i too stupid?

Kind regards
Ralph

 

[dietmar]

Please use the GUI, the setting is part of the 'Option' tab.

 

[twister988]

Hi dietmar and thanks for your reply...

I made a screenshot of my "options-tab", there is no chance to entry cpu-units...

What is wrong?

Regards, Ralph

 

[Sascha]

The CPU unit adjustment seems to appear in the option of CTs only... not in VMs...

 

[dietmar]

The CPU unit adjustment seems to appear in the option of CTs only... not in VMs...

Oh - please can you file a bug at bugzilla.proxmox.com?

 

[Sascha]

Oh - please can you file a bug at bugzilla.proxmox.com?

done.