From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 94971] New: nVMX meta bug
Date: Tue, 17 Mar 2015 03:43:51 +0000 [thread overview]
Message-ID: <bug-94971-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=94971
Bug ID: 94971
Summary: nVMX meta bug
Product: Virtualization
Version: unspecified
Kernel Version: NA
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: bsd@makefile.in
Regression: No
Creating a new Nested Virtualization meta bug to track current Nested
Virtualization issues. I can't edit the old meta bug (bug 53601) due to
permission issues, Nadav suggested to close it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-03-17 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 3:43 bugzilla-daemon [this message]
2015-03-17 3:53 ` [Bug 94971] nVMX meta bug bugzilla-daemon
2015-03-17 9:12 ` bugzilla-daemon
2015-04-08 8:36 ` bugzilla-daemon
2015-04-08 8:57 ` bugzilla-daemon
2015-04-08 8:57 ` bugzilla-daemon
2015-04-08 8:57 ` bugzilla-daemon
2015-04-08 8:58 ` bugzilla-daemon
2015-04-08 9: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-94971-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.