2.2. Starting the Virtual Machine
2.2.1. Starting a Virtual Machine
Procedure
-
Click
and select a virtual machine with a status of Down. - Click .
The Status of the virtual machine changes to Up, and the operating system installation begins. Open a console to the virtual machine if one does not open automatically.
A virtual machine will not start on a host with an overloaded CPU. By default, a host’s CPU is considered overloaded if it has a load of more than 80% for 5 minutes, but these values can be changed using scheduling policies. See Scheduling Policies in the Administration Guide for more information.
Troubleshooting
Scenario - the virtual machine fails to boot with the following error message:
Boot failed: not a bootable disk - No Bootable device
Possible solutions to this problem:
- Make sure that hard disk is selected in the boot sequence, and the disk that the virtual machine is booting from must be set as Bootable.
- Create a Cloned Virtual Machine Based on a Template.
- Create a new virtual machine with a local boot disk managed by RHV that contains the OS and application binaries.
- Install the OS by booting from the Network (PXE) boot option.
Scenario - the virtual machine on IBM POWER9 fails to boot with the following error message:
qemu-kvm: Requested count cache flush assist capability level not supported by kvm, try appending -machine cap-ccf-assist=off
Default risk level protections can prevent VMs from starting on IBM POWER9. To resolve this issue:
-
Create or edit the
/var/lib/obmc/cfam_overrideson the BMC. Set the firmware risk level to
0:# Control speculative execution mode 0 0x283a 0x00000000 # bits 28:31 are used for init level -- in this case 0 Kernel and User protection (safest, default) 0 0x283F 0x20000000 # Indicate override register is valid
- Reboot the host system for the changes to take affect.
Overriding the risk level can cause unexpected behavior when running virtual machines.
2.2.2. Opening a console to a virtual machine
Use Remote Viewer to connect to a virtual machine.
To allow other users to connect to the VM, make sure you shutdown and restart the virtual machine when you are finished using the console. Alternatively, the administrator can Disable strict user checking to eliminate the need for reboot between users. See Virtual Machine Console Settings Explained for more information.
Procedure
- Install Remote Viewer if it is not already installed. See Installing Console Components.
-
Click
and select a virtual machine. -
Click . By default, the browser prompts you to download a file named
console.vv. When you click to open the file, a console window opens for the virtual machine. You can configure your browser to automatically open these files, such that clicking simply opens the console.
console.vv expires after 120 seconds. If more than 120 seconds elapse between the time the file is downloaded and the time that you open the file, click again.
Additional resources
2.2.3. Opening a Serial Console to a Virtual Machine
You can access a virtual machine’s serial console from the command line instead of opening a console from the Administration Portal or the VM Portal. The serial console is emulated through VirtIO channels, using SSH and key pairs. The Manager acts as a proxy for the connection, provides information about virtual machine placement, and stores the authentication keys. You can add public keys for each user from either the Administration Portal or the VM Portal. You can access serial consoles for only those virtual machines for which you have appropriate permissions.
To access the serial console of a virtual machine, the user must have UserVmManager, SuperUser, or UserInstanceManager permission on that virtual machine. These permissions must be explicitly defined for each user. It is not enough to assign these permissions to Everyone.
The serial console is accessed through TCP port 2222 on the Manager. This port is opened during engine-setup on new installations. To change the port, see ovirt-vmconsole/README.md.
You must configure the following firewall rules to allow a serial console:
The serial console relies on the ovirt-vmconsole package and the ovirt-vmconsole-proxy on the Manager and the ovirt-vmconsole package and the ovirt-vmconsole-host package on the hosts.
These packages are installed by default on new installations. To install the packages on existing installations, reinstall the hosts.
Enabling a Virtual Machine’s Serial Console
On the virtual machine whose serial console you are accessing, add the following lines to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8" GRUB_TERMINAL="console serial" GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
NoteGRUB_CMDLINE_LINUX_DEFAULTapplies this configuration only to the default menu entry. UseGRUB_CMDLINE_LINUXto apply the configuration to all the menu entries.If these lines already exist in /etc/default/grub, update them. Do not duplicate them.
Rebuild /boot/grub2/grub.cfg:
BIOS-based machines:
# grub2-mkconfig -o /boot/grub2/grub.cfg
UEFI-based machines:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
See GRUB 2 over a Serial Console in the Red Hat Enterprise Linux 7 System Administrator’s Guide for details.
On the client machine from which you are accessing the virtual machine serial console, generate an SSH key pair. The Manager supports standard SSH key types, for example, an RSA key:
# ssh-keygen -t rsa -b 2048 -f .ssh/serialconsolekey
This command generates a public key and a private key.
In the Administration Portal, click
or click the user icon on the header bar and click Account Settings to open the Account Settings screen. OR
In the VM Portal, click the Settings icon on the header bar to open the Account Settings screen.
- In the User’s Public Key text field (Administration Portal) or SSH Key field (VM Portal), paste the public key of the client machine that will be used to access the serial console.
-
Click
and select a virtual machine. - Click .
- In the Console tab of the Edit Virtual Machine window, select the Enable VirtIO serial console check box.
Connecting to a Virtual Machine’s Serial Console
On the client machine, connect to the virtual machine’s serial console:
If a single virtual machine is available, this command connects the user to that virtual machine:
# ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN -i .ssh/serialconsolekey Red Hat Enterprise Linux Server release 6.7 (Santiago) Kernel 2.6.32-573.3.1.el6.x86_64 on an x86_64 USER login:
If more than one virtual machine is available, this command lists the available virtual machines and their IDs:
# ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN -i .ssh/serialconsolekey list 1. vm1 [vmid1] 2. vm2 [vmid2] 3. vm3 [vmid3] > 2 Red Hat Enterprise Linux Server release 6.7 (Santiago) Kernel 2.6.32-573.3.1.el6.x86_64 on an x86_64 USER login:
Enter the number of the machine to which you want to connect, and press
Enter.Alternatively, connect directly to a virtual machine using its unique identifier or its name:
# ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN connect --vm-id vmid1
# ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN connect --vm-name vm1
Disconnecting from a Virtual Machine’s Serial Console
Press any key followed by ~ . to close a serial console session.
If the serial console session is disconnected abnormally, a TCP timeout occurs. You will be unable to reconnect to the virtual machine’s serial console until the timeout period expires.
2.2.4. Automatically Connecting to a Virtual Machine
Once you have logged in, you can automatically connect to a single running virtual machine. This can be configured in the VM Portal.
Procedure
- In the Virtual Machines page, click the name of the virtual machine to go to the details view.
- Click the pencil icon beside Console and set Connect automatically to ON.
The next time you log into the VM Portal, if you have only one running virtual machine, you will automatically connect to that machine.
