From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: RHEL guest oops with latest kvm-userspace
Date: Sun, 16 Nov 2008 15:25:18 +0100 [thread overview]
Message-ID: <49202D4E.7090804@web.de> (raw)
In-Reply-To: <49201261.6090508@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Jan Kiszka wrote:
>>
>>> Hi Avi,
>>>
>>> I've a problem with the last qemu-cvs merge into kvm-userspace: Booting
>>> the RHEL kernel 2.6.18-53.el5 in with more than one VCPU gives me
>>>
>>> Modules linked in:
>>> Pid: 0, comm: swapper Not tainted 2.6.18-53.el5 #1
>>> RIP: 0010:[<ffffffff8006dd6d>] [<ffffffff8006dd6d>]
>>> write_rdtscp_cb+0xa/0x
>
> I fixed a cpuid screwup which exposed rdtscp when it isn't present; this
> should be fixed in latest git.
It is, thanks.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-11-16 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 15:18 RHEL guest oops with latest kvm-userspace Jan Kiszka
2008-11-10 15:24 ` Jan Kiszka
2008-11-16 12:30 ` Avi Kivity
2008-11-16 14:25 ` Jan Kiszka [this message]
2008-11-12 10:13 ` Avi Kivity
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=49202D4E.7090804@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox