>
> None of these require extra state (i.e. registers), hence ...
>
>> Per my current understanding, I would expect more xstates on the VM than
>> supported on the target
>> server and hence a failure with xstate verification when restoring CPU state.
>
> ... no extra "xstates" (as you name it).
On 06.08.2024 11:30, Fonyuy-Asheri Caleb wrote:
> Seems there's more to this than I think. Here's the entire information about
> my setup.
>
> Source Server:
>Processor: Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz
>Xsave dependences(based on xen gen-cpuid.py):
> '
> On 06.08.2024 09:34, Fonyuy-Asheri Caleb wrote:
>>> If what you say in the earlier paragraph was the case with upstream Xen and
>>> without you restricting what the guest being migrated was able to see on the
>>> source host, then I think that would indicate a bug somewhere. Yet you don't
>>>
On 06.08.2024 09:34, Fonyuy-Asheri Caleb wrote:
>> If what you say in the earlier paragraph was the case with upstream Xen and
>> without you restricting what the guest being migrated was able to see on the
>> source host, then I think that would indicate a bug somewhere. Yet you don't
>> provide e
> If what you say in the earlier paragraph was the case with upstream Xen and
> without you restricting what the guest being migrated was able to see on the
> source host, then I think that would indicate a bug somewhere. Yet you don't
> provide enough details to be certain.
>
> Jan
Sorry for not
On 06.08.2024 09:04, Fonyuy-Asheri Caleb wrote:
>> On 15/07/2024 9:16 am, Jan Beulich wrote:
>>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
> Perhaps the more important question, are you booting the skylake with
> cpuid=no-avx on the command line by any chance?
No. I didn't boot a
Hello Andrew,
Hello Jan,
Please permit me to come back to this once again.
> On 15/07/2024 9:16 am, Jan Beulich wrote:
>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
Perhaps the more important question, are you booting the skylake with
cpuid=no-avx on the command line by any chanc
On 15/07/2024 9:16 am, Jan Beulich wrote:
> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>>> Perhaps the more important question, are you booting the skylake with
>>> cpuid=no-avx on the command line by any chance?
>> No. I didn't boot any of the machines with any cpuid modification
>> whatsoev
> On 15.07.2024 10:48, Fonyuy-Asheri Caleb wrote:
> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>>> Perhaps the more important question, are you booting the skylake with
>>> cpuid=no-avx on the command line by any chance?
>>
>> No. I didn't boot any of the machines with an
On 15.07.2024 10:48, Fonyuy-Asheri Caleb wrote:
On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>> Perhaps the more important question, are you booting the skylake with
>> cpuid=no-avx on the command line by any chance?
>
> No. I didn't boot any of the machines with any cpuid m
>>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
> Perhaps the more important question, are you booting the skylake with
> cpuid=no-avx on the command line by any chance?
No. I didn't boot any of the machines with any cpuid modification
whatsoever.
>>>
>>> Yet is there pe
On 15.07.2024 10:22, Fonyuy-Asheri Caleb wrote:
> - Original Message -
>> From: "Jan Beulich"
>> To: "Fonyuy-Asheri Caleb"
>> Cc: "xen-devel" , "Andrew Cooper"
>>
>> Sent: Monday, July 15, 2024 10:16:07 AM
&g
- Original Message -
> From: "Jan Beulich"
> To: "Fonyuy-Asheri Caleb"
> Cc: "xen-devel" , "Andrew Cooper"
>
> Sent: Monday, July 15, 2024 10:16:07 AM
> Subject: Re: Help with Understanding vcpu xstate restore error during v
On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>> Perhaps the more important question, are you booting the skylake with
>> cpuid=no-avx on the command line by any chance?
>
> No. I didn't boot any of the machines with any cpuid modification whatsoever.
Yet is there perhaps "Mitigating GDS by di
>> PV Default policy: 30 leaves, 2 MSRs
>> ...
>> 000d: -> 0003::0240:
>> 000d:0001 -> 0007:::
>
> ... PV guests get nothing, while you're trying to migrate in a guest
> which...
>
>> =
Ok, so trimming down to the relevant pieces, we have:
On 11/07/2024 12:09 pm, Fonyuy-Asheri Caleb wrote:
> =
> Source server xen-cpuid -p
> ==
On 12.07.2024 11:08, Fonyuy-Asheri Caleb wrote:
>>> I was able to locate the failure point to the file
>>> xen/arch/x86/domctl.c with the following check.
>>>
>>> if( evc->size>> evc->size>PV_XSAVE_SIZE(xfeature_mask) )
>>> gotovcpuextstate_out;
>>
>> It is certainly more complicated than that.
>>
Hi Andrew,
>> I was able to locate the failure point to the file
>> xen/arch/x86/domctl.c with the following check.
>>
>> if( evc->size> evc->size>PV_XSAVE_SIZE(xfeature_mask) )
>> gotovcpuextstate_out;
>
> It is certainly more complicated than that.
>
> What that's saying is that Xen doesn't
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb"
> Cc: "xen-devel" , "Jan Beulich"
> , "Roger Pau Monné"
>
> Sent: Thursday, July 11, 2024 3:04:05 PM
> Subject: Re: Help with Understanding
On 11/07/2024 1:18 pm, Fonyuy-Asheri Caleb wrote:
>>> Please do you mind giving me more insight on the logic currently implemented
>>> and maybe what is wrong with it? It will be important for me since what I'm
>>> doing is research work.
>> See 9e6dbbe8bf40^..267122a24c49
> What reference is this
>> Please do you mind giving me more insight on the logic currently implemented
>> and maybe what is wrong with it? It will be important for me since what I'm
>> doing is research work.
>
> See 9e6dbbe8bf40^..267122a24c49
What reference is this please?
>
>> How do the values evc->size and xf
On 11/07/2024 12:09 pm, Fonyuy-Asheri Caleb wrote:
> - Original Message -
>> From: "Andrew Cooper"
>> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>>
>> Sent: Thursday, July 11, 2024 12:45:18 PM
>> Subject: Re: Help with Unders
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>
> Sent: Thursday, July 11, 2024 12:45:18 PM
> Subject: Re: Help with Understanding vcpu xstate restore error during vm
> migration
> On 11/07
On 11/07/2024 11:38 am, Fonyuy-Asheri Caleb wrote:
> Hello,
>
> I am trying to understand the causes of the vcpu xstate restore error
> during live migration.
> I get the following error during live migration:
>
> xc: error: Failed to set vcpu0's xsave info (22 = Invalid argument):
> Internal e
24 matches
Mail list logo
