From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 115451] New: memset hang on pci device memory using kvm
Date: Tue, 29 Mar 2016 09:59:44 +0000 [thread overview]
Message-ID: <bug-115451-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=115451
Bug ID: 115451
Summary: memset hang on pci device memory using kvm
Product: Virtualization
Version: unspecified
Kernel Version: RHEL - 2.6.18-308.el5
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: gauravs.2010@gmail.com
Regression: No
i have host x86 based rhel system [kernel version - 2.6.18-308.el5]. On this I
am trying to boot up a debian amd64 image using qemu with kvm.
On my virtual os i have a pcimem application, through which I R/W any
configured memory on pci devices.
Issue is whenever i try to use memset in excess of 156 bytes in my pcimem
application to configure any pci device memory, call to memset hangs.
However, memcpy work fine in all scenarios.
memset works fine if boot my virtual os without kvm.
my kvm version is :
$/usr/libexec/qemu-kvm --help
QEMU PC emulator version 0.9.1 (kvm-83-maint-snapshot-20090205), Copyright (c)
2003-2008 Fabrice Bellard
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-03-29 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 9:59 bugzilla-daemon [this message]
2016-03-29 16:34 ` [Bug 115451] memset hang on pci device memory using kvm bugzilla-daemon
2016-04-06 4:48 ` bugzilla-daemon
2016-04-06 5:27 ` bugzilla-daemon
2016-04-06 8:27 ` bugzilla-daemon
2016-04-06 8:32 ` bugzilla-daemon
2016-04-06 9:30 ` bugzilla-daemon
2016-04-06 9:40 ` bugzilla-daemon
2016-04-06 9:41 ` 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-115451-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).