Bug 1320594 - enable hyperv optimizations by default
Summary: enable hyperv optimizations by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.3.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-3.6.6
: 3.6.6
Assignee: Francesco Romani
QA Contact: meital avital
URL:
Whiteboard: virt
Depends On:
Blocks: 1320733
TreeView+ depends on / blocked
 
Reported: 2016-03-23 15:11 UTC by Francesco Romani
Modified: 2016-05-30 10:51 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-30 10:51:56 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 55117 0 master MERGED hyperv: default on again for windows >= 2008/2012 2016-04-11 15:14:28 UTC
oVirt gerrit 55984 0 ovirt-engine-3.6 MERGED hyperv: default on again for windows >= 2008/2012 2016-04-11 17:08:25 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.