Bug 1198581

Summary:	Validate the required number of CPU for the VM before trying to start it
Product:	[Retired] oVirt	Reporter:	Simone Tiraboschi <stirabos>
Component:	ovirt-hosted-engine-setup	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.6	CC:	amureini, bugs, ecohen, gklein, istein, lsurette, rbalakri, sbonazzo, yeylon
Target Milestone:	---	Keywords:	TestCaseNeeded, Triaged
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	There was no explicit validation of the number of CPU the user was going to assign to the engine VM with the real HW capabilities and so, if the user entered a wrong value, it was going to fail starting the engine VM. Validating that value makes it more user friendly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 13:49:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1234915

Description Simone Tiraboschi 2015-03-04 12:39:43 UTC

Description of problem:
Currently there is no check about the required number of CPU core for the VM against real HW capabilities.


Version-Release number of selected component (if applicable):
3.5.1

How reproducible:
100%

Steps to Reproduce:
1. Set a number of core > than the physical available
2.
3.

Actual results:
The input is accepted but the VM refuses to start and we simply print
[ ERROR ] Failed to execute stage 'Closing up': The VM is not powering up: please check VDSM logs

Expected results:
It should validate the core number accepting only valid values and printing an hint on invalid value.

Additional info:

Comment 1 Nikolai Sednev 2015-06-01 10:46:33 UTC

I've got this from engine. when tried to run VM with 10virtual CPUs, 2 cores per virtual socket and 5 virtual sockets, on host with 1 physical socket with 1 threads per core and 2 cores:

Operation Canceled

Error while executing action: 

Test:
Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
The host hosted_engine_1 did not satisfy internal filter CPU because it does not have enough cores to run the VM.


Host's components:
libvirt-daemon-driver-interface-1.2.8-16.el7_1.3.x86_64
vdsm-4.17.0-822.git9b11a18.el7.noarch
sanlock-python-3.2.2-2.el7.x86_64
qemu-kvm-common-ev-2.1.2-23.el7_1.3.1.x86_64
libvirt-python-1.2.8-7.el7_1.1.x86_64
libvirt-daemon-kvm-1.2.8-16.el7_1.3.x86_64
ovirt-release-master-001-0.8.master.noarch
ovirt-engine-sdk-python-3.6.0.0-0.13.20150515.gitdd15fbf.el7.centos.noarch
libvirt-client-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-storage-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-network-1.2.8-16.el7_1.3.x86_64
sanlock-lib-3.2.2-2.el7.x86_64
qemu-kvm-ev-2.1.2-23.el7_1.3.1.x86_64
libvirt-daemon-1.2.8-16.el7_1.3.x86_64
libvirt-lock-sanlock-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-secret-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.3.x86_64
ovirt-hosted-engine-setup-1.3.0-0.0.master.20150518075146.gitdd9741f.el7.noarch
libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.3.x86_64
mom-0.4.4-0.0.master.20150515133332.git2d32797.el7.noarch
qemu-kvm-tools-ev-2.1.2-23.el7_1.3.1.x86_64
ovirt-host-deploy-1.4.0-0.0.master.20150505205623.giteabc23b.el7.noarch
libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.3.x86_64
ovirt-hosted-engine-ha-1.3.0-0.0.master.20150424113553.20150424113551.git7c14f4c.el7.noarch
sanlock-3.2.2-2.el7.x86_64


Engine's components:
ovirt-engine-cli-3.6.0.0-0.2.20150518.gite3609e3.el6.noarch
ovirt-engine-setup-base-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-host-deploy-java-1.4.0-0.0.master.20150515080139.giteabc23b.el6.noarch
ovirt-engine-userportal-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-sdk-python-3.6.0.0-0.13.20150515.gitdd15fbf.el6.noarch
ovirt-iso-uploader-3.6.0-0.0.master.20150410142241.git1a680f9.el6.noarch
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-tools-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-backend-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-release-master-001-0.8.master.noarch
ovirt-host-deploy-1.4.0-0.0.master.20150515080139.giteabc23b.el6.noarch
ovirt-image-uploader-3.6.0-0.0.master.20150128151752.git3f60704.el6.noarch
ovirt-engine-lib-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-jboss-as-7.1.1-1.el6.x86_64
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-restapi-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-dbscripts-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-guest-agent-1.0.10.2-1.el6.noarch

Comment 2 Sandro Bonazzola 2015-11-04 13:49:03 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.