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
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.
This is unlikely to be backported to f13, moving to f14.
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
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).
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
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.