From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 198547] New: Nested kvm fails on amd
Date: Mon, 22 Jan 2018 19:01:21 +0000 [thread overview]
Message-ID: <bug-198547-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=198547
Bug ID: 198547
Summary: Nested kvm fails on amd
Product: Virtualization
Version: unspecified
Kernel Version: 4.14.14-1-ARCH
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: kieran@kcolford.com
Regression: No
Created attachment 273791
--> https://bugzilla.kernel.org/attachment.cgi?id=273791&action=edit
dmesg output of archlinux guest
I'm running fedora host with archlinux guest and trying to run another VM
inside the archlinux guest. On the fedora host, `cat
/sys/module/kvm_amd/parameters/nested` outputs `1`. This error only happens
when running qemu with `-enable-kvm` flag, without the flag it works fine (but
slow as expected).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2018-01-22 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 19:01 bugzilla-daemon [this message]
2018-01-22 19:02 ` [Bug 198547] Nested kvm fails on amd 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-198547-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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.