Description of problem: The documentation for ovirt-vmconsole lacks some core details to functional usage. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/virtual_machine_management_guide/#Opening_a_Serial_Console_to_a_Virtual_Machine 1. There is no mention that the guest must be configured to use serial console, which for RHEL involves modifying grub per KCS: https://access.redhat.com/articles/7212#config7 2. The example in keygen command should be more generic and not reflect specific use, especially since the instructions already refer to a generic user. Replace with: ~~~ # ssh-keygen -t rsa -b 2048 -C "your_rhv_user_here" -f .ssh/serialconsolekey ~~~ 3. The ssh command should also make note that you may need to point to the key, e.g. currently the docs say: ~~~ # ssh -t -p 2222 ovirt-vmconsole@MANAGER_IP ~~~ I had to do this: ~~~ # ssh -t -p 2222 ovirt-vmconsole@MANAGER_IP -i .ssh/serialconsolekey ~~~ 4. The command list can be used to gather a list of VM's and ID's if needed: ~~~ # ssh -t -p 2222 ovirt-vmconsole@MANAGER_IP -i .ssh/serialconsolekey list 5. To terminate a session, use "<Any Key>~ ." sequence.
I am also wondering why we are saying MANAGER_IP, if in other guides we request having DNS and refer to manager by FQDN? Just for consistency. But this is not really a big deal.
Can you set the right milestone for this?
Published document: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/virtual_machine_management_guide/index#Opening_a_Serial_Console_to_a_Virtual_Machine