From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: kvm@vger.kernel.org
Subject: Re: 32-bit qemu on current x86-64 kernel segfauls very early
Date: Tue, 02 Nov 2010 11:59:48 -0400 [thread overview]
Message-ID: <4CD03574.6090708@redhat.com> (raw)
In-Reply-To: <20101102151103.GA4726@infradead.org>
On 11/02/2010 11:11 AM, Christoph Hellwig wrote:
> On Sun, Oct 31, 2010 at 09:06:29AM -0400, Christoph Hellwig wrote:
> > With Linus' git tree from today I can't boot qemu when using kvm. It
> > seems to do fine, just glacially slow without -enable-kvm. The command
> > simplest command line that fails is:
> >
> > /opt/qemu/bin/qemu-system-x86_64 -enable-kvm
>
> This issue was caused by commit 9581d442b9058d3699b4be568b6e5eae38a41493
>
> "KVM: Fix fs/gs reload oops with invalid ldt"
>
Interesting, I guess we corrupt %fs on x86_64.
Intel or AMD?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-11-02 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 13:06 32-bit qemu on current x86-64 kernel segfauls very early Christoph Hellwig
2010-11-02 15:11 ` Christoph Hellwig
2010-11-02 15:59 ` Avi Kivity [this message]
2010-11-02 16:02 ` Christoph Hellwig
2010-11-02 19:10 ` Avi Kivity
2010-11-03 12:37 ` Michael S. Tsirkin
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=4CD03574.6090708@redhat.com \
--to=avi@redhat.com \
--cc=hch@infradead.org \
--cc=kvm@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 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.