Bug 1724159

There are several possible approaches to creating a VM with a bootable OS.

* Creating a Cloned Virtual Machine Based on a Template
* Create a new VM with a local boot disk managed by RHV that contains the OS and application binaries. (recommended)
* Create a VM. Then use Run Once to boot the VM from an ISO file in the ISO library (Use the Attach CD option with the ISO file) or data domain.

One more approach to include:
* Install OS by booting from PXE.

Customers occasionally create a VM without completing all of the required steps. As a result, when they start the VM, they may get the following error:

"Booting from Hard Disk . . .
Boot failed: not a bootable disk
No bootable device."


In particular, we could provide more detail and/or an example of how to specify the installation media and bootable disk. The current documentation on this subject [1] does not provide enough information: 

```You can accept the default settings for all other fields, or change them if required. For more details on all fields in the New Virtual Machine window, see Section A.1, “Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows”.```

We should also include a `.Troubleshooting` section that specifically mentions "Boot failed: not a bootable disk - No bootable device" so users who google "RHV" plus this error message come straight to the troubleshooting topic.


[1.] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Starting_the_Virtual_Machine

Didn't make it in for 4.4.3 and wasn't re-planned for 4.4.4.
Re-setting target milestone for re-evaluation.

- Made general updates to various procedures mentioned in the above comments in order to try and improve clarity and readability.
- Added a short Troubleshooting section under sec 2.2.1 Starting the Virtual Machine


https://jenkins.dxp.redhat.com/job/CCS/job/ccs-mr-preview/358/artifact/doc-Virtual_Machine_Management_Guide/preview/index.html#Powering_on_a_virtual_machine


merge request: 

https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/-/merge_requests/1992

Hi Arik, 
can you review this? or recommend someone who can look at it?


https://jenkins.dxp.redhat.com/job/CCS/job/ccs-mr-preview/358/artifact/doc-Virtual_Machine_Management_Guide/preview/index.html#Powering_on_a_virtual_machine


merge request: 

https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/-/merge_requests/1992

Hi Eli,

One thing I've noticed that is unrelated to your changes but should change is:
"but you cannot switch between chipsets after installing an operating system"
Users can actually change the VMs that are set with i440fx to q35 (by updating the cluster)
But again, that's unrelated to the current changes and can be done separately.

And about the changes in the merge request:

1. The link in step 9 of "2.1. Creating a virtual machine" is incorrect - it should point to new/edit *VM* rather than to new/edit *virtual disk*

2. There's something confusing in the structure - the "create" part says that operating system must be installed and later in the "start" section we say that alternatively one can provision the VM from template or a pre-installed disk.
How about saying in the "create" section that the VM should either use a pre-installed image, either by provisioning it from a template or by attached a pre-installed disk to it, or the operating system needs to be installed from either PXE or ISO

3. The "To solve this problem:" part seems to assume there are several disks attached to the VM and the wrong disk is set as bootable.
Maybe we can be more general here to cover more cases and say that in case of this error, one should make sure that "hard disk" is selected in boot sequence and the disk that the VM should boot from is set as bootable