From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 117301] Could not insert kvm_intel on dual Xeon X5355
Date: Wed, 27 Apr 2016 11:55:00 +0000 [thread overview]
Message-ID: <bug-117301-28872-i0LxXwJKFt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-117301-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=117301
piotr.pejas@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|3.10.0-327.13.1.el7.x86_64 |3.10.0-327.13.1.el7.x86_64,
| |4.5.2-1.el7.elrepo.x86_64
--- Comment #1 from piotr.pejas@gmail.com ---
Same result on latest kernel:
# uname -a
Linux XXX 4.5.2-1.el7.elrepo.x86_64 #1 SMP Wed Apr 20 15:17:10 EDT 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-04-27 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:05 [Bug 117301] New: Could not insert kvm_intel on dual Xeon X5355 bugzilla-daemon
2016-04-27 11:55 ` bugzilla-daemon [this message]
2016-04-28 16:51 ` [Bug 117301] " bugzilla-daemon
2016-04-29 13:30 ` 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-117301-28872-i0LxXwJKFt@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).