From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
Date: Fri, 10 Feb 2012 09:18:36 GMT [thread overview]
Message-ID: <201202100918.q1A9IaX2024632@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42755-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42755
--- Comment #2 from Michael Tokarev <mjt@tls.msk.ru> 2012-02-10 09:18:35 ---
This is very unlikely to do with the kernel. Qemu (which you're using to run
your guest -- kvm is just in-kernel module) will emulate whole machine
including CPU in case it can't access /dev/kvm or if you requested to not use
it in the first place. If the problem is due to lack of access to /dev/kvm,
qemu tells you about that on stderr.
So far, you haven't provided any of:
- qemu version
- qemu command line
- messages generated by qemu
And for this issue, please also provide output of
info kvm
from qemu monitor. If kvm is enabled, it should tell you just that --
"enabled". If not, it'll tell you "disabled" and this means that your guest is
running in full emulation mode.
Without that, this bugreport is not very useful. Especially having in mind
that this setup works for lots of other people just fine.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-02-10 9:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 8:03 [Bug 42755] New: KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane bugzilla-daemon
2012-02-10 8:06 ` [Bug 42755] " bugzilla-daemon
2012-02-10 9:18 ` bugzilla-daemon [this message]
2012-02-10 9:36 ` bugzilla-daemon
2012-02-11 10:50 ` bugzilla-daemon
2012-02-12 8:27 ` bugzilla-daemon
2012-02-12 9:52 ` bugzilla-daemon
2012-02-12 10:10 ` bugzilla-daemon
2012-02-12 10:13 ` bugzilla-daemon
2012-02-12 10:16 ` bugzilla-daemon
2012-02-12 10:16 ` bugzilla-daemon
2012-02-12 10:18 ` bugzilla-daemon
2012-02-12 10:21 ` bugzilla-daemon
2012-02-12 10:30 ` bugzilla-daemon
2012-02-12 10:40 ` bugzilla-daemon
2012-02-12 10:41 ` bugzilla-daemon
2012-02-12 10:49 ` bugzilla-daemon
2012-02-12 14:49 ` bugzilla-daemon
2012-02-12 14:55 ` bugzilla-daemon
2012-02-12 15:09 ` bugzilla-daemon
2012-02-12 16:14 ` bugzilla-daemon
2012-02-13 8:53 ` bugzilla-daemon
2012-02-13 13:19 ` bugzilla-daemon
2012-02-13 13:30 ` bugzilla-daemon
2012-02-13 13:43 ` bugzilla-daemon
2012-02-13 14:14 ` bugzilla-daemon
2012-02-13 14:24 ` bugzilla-daemon
2012-02-13 14:37 ` bugzilla-daemon
2012-02-14 14:47 ` bugzilla-daemon
2012-02-15 7:49 ` bugzilla-daemon
2012-02-15 9:28 ` bugzilla-daemon
2012-02-21 8:55 ` bugzilla-daemon
2012-02-21 9:10 ` bugzilla-daemon
2012-02-21 11:53 ` bugzilla-daemon
2012-02-21 12:45 ` bugzilla-daemon
2012-02-26 9:53 ` bugzilla-daemon
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=201202100918.q1A9IaX2024632@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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.