Bug 709194

Summary:	Runtime pinning should display correctly when inputting default pinning value as 1-3 in virt-manager
Product:	Red Hat Enterprise Linux 6	Reporter:	Min Zhan <mzhan>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	dyuan, hjiang, llim, mshao, mzhan
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	No description necessary	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 16:14:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Min Zhan 2011-05-31 03:07:40 UTC

Description of problem:
For a running guest, input Default pinning value as 1-3, Click Apply, Then the pinning column of runtime pinning display list only display 1,2. 

Version-Release number of selected component (if applicable):
libvirt-0.9.1-1.el6.x86_64
virt-manager-0.8.6-4.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Launch virt-manager, for a running guest

2. Click Details page -> Processor -> Pinning, input Default pinning value as 1-3, Click Apply

3. Check the value of runtime pinning display list below, found the pinning column value only display as 1,2.
  
Actual results:
As above. Same as inputting Default pinning value as 2-3,0-1....  Seems for running time pinning, the last value is not included for format x-x.

Expected results:
The pinning column value should display as 1,2,3

Additional info:

1. For running guest, inputting Default pinning value as 1,2,3. Check the value of runtime pinning display list below, found the pinning column value display correctly as 1,2,3.

2. When input Default pinning value as 1-3 for shutdown guest, Click Apply. Check the value of runtime pinning display list below, found the pinning column value display correctly as 1,2,3.

Comment 1 Cole Robinson 2011-07-18 22:24:19 UTC

This was a virtinst bug, fixed upstream now:

http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=61da388c4c29dd9eee396dcd85a001d35b9bf133

Comment 2 Cole Robinson 2011-07-28 15:29:27 UTC

Fixed in virt-manager-0.9.0-2.el6

Comment 4 Huming Jiang 2011-08-05 05:48:10 UTC

Reproduce this bug with the following components:
virt-manager-0.8.6-4.el6.noarch
libvirt-0.8.7-18.el6.x86_64

Verified this bug with the following components:
libvirt-0.9.4-1.el6.x86_64
python-virtinst-0.600.0-2.el6.noarch
virt-manager-0.9.0-5.el6.x86_64
kernel-2.6.32-171.el6.x86_64

Steps:
1. Launch virt-manager, for a running guest

2. Click Details page -> Processor -> Pinning, input Default pinning value as
1-3, Click Apply

3. Check the value of runtime pinning display list below, found the pinning
column value only display as 1,2,3.

2. Click Details page -> Processor -> Pinning, input Default pinning value as
0-2, Click Apply

3. Check the value of runtime pinning display list below, found the pinning
column value only display as 0,1,2.

But the value of "Default pinning" is shown confused, so i file a new bug to track to it. 
Bug 728426 - The value of default pinning should be shown correctly according to the Runtime pinning values.

Comment 5 Cole Robinson 2011-11-07 16:40:15 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No description necessary

Comment 6 errata-xmlrpc 2011-12-06 16:14:18 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1642.html