On 04.02.2025 18:35, Andrew Cooper wrote:
> On 03/02/2025 8:58 am, Guillaume wrote:
>> Oh cool, thanks a lot for the explanation.
>> I added the "vzeroupper" and Xen crashes so it looks like the CPUID
>> emulation is buggy. Also I was able to try it using a VM (same debian
>> testing) running on vi
On 03/02/2025 8:58 am, Guillaume wrote:
> Oh cool, thanks a lot for the explanation.
> I added the "vzeroupper" and Xen crashes so it looks like the CPUID
> emulation is buggy. Also I was able to try it using a VM (same debian
> testing) running on virt-manager+kvm and it works fine (Xen in debug
>
Oh cool, thanks a lot for the explanation.
I added the "vzeroupper" and Xen crashes so it looks like the CPUID
emulation is buggy. Also I was able to try it using a VM (same debian
testing) running on virt-manager+kvm and it works fine (Xen in debug mode).
I will have a look by printing the xstate
On 02/02/2025 4:58 pm, Guillaume wrote:
> I attached the output of the `xl dmesg`. This is the 4.19.1 kernel I
> rebuild but I have the same issue with master (just for info).
Thanks. This is a TigerLake CPU, and:
> (XEN) Mitigating GDS by disabling AVX while virtualised - protections
> are best
I attached the output of the `xl dmesg`. This is the 4.19.1 kernel I
rebuild but I have the same issue with master (just for info).
And also as you said earlier it works with the default installation because
I see that the first line is:
`(XEN) [001476779e16] Xen version 4.19.1 (Debian 4.19.1-
Can you also get `xl dmesg` too, and attach it?
I think this is a VirtualBox bug, but I'm confused as to why Xen has
decided to turn off AVX.
~Andrew
On 02/02/2025 4:01 pm, Guillaume wrote:
> Yes sure I can collect the output. As you said the change is good
> enough to start the dom0 without err
Yes sure I can collect the output. As you said the change is good enough to
start the dom0 without errors (at least no apparent errors :).
```
Xen reports there are maximum 120 leaves and 2 MSRs
Raw policy: 32 leaves, 2 MSRs
CPUID:
leaf subleaf -> eax ebx ecx edx
:f
This is a sanity check that an algorithm in Xen matches hardware. It is
only compiled into debug builds by default.
Given that you're running under virtualbox, i have a suspicion as to what's
wrong.
Can you collect the full `xen-cpuid -p` output from within your
environment? I don't believe you
Hello,
I'd like to report an issue I encountered when building Xen from source.
To give you some context, During the Xen winter meetup in Grenoble few days
ago, there was a discussion about strengthening collaboration between Xen
and academia. One issue raised by a professor was that Xen is harde
