==
> > Analyze events for all VMs, all VCPUs:
> > VM-EXITSamples Samples% Time%Min TimeMax
> > Time Avg time
> >MSR_WRITE 92404589.96%81.10% 0.42us
> > 68.42us 1.26us ( +- 0.07% )
> >
Liang Li writes:
>> >> > Analyze events for all VMs, all VCPUs:
>> >> > VM-EXITSamples Samples% Time%Min TimeMax
>> >> > Time Avg time
>> >> > EXTERNAL_INTERRUPT 47183159.89%68.58% 0.64us
>> >> > 65.42us 2.34us ( +- 0.11% )
>> >> >
> >> > Analyze events for all VMs, all VCPUs:
> >> > VM-EXITSamples Samples% Time%Min TimeMax
> >> > Time Avg time
> >> > EXTERNAL_INTERRUPT 47183159.89%68.58% 0.64us
> >> > 65.42us 2.34us ( +- 0.11% )
> >> >MSR_WRITE
Liang Li writes:
>> > Hi Vitaly,
>> >
>> > I found a case that the virtualization overhead was almost doubled
>> > when turning on Hper-v related features compared to that without any
>> > no hyper-v feature. It happens when running a 3D game in windows
>> > guest in qemu kvm environment.
>> >
> > Hi Vitaly,
> >
> > I found a case that the virtualization overhead was almost doubled
> > when turning on Hper-v related features compared to that without any
> > no hyper-v feature. It happens when running a 3D game in windows
> > guest in qemu kvm environment.
> >
> > By investigation, I
Liang Li writes:
> [resend for missing cc]
>
> Hi Vitaly,
>
> I found a case that the virtualization overhead was almost doubled
> when turning on Hper-v related features compared to that without any
> no hyper-v feature. It happens when running a 3D game in windows
> guest in qemu kvm
[resend for missing cc]
Hi Vitaly,
I found a case that the virtualization overhead was almost doubled
when turning on Hper-v related features compared to that without any
no hyper-v feature. It happens when running a 3D game in windows
guest in qemu kvm environment.
By investigation, I found
