Bug 456343 – virt-manager will not allow more than one vcpu per guest

Bug 456343 - virt-manager will not allow more than one vcpu per guest

Summary:	virt-manager will not allow more than one vcpu per guest

Status:	CLOSED DUPLICATE of bug 441653

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	virt-manager (Show other bugs)
Sub Component:
Version:	9
Hardware:	x86_64 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Daniel Berrange
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-07-22 19:54 EDT by Liam Dennehy
Modified:	2008-09-03 16:31 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-09-03 16:31:54 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Liam Dennehy 2008-07-22 19:54:53 EDT

Description of problem:
unable to assign more than on vcpu using the virt-manager gui

Version-Release number of selected component (if applicable):
virt-manager-0.5.4-4.fc9

How reproducible:
always

Steps to Reproduce:
1. On a multi-core system (I have three cores)
2. Step through the virt-manager new machine wizard
  
Actual results:
Any number greater than 1 entered in the VCPUs field produces the error:
"Number of vcpus must be in the range 1-1"

Expected results:
Either a warning that I am choosing too many vcpus for my physical hardware or
no comment at all

Additional info:
I've only tried this using qemu-kvm virtualisation, but I have no others installed.

Comment 1 Cole Robinson 2008-09-03 16:31:54 EDT

virt-manager actually gets this info from libvirt, and this is a well know libvirt issue. hopefully it will be resolved for f10 beta.

*** This bug has been marked as a duplicate of bug 441653 ***

Note You need to log in before you can comment on or make changes to this bug.