4.8. Configuring Headless Virtual Machines

You can configure a headless virtual machine when it is not necessary to access the machine via a graphical console. This headless machine will run without graphical and video devices. This can be useful in situations where the host has limited resources, or to comply with virtual machine usage requirements such as real-time virtual machines.
Headless virtual machines can be administered via a Serial Console, SSH, or any other service for command line access. Headless mode is applied via the Console tab, which is available from the cluster level when creating or editing virtual machines and machine pools, and when editing templates. It is also available when creating or editing instance types.
If you are creating a new headless virtual machine, you can use the Run Once window to access the virtual machine via a graphical console for the first run only. See Section A.5, “Explanation of Settings in the Run Once Window” for more details.

Prerequisites

  • If you are editing an existing virtual machine, and the Red Hat Virtualization guest agent has not been installed, note the machine's IP prior to selecting Headless Mode.
  • Before running a virtual machine in headless mode, the GRUB configuration for this machine must be set to console mode otherwise the guest operating system's boot process will hang. To set console mode, comment out the spashimage flag in the GRUB menu configuration file:
     #splashimage=(hd0,0)/grub/splash.xpm.gz serial --unit=0 --speed=9600 --parity=no --stop=1 terminal --timeout=2 serial
    

Note

Restart the virtual machine if it is running when selecting the Headless Mode option.

Procedure 4.14. Configuring a Headless Virtual Machine

  1. Click the Virtual Machines tab and select a virtual machine.
  2. Click Edit.
  3. Click the Console tab.
  4. Select Headless Mode. All other fields in the Graphical Console section are disabled.
  5. Optionally, select Enable VirtIO serial console to enable comunicating with the virtual machine via serial console. This is higly recommended.
  6. Reboot the virtual machine if it is running. See Section 6.3, “Rebooting a Virtual Machine”.