> I don't get it.
>
> I've now replaced
> maxcpus: 128 with vcpus: 128
>
> but this results in:
> maxcpus must be equal to or greater than smp
> on migration.
>
> Command is than:
> -smp 128,sockets=1,cores=2,maxcpus=2
Please can you post the whole VM config?
__
maxcpus is computed now from sockets * cores.
qemu team have done change in code, because for example
it was possible to do sockets=1, cores=2, maxcpus=4.
which is wrong.
sockets and cores define the cpu topology.
vcpus defined the number of enabled cores
previously, proxmox was doing
if
I don't get it.
I've now replaced
maxcpus: 128 with vcpus: 128
but this results in:
maxcpus must be equal to or greater than smp
on migration.
Command is than:
-smp 128,sockets=1,cores=2,maxcpus=2
Greets,
Stefan
Am 02.07.2015 um 15:32 schrieb Stefan Priebe - Profihost AG:
> qemu-server has a qm
qemu-server has a qmupdate script. It seems this one misses this change.
Stefan
Am 02.07.2015 um 15:27 schrieb Stefan Priebe - Profihost AG:
> Am 02.07.2015 um 14:32 schrieb Alexandre DERUMIER:
>> yes.
>>
>> cpu hotplug as changed.
>>
>>
>> Now, the maxcpus = cores * sockets
>>
>> and "vcpus:"
>>
Am 02.07.2015 um 14:32 schrieb Alexandre DERUMIER:
> yes.
>
> cpu hotplug as changed.
>
>
> Now, the maxcpus = cores * sockets
>
> and "vcpus:"
>
> define the hotplugged vcpus number
So i need to sed maxcpus: to vcpus: ?
Do i need todo this only for the current running machine or also for ol
applied, thanks!
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
yes.
cpu hotplug as changed.
Now, the maxcpus = cores * sockets
and "vcpus:"
define the hotplugged vcpus number
- Mail original -
De: "Stefan Priebe"
À: "pve-devel"
Envoyé: Jeudi 2 Juillet 2015 14:03:49
Objet: [pve-devel] unknown setting 'maxcpus'
Hi,
i've today upgrade to lat
Signed-off-by: Thomas Lamprecht
---
README.dev | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/README.dev b/README.dev
index 14d89e7..122004a 100644
--- a/README.dev
+++ b/README.dev
@@ -41,7 +41,8 @@ python-pyparsing libfilesys-df-perl libcrypt-ssleay-perl \
libfile-readba
Hi,
i've today upgrade to latest stable-3 git.
At nearly all commands i get this error:
vm 203 - unable to parse value of 'maxcpus' - unknown setting 'maxcpus'
vm 204 - unable to parse value of 'maxcpus' - unknown setting 'maxcpus'
vm 202 - unable to parse value of 'maxcpus' - unknown setting 'ma
> I have build hammer 0.94.2 for jessie here (with --with-jemalloc)
>
> http://odisoweb1.odiso.net/ceph-jessie/
Thanks (I still hope ceph people will release something ...)
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi
I have build hammer 0.94.2 for jessie here (with --with-jemalloc)
http://odisoweb1.odiso.net/ceph-jessie/
- Mail original -
De: "aderumier"
À: "Stefan Priebe"
Cc: "pve-devel"
Envoyé: Jeudi 2 Juillet 2015 09:12:31
Objet: Re: [pve-devel] ceph hammer officially release by redhat
>>2.)
>>2.) We can make jemalloc the default instead of tcmalloc
I'm going to build my cluster with jemalloc too,
too much problem with tcmalloc/ too difficult to tune
I'll hope that ceph team will push as default soon.
- Mail original -
De: "Stefan Priebe"
À: "aderumier"
Cc: "pve-devel"
E
12 matches
Mail list logo
