Re: [pve-devel] unknown setting 'maxcpus'

2015-07-03 Thread Dietmar Maurer
cores*socket is the maximum, so vcpus needs to be smaller/equal. > On July 3, 2015 at 10:04 PM Stefan Priebe wrote: > > > Am 02.07.2015 um 16:01 schrieb Dietmar Maurer: > >> I don't get it. > >> > >> I've now replaced > >> maxcpus: 128 with vcpus: 128 > >> > >> but this results in: > >> maxcpus

Re: [pve-devel] unknown setting 'maxcpus'

2015-07-03 Thread Stefan Priebe
Am 02.07.2015 um 16:01 schrieb Dietmar Maurer: 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? Old c

[pve-devel] [PATCH 1/2] add missing dh-autoreconf buildtime dependency

2015-07-03 Thread Wolfgang Bumiller
--- debian/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/control b/debian/control index 1216f56..585efd4 100644 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: lxc Section: admin Priority: optional Maintainer: Proxmox Support Team -Build-D

[pve-devel] [PATCH 2/2] Add patch to use /dev/loop-control

2015-07-03 Thread Wolfgang Bumiller
LXC iterates through the /dev directory trying to attach to existing loop devices, meaning it only uses nodes that already exist. This patch makes it /dev/loop-control to find and allocate new ones on the fly. Fixes #651 --- .../0001-Use-dev-loop-control-if-it-exists.patch | 59