From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: RHEL guest oops with latest kvm-userspace
Date: Wed, 12 Nov 2008 12:13:05 +0200 [thread overview]
Message-ID: <491AAC31.1010307@redhat.com> (raw)
In-Reply-To: <491850B8.6010700@siemens.com>
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
>
> RIP: 0010:[<ffffffff8006dd6d>] [<ffffffff8006dd6d>] write_rdtscp_cb+0xa/0xd
>
...
> I suspect that is due to some lost features or regression around cpuid
> after the kvm merge into qemu, but I can't bisect in that reagion. Any
> ideas? Further info needed? Just let me know.
You're right - rdtscp probably appeared out of nowhere. I'll fix it up.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-11-12 10:13 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
2008-11-12 10:13 ` Avi Kivity [this message]
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=491AAC31.1010307@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.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