Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2013-05-10 17:39, Kashyap Chamarthy wrote:
> On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>> On 2013-05-10 17:12, Jan Kiszka wrote:
>>> On 2013-05-10 15:00, Kashyap Chamarthy wrote:
>>>> Heya,
>>>>
>>>> This is on Intel Haswell.
>>>>
>>>> First, some version info:
>>>>
>>>> L0, L1 -- both of them have same versions of kernel, qemu:
>>>>
>>>> =====
>>>> $ rpm -q kernel --changelog | head -2
>>>> * Thu May 09 2013 Josh Boyer  - 3.10.0-0.rc0.git23.1
>>>> - Linux v3.9-11789-ge0fd9af
>>>
>>> Please recheck with kvm.git, next branch.
>>
>> Hmm, looks like your branch already contains the patch I was thinking of
>> (03b28f8).
> 
> Yes.
> 
>>
>> You could try if leaving shadow VMCS off makes a difference, but I bet
>> that is unrelated.
> 
> Right. I could try. But, like you said, does it *really* make a difference.

We know after you tried. I don't have access to a Haswell box, so we
better exclude this beforehand.

> 
>> You get that backtrace in L1, correct?
> 
> Yes.
> 
> If you have any further tracing pointers, I could do some debugging.

Thanks, I may come back to you if reproduction fails here.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux