<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 14, 2018 at 1:47 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
the vnc device is there by default (I copied it out of my own hosted<br>
engine instance), I do not know why it was missing in your case.<br></blockquote><div><br></div><div>graphical_console parameter has been introduced in ovirt_vms ansible module just since ansible 2.5.</div><div><a href="http://docs.ansible.com/ansible/latest/modules/ovirt_vms_module.html#ovirt-vms">http://docs.ansible.com/ansible/latest/modules/ovirt_vms_module.html#ovirt-vms</a></div><div><br></div><div>Anso so we have to consume it as well.</div><div><br></div><div>I just opened <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1567772">https://bugzilla.redhat.com/show_bug.cgi?id=1567772</a></div><div>to track it.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Best regards<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Martin Sivak<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
On Fri, Apr 13, 2018 at 5:13 PM, Thomas Klute <<a href="mailto:klute@ingenit.com">klute@ingenit.com</a>> wrote:<br>
> Dear Martin,<br>
><br>
> yes, that worked. Thank you so much!!<br>
> We were able to see that the latest kernel update failed and did not<br>
> create the initramfs file and thus the boot process failed with a kernel<br>
> panic.<br>
><br>
> Debugging this problem took us many hours... It felt so complicated to<br>
> connect a vnc to this vm - compared to a bare metal setup with display<br>
> and keyboard.<br>
> Wouldn't it be a good idea to have the vnc device in the config by default?<br>
><br>
> Best regards,<br>
> Thomas<br>
><br>
>> You need to be in global maintenance, but I think you already know that.<br>
>> Then try updating the vm.conf like you already did and add this line:<br>
>><br>
>> devices={device:vnc,type:<wbr>graphics,deviceId:f1d0394e-<wbr>b077-4ea6-99e5-b9b6b8fe073c,<wbr>address:None}<br>
>><br>
>> Then restart the VM using hosted-engine commands and try the VNC approach again.<br>
>><br>
>> Best regards<br>
>><br>
>> Martin Sivak<br>
>><br>
>> On Fri, Apr 13, 2018 at 2:35 PM, Thomas Klute <<a href="mailto:klute@ingenit.com">klute@ingenit.com</a>> wrote:<br>
>>> Dear Martin,<br>
>>><br>
>>> thanks for the feedback.<br>
>>> We already read this and tried it.<br>
>>> It seems to me that the graphics device was removed from the hosted<br>
>>> engine by some ovirt release.<br>
>>><br>
>>> If I try to set a console password I see this message:<br>
>>><br>
>>> hosted-engine --add-console-password<br>
>>> Enter password:<br>
>>> no graphics devices configured<br>
>>><br>
>>> Furthermore, there is nothing listening on port 5900 after that.<br>
>>> The HostedEngine qemu process shows a " -display none " as parameter and<br>
>>> I have no idea where this can be changed.<br>
>>><br>
>>> I already created a /var/run/ovirt-hosted-engine-<wbr>ha/vm-custom.conf<br>
>>> containing:<br>
>>> display=vnc<br>
>>> kvmEnable=true<br>
>>><br>
>>> But nothing changed.<br>
>>> I also edited the HostedEngine VM config using virsh and added a vnc<br>
>>> display:<br>
>>> /usr/bin/virsh -c<br>
>>> qemu:///system?authfile=/etc/<wbr>ovirt-hosted-engine/virsh_<wbr>auth.conf edit<br>
>>> HostedEngine<br>
>>><br>
>>> <graphics type='vnc' port='12355' autoport='no' listen='0.0.0.0'><br>
>>> <listen type='address' address='0.0.0.0'/><br>
>>> </graphics><br>
>>> <video><br>
>>> <model type='qxl' ram='65536' vram='65536' vgamem='16384'<br>
>>> heads='1' primary='yes'/><br>
>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x07'<br>
>>> function='0x0'/><br>
>>> </video><br>
>>><br>
>>> But there is still "display none" passed as command line parameter to<br>
>>> qemu and thus, I suppose, there's no display.<br>
>>><br>
>>> Any help is appreciated, thanks,<br>
>>> Thomas<br>
>>><br>
>>><br>
>>>> Hi,<br>
>>>><br>
>>>> the serial console will show output if the kernel knows to use it.<br>
>>>><br>
>>>> The VNC approach is also possible and I believe we already have a<br>
>>>> graphical device present. What you are looking for is probably this<br>
>>>> (VNC method is described there):<br>
>>>> <a href="https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems" rel="noreferrer" target="_blank">https://www.ovirt.org/<wbr>documentation/how-to/hosted-<wbr>engine/#handle-engine-vm-boot-<wbr>problems</a><br>
>>>><br>
>>>> Best regards<br>
>>>><br>
>>>> --<br>
>>>> Martin Sivak<br>
>>>> SLA / oVirt<br>
>>>><br>
>>>> On Fri, Apr 13, 2018 at 11:26 AM, Thomas Klute <<a href="mailto:klute@ingenit.com">klute@ingenit.com</a>> wrote:<br>
>>>>> Dear oVirt Team,<br>
>>>>><br>
>>>>> after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't<br>
>>>>> come up anymore.<br>
>>>>> The qemu-kvm process is there but we're unable to access the VM using<br>
>>>>> - the serial console (simply does not show anything, does not react to<br>
>>>>> characters typed)<br>
>>>>> - VNC / Spice because the hosted engine vm.conf does not contain any<br>
>>>>> graphics device.<br>
>>>>><br>
>>>>> Before trying to reinstall, we'd like to recover and debug what is going on.<br>
>>>>> We mounted a Centos7 install .iso and started the VM using<br>
>>>>> hosted-engine --vm-start<br>
>>>>> --vm-conf=/var/run/ovirt-<wbr>hosted-engine-ha/vm-custom.<wbr>conf<br>
>>>>> But we still have to problem, that the serial console does not show<br>
>>>>> anything and there is no way to connect using VNC.<br>
>>>>><br>
>>>>> So, what is the recommended way to move forward in such situation?<br>
>>>>> IMHO the classical way would be to add a graphics device and connect via<br>
>>>>> VNC?<br>
>>>>> I did not use the serial console much, up to now. Should the serial<br>
>>>>> console show any output during boot?<br>
>>>>><br>
>>>>> Thanks for your help,<br>
>>>>> Thomas<br>
>>>>><br>
>>>>> --<br>
>>>>> ______________________________<wbr>______________________________<wbr>____________<br>
>>>>><br>
>>>>> Dipl.-Inform. Thomas Klute <a href="mailto:klute@ingenit.com">klute@ingenit.com</a><br>
>>>>> Geschäftsführer / CEO<br>
>>>>> ------------------------------<wbr>------------------------------<wbr>----------<br>
>>>>> ingenit GmbH & Co. KG Tel. +49 (0)231 58 698-120<br>
>>>>> Emil-Figge-Strasse 76-80 Fax. +49 (0)231 58 698-121<br>
>>>>> D-44227 Dortmund <a href="http://www.ingenit.com" rel="noreferrer" target="_blank">www.ingenit.com</a><br>
>>>>><br>
>>>>> Registergericht: Amtsgericht Dortmund, HRA 13 914<br>
>>>>> Gesellschafter : Thomas Klute, Marc-Christian Schröer<br>
>>>>> ______________________________<wbr>______________________________<wbr>____________<br>
>>>>><br>
>>>>> ______________________________<wbr>_________________<br>
>>>>> Users mailing list<br>
>>>>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
>>>>> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
>>> Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit<br>
>>> gerne zur Verfügung.<br>
>>><br>
>>> Mit Grüßen aus Dortmund,<br>
>>> Thomas Klute<br>
>>><br>
>>> --<br>
>>> ______________________________<wbr>______________________________<wbr>____________<br>
>>><br>
>>> Dipl.-Inform. Thomas Klute <a href="mailto:klute@ingenit.com">klute@ingenit.com</a><br>
>>> Geschäftsführer / CEO<br>
>>> ------------------------------<wbr>------------------------------<wbr>----------<br>
>>> ingenit GmbH & Co. KG Tel. +49 (0)231 58 698-120<br>
>>> Emil-Figge-Strasse 76-80 Fax. +49 (0)231 58 698-121<br>
>>> D-44227 Dortmund <a href="http://www.ingenit.com" rel="noreferrer" target="_blank">www.ingenit.com</a><br>
>>><br>
>>> Registergericht: Amtsgericht Dortmund, HRA 13 914<br>
>>> Gesellschafter : Thomas Klute, Marc-Christian Schröer<br>
>>> ______________________________<wbr>______________________________<wbr>____________<br>
>>><br>
>><br>
><br>
> Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit<br>
> gerne zur Verfügung.<br>
><br>
> Mit Grüßen aus Dortmund,<br>
> Thomas Klute<br>
><br>
> --<br>
> ______________________________<wbr>______________________________<wbr>____________<br>
><br>
> Dipl.-Inform. Thomas Klute <a href="mailto:klute@ingenit.com">klute@ingenit.com</a><br>
> Geschäftsführer / CEO<br>
> ------------------------------<wbr>------------------------------<wbr>----------<br>
> ingenit GmbH & Co. KG Tel. +49 (0)231 58 698-120<br>
> Emil-Figge-Strasse 76-80 Fax. +49 (0)231 58 698-121<br>
> D-44227 Dortmund <a href="http://www.ingenit.com" rel="noreferrer" target="_blank">www.ingenit.com</a><br>
><br>
> Registergericht: Amtsgericht Dortmund, HRA 13 914<br>
> Gesellschafter : Thomas Klute, Marc-Christian Schröer<br>
> ______________________________<wbr>______________________________<wbr>____________<br>
><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>