Currently, the virt-manager 'Create a new virtual machine' dialog offers the Version choice of 'Suse Linux Enterprise Server'. When this is used to create a SLES11 machine, virtio devices are not used by default for said SLES11 guest. However, SLES11 supports virtio devices just fine. So far, when I've installed SLES11 guests with this dialog, I've answered "Fedora 11" for Version so that virtio is enabled for the SLES11 guest I create. This is a bit non-intuitive. In my very basic performance tests, SLES11 and Fedora11 guests perform similarly in terms of virtio for a Fedora11 guest. My basic test is an IO intensive test and entails simply a timed kernel+module build of the linux tree. Test host machine is Fedora11 (upgraded to current from preview). Relevant pkg versions: qemu-kvm-0.10.4-4.fc11.x86_64 virt-manager-0.7.0-5.fc11.x86_64 libvirt-0.6.2-11.fc11.x86_64
Moving to python-virtinst component, since that's where the OS configuration data tables are stored.
python-virtinst is at this level on the test machine: python-virtinst-0.400.3-8.fc11.noarch Thanks; sorry I got the component wrong.
Fixed upstream: http://hg.et.redhat.com/cgi-bin/hg-virt.cgi/applications/virtinst--devel/rev/dbda3bfc28f8 Moving to POST
Resolved for F-12 by python-virtinst-0.500.0-1.fc12; perhaps worth backporting to F-11
python-virtinst-0.400.3-9.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/python-virtinst-0.400.3-9.fc11
python-virtinst-0.400.3-9.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update python-virtinst'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9548
This should be fixed by python-virtinst-0.400.3-10.fc11 now in stable. Closing.