On 23.11.2015 08:51, Jan Beulich wrote:
On 23.11.15 at 08:37, wrote:
>> Actually there's no problem with ICEBP - just like INTnn it isn't itself
>> interceptable (and the injection of vector 0x01 from the x86
>> emulator path can't fully distinguish between ICEBP and INT $1 in
>> these old v
>>> On 23.11.15 at 08:37, wrote:
> Actually there's no problem with ICEBP - just like INTnn it isn't itself
> interceptable (and the injection of vector 0x01 from the x86
> emulator path can't fully distinguish between ICEBP and INT $1 in
> these old versions anyway). So what you have should be g
>>> On 20.11.15 at 18:07, wrote:
> On 20.11.2015 17:54, Jan Beulich wrote:
> On 20.11.15 at 17:15, wrote:
>>> So this is a quick hack I just tried and that keeps the HVM alive:
>>>
>>> @@ -1294,7 +1288,6 @@ void vmx_inject_hw_exception(int trap, i
>>> switch ( trap )
>>> {
>>>
On 20.11.2015 17:54, Jan Beulich wrote:
On 20.11.15 at 17:15, wrote:
>> So this is a quick hack I just tried and that keeps the HVM alive:
>>
>> @@ -1294,7 +1288,6 @@ void vmx_inject_hw_exception(int trap, i
>> switch ( trap )
>> {
>> case TRAP_debug:
>> -type = X86_EVE
>>> On 20.11.15 at 17:15, wrote:
> So this is a quick hack I just tried and that keeps the HVM alive:
>
> @@ -1294,7 +1288,6 @@ void vmx_inject_hw_exception(int trap, i
> switch ( trap )
> {
> case TRAP_debug:
> -type = X86_EVENTTYPE_SW_EXCEPTION;
> if ( guest_cpu_
On 20.11.2015 17:10, Stefan Bader wrote:
> On 20.11.2015 16:59, Jan Beulich wrote:
> On 20.11.15 at 16:03, wrote:
>>> I am currently trying to backport the changes of XSA156 back to Xen-4.1.x
>>> and I
>>> am struggling with the VMX side. I did see the backports made for 4.2 and
>>> 3.4 on
>
On 20.11.2015 16:59, Jan Beulich wrote:
On 20.11.15 at 16:03, wrote:
>> I am currently trying to backport the changes of XSA156 back to Xen-4.1.x
>> and I
>> am struggling with the VMX side. I did see the backports made for 4.2 and
>> 3.4 on
>> the security mailing list but I am not sure th
>>> On 20.11.15 at 16:03, wrote:
> I am currently trying to backport the changes of XSA156 back to Xen-4.1.x and
> I
> am struggling with the VMX side. I did see the backports made for 4.2 and 3.4
> on
> the security mailing list but I am not sure the 3.4 backport is not having the
> same issues
