Bug 833655

Summary: After suspending host, all VMs are pinned to CPU 0
Product: [Fedora] Fedora Reporter: Josh Adams <jadams1217>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: berrange, clalancette, dougsland, itamar, jforbes, jyang, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 05:51:45 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Josh Adams 2012-06-20 00:12:23 EDT
Description of problem:
Using virt-manager to create and manage VMs (qemu-kvm), it seems that once the host has been suspended all VMs are pinned to CPU 0 upon resume.  Obviously, this causes some serious performance issues.  I am not necessarily sure if libvirt is at fault here, but I have not been able to find much by searching for this problem.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Create a VM in virt-manager
2. Suspend the host computer
3. Resume the host computer
4. Click on the "Show virtual hardware details" (lightbulb) button
5. Click on Processor
6. Click on "Pinning"
Actual results:
VCPU    On CPU    Pinning
0       0           0
1       0           0

Expected results:
VCPU    On CPU    Pinning
0       (any cpu)   0,1,2,3
1       (any cpu)   0,1,2,3

Additional info:
I don't remember this always having happened in the past, but it has been happening atleast since Fedora 16.
Comment 1 Daniel Berrange 2012-06-20 05:51:45 EDT

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