From: Luis Henriques <henrix@sapo.pt>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348
Date: Tue, 2 Dec 2008 19:09:14 +0000 [thread overview]
Message-ID: <20081202190914.GA12115@hades> (raw)
In-Reply-To: <493528D8.8010904@redhat.com>
On Tue, Dec 02, 2008 at 02:23:52PM +0200, Avi Kivity wrote:
> Luis Henriques wrote:
>> On Sun, Nov 30, 2008 at 10:44:55PM +0200, Avi Kivity wrote:
>>
>>> Luis Henriques wrote:
>>>
>>>> No, I was not able to reproduce the issue. Please let me know if you need some
>>>> more information on my system (.config, for instance).
>>>>
>>> Were you using some other virtualization product? Were you running
>>> suspend/resume?
>>>
>>
>> No for both questions. However, I had compiled support for suspend (not sure if
>> this is what you mean by "running suspend/resume") - This is a feature I used
>> only once or twice...
>>
>
> The underlying problem is that an svm instruction has been executed, but
> svm is disabled. Since kvm enables svm unconditionally on all
> processors on startup, there are only a few paths that can potentially
> trigger this:
>
> - another virtualization module turned svm off
> - cpu hotadd/hotremove (suspend/resume triggers this)
> - something did a read-modify-write cycle on cr4 (which contains the svm
> enable bit) while kvm enabled that bit
> - core was turned off (does linux power management do that?)
>
> Anything ring a bell?
Ok, I am not sure but there is a possibility of having the vboxdrv driver
loaded. _But_ I was not using, i.e., I do not use VirtualBox. In my
attempts to reproduce the issue, I tried to load this module but, unfortunatly,
my distro has this package broken ATM (err... in fact, the problem is not the
distro but me - I am using an unstable version).
vboxdrv could be a problem if I was using it, but I believe it shouldn't cause
this if it is not being used... but it's just a guess.
--
Luis Henriques
next prev parent reply other threads:[~2008-12-02 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 19:34 [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348 Luis Henriques
2008-11-30 20:20 ` Avi Kivity
2008-11-30 20:38 ` Luis Henriques
2008-11-30 20:44 ` Avi Kivity
2008-11-30 21:04 ` Luis Henriques
2008-12-02 12:23 ` Avi Kivity
2008-12-02 12:25 ` Avi Kivity
2008-12-02 12:31 ` Avi Kivity
2008-12-02 19:09 ` Luis Henriques [this message]
2008-12-02 19:27 ` Avi Kivity
2008-12-02 19:30 ` Avi Kivity
2008-12-02 19:46 ` Luis Henriques
2008-12-02 20:25 ` Steven Rostedt
2008-12-02 20:38 ` Avi Kivity
2008-12-02 20:48 ` Steven Rostedt
2008-12-02 20:56 ` Avi Kivity
2008-12-04 15:36 ` Avi Kivity
2008-12-04 22:05 ` Luis Henriques
2008-12-02 20:46 ` Luis Henriques
2008-12-02 21:16 ` Steven Rostedt
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=20081202190914.GA12115@hades \
--to=henrix@sapo.pt \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox