> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, March 01, 2017 11:40 PM
>
> >>> On 01.03.17 at 16:23, wrote:
> > On Wed, 2017-03-01 at 07:28 -0700, Jan Beulich wrote:
> >> > > > On 01.03.17 at 15:22, wrote:
> >> >
> >> > On Wed, 2017-03-01 at 07:04 -0700, Jan Beulich wrote:
> >
>>> On 01.03.17 at 16:23, wrote:
> On Wed, 2017-03-01 at 07:28 -0700, Jan Beulich wrote:
>> > > > On 01.03.17 at 15:22, wrote:
>> >
>> > On Wed, 2017-03-01 at 07:04 -0700, Jan Beulich wrote:
>> > > > > > On 01.03.17 at 14:44, wrote:
>> > > >
>> > > > Additionally, it would be painful to return
On Wed, 2017-03-01 at 07:28 -0700, Jan Beulich wrote:
> > > > On 01.03.17 at 15:22, wrote:
> >
> > On Wed, 2017-03-01 at 07:04 -0700, Jan Beulich wrote:
> > > > > > On 01.03.17 at 14:44, wrote:
> > > >
> > > > Additionally, it would be painful to return the correct error value
> > > > all the w
>>> On 01.03.17 at 15:22, wrote:
> On Wed, 2017-03-01 at 07:04 -0700, Jan Beulich wrote:
>> > > > On 01.03.17 at 14:44, wrote:
>> > Additionally, it would be painful to return the correct error value
>> > all the way back to nvmx_handle_vmptrld().
>>
>> Surely that's at best relevant in the othe
On Wed, 2017-03-01 at 07:04 -0700, Jan Beulich wrote:
> > > > On 01.03.17 at 14:44, wrote:
> >
> > On Wed, 2017-03-01 at 05:55 -0700, Jan Beulich wrote:
> > > > > > On 01.03.17 at 10:13, wrote:
> > > >
> > > > If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
> > > > during vm
>>> On 01.03.17 at 14:44, wrote:
> On Wed, 2017-03-01 at 05:55 -0700, Jan Beulich wrote:
>> > > > On 01.03.17 at 10:13, wrote:
>> >
>> > If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
>> > during vmread/vmwrite:
>> >
>> > (XEN) Xen BUG at .../git/upstream/xen/xen/include/as
On Wed, 2017-03-01 at 05:55 -0700, Jan Beulich wrote:
> > > > On 01.03.17 at 10:13, wrote:
> >
> > If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
> > during vmread/vmwrite:
> >
> > (XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
> > (XEN) [ Xen-4.
>>> On 01.03.17 at 14:22, wrote:
> On 01/03/17 12:55, Jan Beulich wrote:
> On 01.03.17 at 10:13, wrote:
>>> If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
>>> during vmread/vmwrite:
>>>
>>> (XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
>>> (XEN)
On 01/03/17 12:55, Jan Beulich wrote:
On 01.03.17 at 10:13, wrote:
>> If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
>> during vmread/vmwrite:
>>
>> (XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
>> (XEN) [ Xen-4.9-unstable x86_64 debug=y
>>> On 01.03.17 at 10:13, wrote:
> If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
> during vmread/vmwrite:
>
> (XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
> (XEN) [ Xen-4.9-unstable x86_64 debug=y Tainted:H ]
> (XEN) Xen call trace:
On 01/03/17 09:13, Sergey Dyasli wrote:
> If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
> during vmread/vmwrite:
>
> (XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
> (XEN) [ Xen-4.9-unstable x86_64 debug=y Tainted:H ]
> (XEN) Xen call t
If nested vmcs's address is invalid, virtual_vmcs_enter() will fail
during vmread/vmwrite:
(XEN) Xen BUG at .../git/upstream/xen/xen/include/asm/hvm/vmx/vmx.h:333
(XEN) [ Xen-4.9-unstable x86_64 debug=y Tainted:H ]
(XEN) Xen call trace:
(XEN)[] vmcs.c#arch/x86/hvm/vmx/vmcs.o.un
12 matches
Mail list logo