All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203543] Starting with kernel 5.1.0-rc6,  kvm_intel can no longer be loaded in nested kvm/guests
Date: Wed, 08 May 2019 12:46:19 +0000	[thread overview]
Message-ID: <bug-203543-28872-C5N2oZe9SU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203543-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=203543

--- Comment #4 from David Hill (hilld@binarystorm.net) ---
I didn't do anything fancy... only enabled nested kvm with:


[root@wolfe modprobe.d]# cat kvm.conf 
###
### This configuration file was provided by the qemu package.
### Feel free to update as needed.
###

###
### Set these options to enable nested virtualization
###

#options kvm_intel nested=1
#options kvm_amd nested=1
options kvm_intel nested=1

and exposed the flag in the libvirtd kvm definition.   Here is the hardware
description of the VM:

  <vcpu placement='static'>4</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-4.0'>hvm</type>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
    <vmport state='off'/>
  </features>
  <cpu mode='custom' match='exact' check='partial'>
    <model fallback='allow'>IvyBridge-IBRS</model>
    <feature policy='require' name='vmx'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-05-08 12:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 20:45 [Bug 203543] New: Starting with kernel 5.1.0-rc6, kvm_intel can no longer be loaded in nested kvm/guests bugzilla-daemon
2019-05-07 23:23 ` Liran Alon
2019-05-07 23:29 ` [Bug 203543] " bugzilla-daemon
2019-05-08  4:08 ` bugzilla-daemon
2019-05-08 12:44 ` bugzilla-daemon
2019-05-08 12:46 ` bugzilla-daemon [this message]
2019-05-08 13:51 ` bugzilla-daemon
2019-05-08 16:00   ` Liran Alon
2019-05-08 16:21     ` Sean Christopherson
2019-05-08 16:10 ` bugzilla-daemon
2019-05-08 16:29 ` bugzilla-daemon
2019-05-08 22:14 ` bugzilla-daemon
2019-05-21 12:57   ` David Hill
2019-05-21 12:57 ` bugzilla-daemon
2019-05-21 13:37 ` bugzilla-daemon
2019-05-21 14:11   ` Sean Christopherson
2019-05-21 14:17     ` Sean Christopherson
2019-05-21 14:17 ` bugzilla-daemon
2019-05-21 14:18 ` bugzilla-daemon
2019-05-21 16:02 ` bugzilla-daemon
2019-05-21 18:06 ` bugzilla-daemon
2019-05-26 12:11   ` David Hill
2019-05-26 12:11 ` bugzilla-daemon
2019-12-01 18:07 ` bugzilla-daemon
2019-12-01 21:49 ` bugzilla-daemon
2019-12-02  3:20 ` bugzilla-daemon
2019-12-02  3:42 ` bugzilla-daemon
2019-12-02  4:15 ` bugzilla-daemon
2019-12-02  4:27 ` bugzilla-daemon
2019-12-02  4:44 ` 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-203543-28872-C5N2oZe9SU@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.