Bug 1609355 - [Docs] VM Guide - ovirt-vmconsole
Summary: [Docs] VM Guide - ovirt-vmconsole
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.2.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.6
: ---
Assignee: Avital Pinnick
QA Contact: Tahlia Richardson
URL:
Whiteboard: docs-accepted
Depends On:
Blocks: 902971
TreeView+ depends on / blocked
 
Reported: 2018-07-27 17:36 UTC by amashah
Modified: 2021-09-09 15:14 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 07:32:24 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1608733 0 urgent CLOSED Serial console connection to HE returns "ERROR: No pty support, please enable at client side" and fails. 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker RHV-43569 0 None None None 2021-09-09 15:14:56 UTC

Internal Links: 1608733

Description amashah 2018-07-27 17:36:22 UTC
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.

Comment 1 Marina Kalinin 2018-07-27 17:40:55 UTC
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.

Comment 8 Yaniv Lavi 2018-09-02 09:53:27 UTC
Can you set the right milestone for this?


Note You need to log in before you can comment on or make changes to this bug.