Bug 1335977

Summary:	RFE: track windows socket vs cores CPU preference
Product:	[Community] Virtualization Tools	Reporter:	Cole Robinson <crobinso>
Component:	libosinfo	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, cfergeau, fidencio
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-29 00:12:08 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:

Description Cole Robinson 2016-05-13 17:04:12 UTC

Certain windows versions apparently have CPU topology restrictions WRT sockets vs cores. There's more info tracked here:

https://bugzilla.redhat.com/show_bug.cgi?id=969352

libosinfo should provide some metadata about that distinction, so apps can avoid setting up unsupported configs

Comment 2 Cole Robinson 2018-09-04 18:33:10 UTC

This is still relevant with windows 10 versions as well:

https://answers.microsoft.com/en-us/windows/forum/windows_10-win_upgrade/windows-10-versions-cpu-limits/905c24ad-ad54-4122-b730-b9e7519c823f?auth=1

Comment 3 Cole Robinson 2019-03-29 00:12:08 UTC

While this is still relevant, and technically something libosinfo should support, no one seems to actually complain in practice about it and it's never come up as an issue for a supported product. So I'm closing this issue until there's an important usecase to drive it.

Comment 4 Cole Robinson 2019-03-29 00:15:23 UTC

Now that I go look through the bug history there are actually some complaints about this so I've moved it to the upstream tracker: https://gitlab.com/libosinfo/libosinfo/issues/22