qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Sandesh Patel <sandesh.patel@nutanix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Rob Scheepens <rob.scheepens@nutanix.com>,
	Prerna Saxena <confluence@nutanix.com>,
	Dexuan Cui <decui@microsoft.com>, Alexander Graf <alex@csgraf.de>
Subject: Re: More than 255 vcpus Windows VM setup without viommu ?
Date: Wed, 24 Jul 2024 10:22:03 +0100	[thread overview]
Message-ID: <eb1cef16ff02bbd80536e10bb7f0a59fb42d7c56.camel@infradead.org> (raw)
In-Reply-To: <0957DDAE-1214-4502-BC03-1A18D02B613E@nutanix.com>

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

On Tue, 2024-07-16 at 05:13 +0000, Sandesh Patel wrote:
> 
> 
> > On 11 Jul 2024, at 5:22 PM, Sandesh Patel <sandesh.patel@nutanix.com> wrote:
> > 
> > Thanks David for all the analysis.
> > > 
> > > Looking at the Linux guest support, it seems to look just at the HyperV
> > > CPUID leaves 0x40000081 and 0x40000082. QEMU knows of those only for
> > > SYNDBG; Sandesh do you want to try setting the
> > > HYPERV_VS_PROPERTIES_EAX_EXTENDED_IOAPIC_RTE bit that Linux looks for,
> > > and see how that affects Windows guests (with no emulated IOMMU)?
> > > 
> > 
> 
> I am enabling same bit (BIT(2) under
> HYPERV_CPUID_SYNDBG_PLATFORM_CAPABILITIES (0x40000082) with simple
> kvm patch (need to check how do we switch to 15 bit destination id
> when enabling this)-
> 
> 
> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
> index 04cca46fed1e..b9e74b791247 100644
> --- a/arch/x86/kvm/hyperv.c
> +++ b/arch/x86/kvm/hyperv.c
> @@ -2567,6 +2567,7 @@ int kvm_get_hv_cpuid(struct kvm_vcpu *vcpu, struct kvm_cpuid2 *cpuid,
>  
>                 case HYPERV_CPUID_SYNDBG_PLATFORM_CAPABILITIES:
>                         ent->eax |= HV_X64_SYNDBG_CAP_ALLOW_KERNEL_DEBUGGING;
> +                      ent->eax |= HYPERV_VS_PROPERTIES_EAX_EXTENDED_IOAPIC_RTE;
>                         break;
>  
>                 default:
> diff --git a/arch/x86/kvm/hyperv.h b/arch/x86/kvm/hyperv.h
> index 1030b1b50552..384585a1f165 100644
> --- a/arch/x86/kvm/hyperv.h
> +++ b/arch/x86/kvm/hyperv.h
> @@ -41,6 +41,7 @@
>   * These are HYPERV_CPUID_SYNDBG_PLATFORM_CAPABILITIES.EAX bits.
>   */
>  #define HV_X64_SYNDBG_CAP_ALLOW_KERNEL_DEBUGGING       BIT(1)
> +#define HYPERV_VS_PROPERTIES_EAX_EXTENDED_IOAPIC_RTE   BIT(2)
>  
>  /* Hyper-V Synthetic debug options MSR */
>  #define HV_X64_MSR_SYNDBG_CONTROL              0x400000F1
> 
> 
> I am hitting an issue where the Windows guest is not booting (guest
> reset in loop) when adding hv-syndbg hyperv feature (or using hv-
> passthrough). Possibly an occurrence of -
>  https://patchew.org/QEMU/20230612084201.294248-1-vkuznets@redhat.com
> /
> Anything special to take care here?

As a simple test, have you tried just *not* setting the
ALLOW_KERNEL_DEBUGGING bit? Just comment that line out? So we're only
setting the magic value in 0x40000081 and then the extended I/OAPIC RTE
bit in 0x40000082? 

Although we've heard separately that this *isn't* implemented in
Windows, so we guess it isn't going to work.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]

  reply	other threads:[~2024-07-24  9:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  5:17 More than 255 vcpus Windows VM setup without viommu ? Sandesh Patel
2024-07-02  9:04 ` David Woodhouse
2024-07-03 16:01   ` Sandesh Patel
2024-07-08  9:13     ` David Woodhouse
2024-07-11  7:26       ` David Woodhouse
2024-07-11 11:23         ` David Woodhouse
2024-07-11 11:52           ` Sandesh Patel
2024-07-16  5:13             ` Sandesh Patel
2024-07-24  9:22               ` David Woodhouse [this message]
2024-08-01 10:28         ` Sandesh Patel
2024-09-28 14:59 ` David Woodhouse
2024-09-30 15:50   ` David Woodhouse
2024-10-02 11:33     ` Igor Mammedov
2024-10-02 15:30       ` David Woodhouse
2024-10-01 13:33   ` Daniel P. Berrangé
2024-10-01 16:37     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2024-07-02  7:20 Sandesh Patel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb1cef16ff02bbd80536e10bb7f0a59fb42d7c56.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=alex@csgraf.de \
    --cc=confluence@nutanix.com \
    --cc=decui@microsoft.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob.scheepens@nutanix.com \
    --cc=sandesh.patel@nutanix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).