From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42755] New: KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
Date: Fri, 10 Feb 2012 08:03:43 GMT [thread overview]
Message-ID: <bug-42755-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42755
Summary: KVM is being extremely slow on AMD Athlon64 4000+ Dual
Core 2.1GHz Brisbane
Product: Virtualization
Version: unspecified
Kernel Version: 3.2.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: sandikata@yandex.ru
Regression: No
Hello.
Kvm seems to be broken on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane. A
kernel build takes over
2 hours, compared to 15 minutes on the host. I'm running with virtio
for storage, and this does not seem to be related to IO. A simple test
with dd also demonstrates that the problem is cpu-ralated:
Host test:
dd if=/dev/zero of=/dev/null bs=1k count=8M
8388608+0 записей считано (read)
8388608+0 записей написано (write)
скопировано (copyed) 8589934592 байта (8,6 GB), 7,04456 c, 1,2 GB/c
This also does not seem to be a cpu bug, as both VirtualBox and VMware
work fine.
Vmware/Virtualbox test:
dd if=/dev/zero of=/dev/null bs=1k count=8M
8388608+0 записей считано (read)
8388608+0 записей написано (write)
скопировано (copyed) 8589934592 байта (8,6 GB), 5,02745 c, 1,7 GB/c
I've tried different kernels on host, between 2.6.22 and current git,
with the same results. The guest is running Gentoo Hardened kernel 3.2.2
, but I could try with a an other distro and a vanilla kernel
if required.
My kvm version is kvm 1.0
Help would be much appreciated.
--
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 reply other threads:[~2012-02-10 8:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 8:03 bugzilla-daemon [this message]
2012-02-10 8:06 ` [Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane bugzilla-daemon
2012-02-10 9:18 ` bugzilla-daemon
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=bug-42755-28872@https.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.