Bug 2094415

Summary:	When running Isolate Thread VM , the CPU that must be reserved for VDSM is taken
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	BLL.Virt	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5.1	CC:	ahadas, bugs, dfodor, michal.skrivanek
Target Milestone:	ovirt-4.5.1	Flags:	pm-rhel: ovirt-4.5?
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-23 05:54:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Polina 2022-06-07 14:25:30 UTC

Description of problem:
When running Isolate Thread VM , the CPU that must be reserved for VDSM is taken.
As result more than must be allowed virtual CPUs are running .

Version-Release number of selected component (if applicable):
When running Isolate Thread VM , the CPU that must be reserved for VDSM is taken.
As result more than must be allowed virtual CPUs are running .

How reproducible:100%


Steps to Reproduce:
1.Run on host of topology Thread(s) 2, Core(s) 8, Socket(s) 2 a VM with Isolated Threads policy and 15 vCPUs (15 vsockets: 1:1).
2.Run the second VM with dedicated policy 2 vCPUs (2 vsockets: 1:1).


Actual results: the second VM runs. 


Expected results: we expect that such VM could not be started since one CPU must be reserved for VDSM. the second VM only could have 1:1:1


Additional info:

Comment 1 Liran Rotenberg 2022-06-07 14:36:16 UTC

Well not exactly..
VDSM will still have its own CPU to run on, no dedicated/isolate-threads will run on it.
The problem is isolate-threads suppose to own the whole core, not have one CPU for it and the other for VDSM (while dedicated can do that).

Comment 2 Polina 2022-06-19 10:53:46 UTC

verified on ovirt-engine-4.5.1.2-0.11.el8ev.noarch according to described scenario

Comment 3 Sandro Bonazzola 2022-06-23 05:54:58 UTC

This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.