From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: Re: crash in nvmx_vcpu_destroy
Date: Thu, 21 Feb 2013 11:49:43 +0100 [thread overview]
Message-ID: <20130221104943.GA22260@aepfle.de> (raw)
In-Reply-To: <20130220145823.GA18129@aepfle.de>
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. And its
not clear why nestedhvm_vcpu_destroy calls into nvmx_vcpu_destroy
anyway. nestedhvm is not in the config file.
Olaf
next prev parent reply other threads:[~2013-02-21 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:58 crash in nvmx_vcpu_destroy Olaf Hering
2013-02-21 10:49 ` Olaf Hering [this message]
2013-02-21 11:03 ` Jan Beulich
2013-02-21 11:29 ` Jan Beulich
2013-02-21 11:08 ` Tim Deegan
2013-02-21 11:01 ` Tim Deegan
2013-02-21 11:10 ` Tim Deegan
2013-02-21 14:19 ` Olaf Hering
2013-02-21 14:22 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130221104943.GA22260@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.