From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 115451] memset hang on pci device memory using kvm
Date: Wed, 06 Apr 2016 09:30:05 +0000 [thread overview]
Message-ID: <bug-115451-28872-GRV27MmNFD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-115451-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=115451
--- Comment #6 from Gaurav Sharma <gauravs.2010@gmail.com> ---
I am using qemu version 2.2.0 and kvm modules are the default with the host
kernel version [RHEL 5.8], which doesn't seems to be that old to me.
Any data point am i missing ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-04-06 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 9:59 [Bug 115451] New: memset hang on pci device memory using kvm bugzilla-daemon
2016-03-29 16:34 ` [Bug 115451] " 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 [this message]
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-GRV27MmNFD@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).