From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53361] Wrong CPUID data returned by KVM
Date: Mon, 04 Aug 2014 16:55:19 +0000 [thread overview]
Message-ID: <bug-53361-28872-a1stueWZa5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-53361-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=53361
Chris Harrington <ironiridis@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ironiridis@gmail.com
--- Comment #1 from Chris Harrington <ironiridis@gmail.com> ---
Looks like the QEMU folks had a relevant change on this bug:
https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg04140.html
Could you retest?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-04 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 20:22 [Bug 53361] New: Wrong CPUID data returned by KVM bugzilla-daemon
2014-08-04 16:55 ` bugzilla-daemon [this message]
2014-08-09 2:10 ` [Bug 53361] " bugzilla-daemon
2019-04-08 15:02 ` 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-53361-28872-a1stueWZa5@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).