So finally tested with this:
-cpu host,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,-vmx
The used hyper-v enhancements are the ones generally recommended for
Windows vms.
Overall it seemed to really work: the performance was like bare metal,
and the BSOD second problem was also gone (for th
On Fri, Dec 29, 2023 at 2:10 PM Stefan Hajnoczi wrote:
> > First, performance: since some years ago, since prior to qemu 6.2 until
> > latest 8.2, win10 and win11 vms always worked slower than expected. This
> > could be noticed by comparing booting/starting times between vm and a
> > bare metal i
On Thu, Dec 28, 2023 at 11:45:18AM -0600, x...@trimaso.com.mx wrote:
> I noticed something weird when using "-cpu host" with Windows vms.
> First, I always use it along with ",hv_passthrough" as well.
>
> First, performance: since some years ago, since prior to qemu 6.2 until
> latest 8.2, win10 a
On Thu, 28 Dec 2023 at 17:21, wrote:
CCing Paolo, the general x86 maintainer.
Stefan
> I noticed something weird when using "-cpu host" with Windows vms.
> First, I always use it along with ",hv_passthrough" as well.
>
> First, performance: since some years ago, since prior to qemu 6.2 until
>
I noticed something weird when using "-cpu host" with Windows vms.
First, I always use it along with ",hv_passthrough" as well.
First, performance: since some years ago, since prior to qemu 6.2 until
latest 8.2, win10 and win11 vms always worked slower than expected. This
could be noticed by co