I installed the Windows 2003 server on the qemu emulator. After the first
shutdown using VNC Viewer I can't get there. At first It started writing
that this port is not listenening. Then I entered command qemu-system-i386.
After that I was able to connect, but instead of Windows there was written
N
Hi KVM & AMD folks,
We are trying to enable AVIC on Windows guest and AMD host machine, on upstream
kernel 5.8+. From our experiments and vmexit metrics, we can see AVIC brings us
huge benefits over decreased by >80% interrupt vmexit, and totally avoid vintr
and write_cr8 vmexits. But it seems
Paolo Bonzini writes:
> On 03/02/21 07:40, Kechen Lu wrote:
>> From the above observations, trying to see if there's a way for
>> enabling AVIC while also having the most optimized clock source for
>> windows guest.
>>
>
> You would have to change KVM, so that AVIC is only disabled if Auto-EOI
[resent for the previous non-plain text format]
Hi KVM & AMD folks,
We are trying to enable AVIC on Windows guest and AMD host machine, on upstream
kernel 5.8+. From our experiments and vmexit metrics, we can see AVIC brings us
huge benefits over decreased by >80% interrupt vmexit, and totally
I installed the Windows 2003 server on the qemu emulator. After the first
shutdown using VNC Viewer I can't get there. At first It started writing
that this port is not listenening. Then I entered command qemu-system-i386.
After that I was able to connect, but instead of Windows there was written
N
Cc'ing qemu-block@ developers.
On 10/28/20 6:18 AM, daggs wrote:
> Greetings,
>
> I have a vm running under qemu 5.1.0 with a cdrom scsi passthough into it.
> I can eject the device in and out but when I insert a disc, is isn't detected
> and the dmesg on the guest is filled with these prints:
>
Greetings Philippe,
> Sent: Wednesday, February 03, 2021 at 6:48 PM
> From: "Philippe Mathieu-Daudé"
> To: "daggs" , qemu-discuss@nongnu.org
> Cc: "qemu-devel" , "Qemu-block"
> Subject: Re: cdrom scsi passthough not working well
>
> Cc'ing qemu-block@ developers.
>
> On 10/28/20 6:18 AM, daggs
Hi Vitaly and Paolo,
Thanks so much for quick reply. This makes sense to me. From my understanding,
basically this can be two part of it to resolve it.
First, we make sure to set and expose 0x4004.EAX Bit9 to windows guest,
like in kvm_vcpu_ioctl_get_hv_cpuid(), having this recommendation
