Bug 1425076 - A VM with rhel68 OS that is set to be headless is not accessible
Summary: A VM with rhel68 OS that is set to be headless is not accessible
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Documentation
Version: 4.1.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-20 14:14 UTC by Shira Maximov
Modified: 2017-03-13 11:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 07:30:17 UTC
oVirt Team: Virt
Embargoed:
tjelinek: planning_ack?
tjelinek: devel_ack?
tjelinek: testing_ack?


Attachments (Terms of Use)
qemu log (7.41 KB, text/plain)
2017-02-20 14:14 UTC, Shira Maximov
no flags Details
VM /var/log/messages (903.39 KB, text/plain)
2017-02-21 09:32 UTC, Shira Maximov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1381184 0 medium CLOSED [RFE] allow starting VMs without graphical console (headless) 2021-02-22 00:41:40 UTC

Internal Links: 1381184

Description Shira Maximov 2017-02-20 14:14:57 UTC
Created attachment 1255699 [details]
qemu log

Description of problem:
A VM with rhel68 OS that is set to be headless doesn't start

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.1.2-0.1.el7



How reproducible:
100%

Steps to Reproduce:
1. Create VM with RHEL68 (from template / PXE) with non-headless and with guest agent installed
2. make sure that the VM is up and running and remember the VM ip.
3. power off the VM 
4. set the VM to be headless (console-> headless mode)
5. start the VM
6. try to connect the VM with ssh and also ping- Doesn't work.
   
   try to connect to the VM with Serial Console- Doesn't work:
   debug1: client_input_channel_req: channel 0 rtype keepalive reply 

Actual results:
The VM is running on the engine, but is not accessible 

Expected results:
The VM should be accessible

Additional info:

Comment 1 Michal Skrivanek 2017-02-21 06:11:17 UTC
Bit more ligs are needed. ssh debug logs from your client. system logs from the guest containing the start when headless

Comment 2 Shira Maximov 2017-02-21 09:32:35 UTC
Created attachment 1256035 [details]
VM /var/log/messages

Comment 3 Michal Skrivanek 2017-02-21 10:45:18 UTC
as I saw in email conversation it was eventually working, you just need to correctly configure and use the serial console

Comment 4 Shira Maximov 2017-02-21 19:41:17 UTC
which mail conversions? this is a different issue, 
the problem in serial console is not connected to this bug

Comment 5 Tomas Jelinek 2017-03-01 12:03:23 UTC
After some digging into this issue in the Shira's environment I found that the problem was in a grub configuration which needs to be set to console mode.

This deserves some documentation - turning into documentation bug.

Comment 6 Yaniv Lavi 2017-03-02 13:16:17 UTC
Please move it to a github issue on the feature page.

Comment 7 Tomas Jelinek 2017-03-08 07:30:17 UTC
Moved to upstream: https://github.com/oVirt/ovirt-site/issues/838


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