Description of problem:
Direct kernel/initrd booting for VMs is supported by libvirt/qemu, and was added to oVirt in the past. However, this feature is not utilized by end users, and the backend support depends on directly moving these files through a mechanism which is not data domains.
Rather than rewriting to use data domains (similar to the existing ISO bugs), it's better to remove it from the following:
Any ansible code which may invoke it
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
This makes accessing the the boot options (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-anaconda-boot-options) impossible.
What is the rationale of removing this? "this feature is not utilized by end users"?!
We actually did intend to use the kernel_params of the Ansible ovirt_vm module to initiate a kickstart installation process of a guest VM. Now that support is removed, we're left without a visible alternative.
Are there remaining alternatives to controlling boot options via Ansible (e.g. ovirt_vm) or the REST API now?
Well, the alternatives are:
* PXE installation
* embed a kickstart onto the ISO
* Provision with Foreman
* Make/seal a template out of a VM
* Configuration of a pre-built image with cloud-init
Are there any required boot options outside of inst.ks?
What would be the reproduction steps?
Open the runonce dialog and VM boot settings and see that the option is not there (it is present in 4.3)