From: Avi Kivity <avi@redhat.com>
To: n2CpHSJnr4MP@dyweni.com
Cc: KVM <kvm@vger.kernel.org>, Qemu Devel <qemu-devel@nongnu.org>,
Oprofile-List <oprofile-list@lists.sourceforge.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: general protection fault
Date: Thu, 02 Feb 2012 14:40:43 +0200 [thread overview]
Message-ID: <4F2A844B.107@redhat.com> (raw)
In-Reply-To: <3c9160646ba439b51b505543c0ac8275@pl1.haspere.com>
On 01/18/2012 06:40 AM, Dyweni - KVM wrote:
> Hi All,
>
> I'm not sure who this falls to, so I've included all all parties that
> I thought may be relevant.
>
> I'm getting the following error from my guest kernel when running
> oprofile within qemu-kvm:
>
kvm does not virtualize a PMU before Linux 3.3, so oprofile is not
supported. The facilities for identifying the PMU to the guest are very
lacking, so it's hard to make this fail gracefully.
On a Linux 3.3 host, you can provide a PMU to the guest, but only using
latest qemu and providing -cpu host or similar. This only works on
Intel hosts for now.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: n2CpHSJnr4MP@dyweni.com
Cc: Oprofile-List <oprofile-list@lists.sourceforge.net>,
Qemu Devel <qemu-devel@nongnu.org>, KVM <kvm@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] general protection fault
Date: Thu, 02 Feb 2012 14:40:43 +0200 [thread overview]
Message-ID: <4F2A844B.107@redhat.com> (raw)
In-Reply-To: <3c9160646ba439b51b505543c0ac8275@pl1.haspere.com>
On 01/18/2012 06:40 AM, Dyweni - KVM wrote:
> Hi All,
>
> I'm not sure who this falls to, so I've included all all parties that
> I thought may be relevant.
>
> I'm getting the following error from my guest kernel when running
> oprofile within qemu-kvm:
>
kvm does not virtualize a PMU before Linux 3.3, so oprofile is not
supported. The facilities for identifying the PMU to the guest are very
lacking, so it's hard to make this fail gracefully.
On a Linux 3.3 host, you can provide a PMU to the guest, but only using
latest qemu and providing -cpu host or similar. This only works on
Intel hosts for now.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-02 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 4:40 general protection fault Dyweni - KVM
2012-01-18 4:40 ` [Qemu-devel] " Dyweni - KVM
2012-01-18 5:22 ` Dyweni - KVM
2012-01-18 5:22 ` [Qemu-devel] " Dyweni - KVM
2012-02-02 12:15 ` Robert Richter
2012-02-02 12:15 ` Robert Richter
2012-02-02 12:15 ` Robert Richter
2012-02-02 12:40 ` Avi Kivity [this message]
2012-02-02 12:40 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-11-30 2:49 General Protection fault ADITYA KRISHNAN
2007-05-18 5:34 A minor cleanup Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A0174CF0E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-05-18 20:59 ` general protection fault Andrey Dmitriev
2007-05-20 7:21 ` Dor Laor
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=4F2A844B.107@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n2CpHSJnr4MP@dyweni.com \
--cc=oprofile-list@lists.sourceforge.net \
--cc=qemu-devel@nongnu.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.