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):
virt-manager-0.9.1-4.fc17
libvirt-0.9.11.3-1.fc17
qemu-kvm-1.0-17.fc17

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.