[pve-devel] unknown setting 'maxcpus'

[Dietmar Maurer]

cores*socket is the maximum, so vcpus needs to be smaller/equal.

> On July 3, 2015 at 10:04 PM Stefan Priebe <s.priebe at profihost.ag> 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 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 config was:
> bootdisk: scsi0
> cores: 8
> hotplug: 1
> ide2: none,media=cdrom
> localtime: 1
> maxcpus: 128
> memory: 32243
> name: cgroup-test
> net0: virtio=92:D3:F8:26:96:A5,bridge=vmbr0
> onboot: 1
> ostype: l26
> scsi0: 
> cephstor1:vm-103-disk-1,iops_rd=2150,iops_wr=1550,mbps_rd=1300,mbps_wr=900,size=40G
> scsihw: virtio-scsi-pci
> smbios1: uuid=a5dd3482-4a3a-4280-9150-7429b686f4b4
> 
> Stefan
>