Bug 1320594

Summary: enable hyperv optimizations by default
Product: [oVirt] ovirt-engine Reporter: Francesco Romani <fromani>
Component: Backend.CoreAssignee: Francesco Romani <fromani>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: medium    
Version: 3.6.3.3CC: bugs, mgoldboi, michal.skrivanek
Target Milestone: ovirt-3.6.6Flags: rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+
Target Release: 3.6.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-30 10:51:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1320733    

Description Francesco Romani 2016-03-23 15:11:24 UTC 
Description of problem:
In bug https://bugzilla.redhat.com/1163828 we disabled the hyperv optimization by default because the recommended supported hypervisor was RHEL6, on which some instabilities where reported.

Nowadays Engine >= 3.6 requires RHEL7, which much more modern and improved QEMU, which should now support hyperv fine.

We also heard encouraging reports from virt QE, so let's trust them and try again enabling HyperV by default.


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

How reproducible:
100%


Steps to Reproduce:
1. Prepare windows >= 2008 VM
2. Run the VM
3. verify the HyperV optimization are not enabled (no "hypervEnable" parameter sent to Vdsm)

Actual results:
No HyperV optimizations enabled even though QEMU supports all of them

Expected results:
Windows >= 2008 VMs should get the optimizations
Comment 1 Red Hat Bugzilla Rules Engine 2016-03-23 15:11:28 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 meital avital 2016-05-22 07:32:56 UTC 
Verified on version: 3.6.6.2-0.1.el6 

Verified steps:
1) Have 2 VMS, win2008 on cluster 3.6 and win2012 on cluster 3.5
2) Run the VMs

For win2008 on Cluster 3.6 we can see the <hyperv> section:
[root@amd-vfio ~]# virsh -r dumpxml 36 | less

 <hyperv>
     <relaxed state='on'/>
     <vapic state='on'/>
     <spinlocks state='on' retries='8191'/>
   </hyperv>
 </features>
 <cpu mode='custom' match='exact'>
   <model fallback='allow'>Opteron_G3</model>
   <topology sockets='16' cores='1' threads='1'/>
   <numa>
     <cell id='0' cpus='0-1' memory='4194304' unit='KiB'/>
   </numa>
 </cpu>
 <clock offset='variable' adjustment='-25199' basis='utc'>
   <timer name='hypervclock' present='yes'/>
   <timer name='rtc' tickpoli

For win2012 on Cluster 3.5 I validate that there is no  <hyperv> section.