Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 953939

Summary: No hardware acceleration for virtualized guests
Product: [Community] Spacewalk Reporter: Simon Coy <slabber>
Component: ServerAssignee: Stephen Herr <sherr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.9CC: sebastian, slabber
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-01 20:11:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    

Description Simon Coy 2013-04-19 15:15:37 UTC 
Description of problem:
I don’t think any virtualized guests on RHEL/CentOS 6 are being hardware accelerated anymore.  After provisioning a virtual guest using a kickstart profile with Virtualization Type = “KVM Virtualized Guest”, virt-install on the host system always runs with option –virt-type=qemu.  This has the effect that by default, libvirt will now run the guest without hardware acceleration.

Is there a way on RHEL/CentOS 6 to enable KVM support by passing through virt-type=kvm instead?  I have tried manually setting the virt-type in cobbler but this doesn’t seem to affect the task being pulled by rhn_check.


Version-Release number of selected component (if applicable):
libvirt-client-0.10.2-18.el6_4.4.x86_64
libvirt-0.10.2-18.el6_4.4.x86_64
libvirt-python-0.10.2-18.el6_4.4.x86_64
spacewalk-backend-libs-1.9.48-1.el6.noarch
spacewalk-koan-1.9.2-1.el6.noarch
rhn-virtualization-common-5.4.44-1.el6.noarch
rhn-virtualization-host-5.4.44-1.el6.noarch
cobbler-epel-2.0.11-14.el6.noarch
cobbler-2.2.3-2.el6.noarch

How reproducible:
Kickstart a new virtual guest

Steps to Reproduce:
1.Spacewalk webUI -> Systems -> <Virtualization Host> -> Virtualization -> Provisioning
2.Enter 'Guest Name'
3.Schedule kickstart and finish
  
Actual results:
New VM runs without hardware acceleration.

Expected results:
New VM runs with hardware acceleration.

Additional info:
None
Comment 1 Michael Mráka 2013-10-21 13:31:34 UTC 
Hello Simon,

Spacewalk do not create guests via virt-install but spacewalk-koan.
Moreover I can see guest kickstarted from "KVM Virtualized Guest” profile and it's running with 
  /usr/libexec/qemu-kvm -name virt1 -S -M rhel6.4.0 -enable-kvm ...
On Spacewalk > Systems > <guest_name> > Details > Hardware I can see
Vendor: 	 Seabios
System: 	 KVM RHEL 6.4.0 PC 
Product: 	 KVM

Packages installed on my host machine:
# rpm -q libvirt-client libvirt libvirt-python spacewalk-koan rhn-virtualization-common rhn-virtualization-host 
libvirt-client-0.10.2-18.el6_4.14.x86_64
libvirt-0.10.2-18.el6_4.14.x86_64
libvirt-python-0.10.2-18.el6_4.14.x86_64
spacewalk-koan-2.0.1-2.el6sat.noarch
rhn-virtualization-common-5.4.48-1.el6sat.noarch
rhn-virtualization-host-5.4.48-1.el6sat.noarch

Could you provide more details for your setup?
Do you have kvm kernel modules loaded?
 lsmod |grep kvm
Comment 2 Stephen Herr 2014-07-01 20:11:18 UTC 
This should be fixed as part of bug 1109276, which should be fixed in the next release of Spacewalk. When it is released ensure that you are using the latest packages from Spacewalk and have the newest version of koan installed from EPEL on your virt host and your provisioned guests should correctly use kvm acceleration.

*** This bug has been marked as a duplicate of bug 1109276 ***
Comment 3 Eric Herget 2017-09-28 18:10:02 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.