Bug 630776

Summary:	RFE: Allow specifying CPU socket/core/thread description
Product:	[Fedora] Fedora	Reporter:	Richard Henderson <rth>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	virt-manager-0.8.7-2.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-16 20:53:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard Henderson 2010-09-06 22:35:27 UTC

Description of problem:
The current "Processor" tab currently only allows "CPUs" to be configured,
and maps those directly to sockets.  I.e. CPUs == 2 yields

  -smp 2,sockets=2,cores=1,threads=1

on the qemu command-line.

This is unfortunate for many guest operating systems.

For instance, Windows 7 basic is software-limited to 1 socket; Windows 7
professional is limited to 2 sockets.  For more than 2 sockets Microsoft
requires that you install their server edition.

Simiarly, Red Hat Enterprise Linux Desktop 5 is limited to 1 socket.

However, each of the aforementioned will use as many cores and threads
indicated within the socket limitation.


Version-Release number of selected component (if applicable):
virt-manager-0.8.5-1.fc13.noarch
libvirt-0.8.2-1.fc13.x86_64

Comment 1 Cole Robinson 2010-12-17 16:14:30 UTC

This is configurable upstream now:

http://hg.fedorahosted.org/hg/virt-manager/rev/2da86617fb68

In the future we will probably try and use OS knowledge to set a working topology out of the box, but that's not implemented at the moment.

Comment 2 Cole Robinson 2011-03-29 21:07:31 UTC

This is unlikely to be backported to f13, moving to f14.

Comment 3 Fedora Update System 2011-03-31 17:12:47 UTC

virt-manager-0.8.7-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/virt-manager-0.8.7-1.fc14

Comment 4 Fedora Update System 2011-04-01 18:28:40 UTC

Package virt-manager-0.8.7-1.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-0.8.7-1.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/virt-manager-0.8.7-1.fc14
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-04-07 14:30:20 UTC

virt-manager-0.8.7-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/virt-manager-0.8.7-2.fc14

Comment 6 Fedora Update System 2011-04-16 20:53:10 UTC

virt-manager-0.8.7-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.