Re: [libvirt] [PATCH] qemu: Check for maximum vcpus exceeding cpu topology

2017-02-20 Thread Peter Krempa
On Mon, Feb 20, 2017 at 17:54:48 +0530, Madhu Pavan wrote: > > > On 02/07/2017 06:41 PM, Peter Krempa wrote: > > On Tue, Feb 07, 2017 at 07:56:29 -0500, Kothapally Madhu Pavan wrote: > > > This patch will prevent guest to start when the maximum > > > vcpus are greater than cpu topology limit.

Re: [libvirt] [PATCH] qemu: Check for maximum vcpus exceeding cpu topology

2017-02-20 Thread Madhu Pavan
On 02/07/2017 06:41 PM, Peter Krempa wrote: On Tue, Feb 07, 2017 at 07:56:29 -0500, Kothapally Madhu Pavan wrote: This patch will prevent guest to start when the maximum vcpus are greater than cpu topology limit. Currently similar checks do exist only during setvcpus. The patch adds the

Re: [libvirt] [PATCH] qemu: Check for maximum vcpus exceeding cpu topology

2017-02-07 Thread Daniel P. Berrange
On Tue, Feb 07, 2017 at 07:56:29AM -0500, Kothapally Madhu Pavan wrote: > This patch will prevent guest to start when the maximum > vcpus are greater than cpu topology limit. Currently similar > checks do exist only during setvcpus. The patch adds the > missing check. The c9cb35c255222 reverted

Re: [libvirt] [PATCH] qemu: Check for maximum vcpus exceeding cpu topology

2017-02-07 Thread Peter Krempa
On Tue, Feb 07, 2017 at 07:56:29 -0500, Kothapally Madhu Pavan wrote: > This patch will prevent guest to start when the maximum > vcpus are greater than cpu topology limit. Currently similar > checks do exist only during setvcpus. The patch adds the > missing check. The c9cb35c255222 reverted

[libvirt] [PATCH] qemu: Check for maximum vcpus exceeding cpu topology

2017-02-07 Thread Kothapally Madhu Pavan
This patch will prevent guest to start when the maximum vcpus are greater than cpu topology limit. Currently similar checks do exist only during setvcpus. The patch adds the missing check. The c9cb35c255222 reverted similar check to avoid older configs from vanishing. The current patch adds it in