Re: [Xen-devel] crash in nvmx_vcpu_destroy

[Tim Deegan <tim@xxxxxxx>]

At 11:49 +0100 on 21 Feb (1361447383), Olaf Hering wrote:
> On Wed, Feb 20, Olaf Hering wrote:
> 
> > (XEN) Xen call trace:
> > (XEN)    [<ffff82c4c01dd197>] nvmx_vcpu_destroy+0xb7/0x150
> > (XEN)    [<ffff82c4c01b5ce9>] hvm_vcpu_destroy+0x9/0x40
> 
> For some reason nestedhvm_vcpu_destroy is not in the backtrace.

On non-debug builds, nestedhvm_vcpu_destroy gets compiled using a tail
call (i.e. it jumps to the arch-specific function and lets that return
directly to the caller).

> And its not clear why nestedhvm_vcpu_destroy calls into
> nvmx_vcpu_destroy anyway. nestedhvm is not in the config file.

Intriguing.  I wonder what sets the hvm-param then.

Tim.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel