Great news! Just remember to also turn off memballoon as mentioned in one of my previous posts. For some inexplicable reason virt-manager turns memballoon on by default. It doesn’t work with Windows.
Also note that host-model is not the same as host-passthrough. In many cases host-passthrough is performing better, but there are exceptions.
In addition, there are hypervisor enlightenments (features) that can be turned on. Here is my features section for comparison:
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state="on"/>
<vapic state="on"/>
<spinlocks state="on" retries="8191"/>
<vpindex state="on"/>
<runtime state="on"/>
<synic state="on"/>
<stimer state="on">
<direct state="on"/>
</stimer>
<reset state="on"/>
<vendor_id state="on" value="AuthenticAMD"/>
<frequencies state="on"/>
<reenlightenment state="on"/>
<tlbflush state="on"/>
<ipi state="on"/>
<evmcs state="off"/>
</hyperv>
<kvm>
<hidden state="on"/>
</kvm>
<vmport state="off"/>
<ioapic driver="kvm"/>
</features>
In above configuration, you need the section only if you pass through a Nvidia GPU.
Another section that has impact on performance is the timing section (clock):
<clock offset="localtime">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
<timer name="hypervclock" present="yes"/>
<timer name="tsc" present="yes" mode="native"/>
</clock>
Note the last line.
The above examples are only relevant if you want or need to tweak VM performance. If that is not an issue, leave as is and be happy.