#5739 Enable Nested Virt for QA Virthosts
Closed: Fixed 7 years ago Opened 7 years ago by tflink.

I'd like to have nested virt enabled for the following hosts:

  • qa10.qa
  • qa11.qa
  • qa12.qa
  • qa13.qa

Rebooting qa11.qa is not a problem but we'd prefer to schedule downtime for any of the other hosts.


Fixed in ansible commit a73ef401bf30cf0ba33cc44f39af689336d1b6a3

They will need to be rebooted for it to take effect.

:running_shirt_with_sash:

@kevin changed the status to Closed

7 years ago

So I replayed taskotron-client-hosts.yml -l taskotron-dev-client-hosts to make sure the ansible change was deployed and rebooted qa11.qa but still got:

[mkrizek@qa11 ~][PROD]$ cat /sys/module/kvm_intel/parameters/nested
N

Did I miss something?

So, that variable is applied/used in the 'virthost' role.

The new taskotron-client-hosts.yml playbook doesn't include that role so it's not taking effect.

So, two options:

  • include the virthost role in that playbook (but not sure what else it might change for them).

or

  • include the small snippet from the virthost role into a role that is part of that playbook. Basically it just installs a kvm_intel.conf to /etc/modprobe.d/kvm_intel.conf and that has in it just "options kvm_intel nested=1"

Login to comment on this ticket.

Metadata