> On 11 Jul 2024, at 12:56 PM, David Woodhouse wrote:
>
> On Mon, 2024-07-08 at 10:13 +0100, David Woodhouse wrote:
>> On Wed, 2024-07-03 at 16:01 +, Sandesh Patel wrote:
>>>>
>>>> Interesting. What exactly has Windows *done* in those MSI entries?
&
On 11 Jul 2024, at 5:22 PM, Sandesh Patel wrote:
Thanks David for all the analysis.
Looking at the Linux guest support, it seems to look just at the HyperV
CPUID leaves 0x4081 and 0x4082. QEMU knows of those only for
SYNDBG; Sandesh do you want to try setting the
Thanks David for all the analysis.
> On 11 Jul 2024, at 4:53 PM, David Woodhouse wrote:
>
> On Thu, 2024-07-11 at 08:26 +0100, David Woodhouse wrote:
>>
>> I used identical command lines on both, and on each host I got the same
>> result with all of '-cpu host', '-cpu EPYC' and -cpu Skylake-Ser
Thanks David for the response.
On 2 Jul 2024, at 2:34 PM, David Woodhouse wrote:
On Tue, 2024-07-02 at 05:17 +, Sandesh Patel wrote:
Hi All,
Is it possible to setup a large Windows VM (say 512 vcpus) without
adding viommu (EIM=on, IR=on)?
When I try to power such VM, the qemu process
Hi All,
Is it possible to setup a large Windows VM (say 512 vcpus) without adding
viommu (EIM=on, IR=on)?
When I try to power such VM, the qemu process crashes with error-
```
qemu-kvm: ../accel/kvm/kvm-all.c:1837: kvm_irqchip_commit_routes: Assertion
`ret == 0’ failed
```
Stack trace-
```
#1
Hi All,
Is it possible to setup a large Windows VM (say 512 vcpus) without adding
viommu (EIM=on, IR=on)?
When I try to power such VM, the qemu process crashes with error-
```
qemu-kvm: ../accel/kvm/kvm-all.c:1837: kvm_irqchip_commit_routes: Assertion
`ret == 0’ failed
```
Stack trace-
```
#1
