openstack/ironic-inspector
Code Issues Proposed changes

Add troubleshooting step for virtual box

Browse Source 
This patch adds a note on how to allow inspector to work on a virtual
box guest. This can be helpful for devs with limited access to test
environments.

Change-Id: I3c23594ad8a66861598057879018e37327999e60
This commit is contained in:
Chris Krelle 2017-01-06 13:47:52 -08:00
parent 46f4019364
commit 74565133b0
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/troubleshooting.rst
View File

@ -131,3 +131,19 @@ On Ubuntu 14.04 this can be done by editing your
``/etc/resolvconf/resolv.conf.d/head`` and adding your nameservers there.
This will ensure they will come up first when ``/etc/resolv.conf``
is regenerated.
Running Inspector in a VirtualBox environment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
By default VirtualBox does not expose a DMI table to the guest. This prevents
ironic-inspector from being able to discover the properties of the a node. In
order to run ironic-inspector on a VirtualBox guest the host must be configured
to expose DMI data inside the guest. To do this run the following command on
the VirtualBox host::
VBoxManage setextradata {NodeName} "VBoxInternal/Devices/pcbios/0/Config/DmiExposeMemoryTable" 1
.. note::
Replace `{NodeName}` with the name of the guest you wish to expose the DMI
table on. This command will need to be run once per host to enable this
functionality.