<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 19 Feb 2018, at 23:36, Jason Keltz <<a href="mailto:jas@cse.yorku.ca" class="">jas@cse.yorku.ca</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Hi Michal,</p><p class="">On 2/15/2018 12:05 PM, Michal Skrivanek wrote:
</p>
<blockquote cite="mid:2EA3B6C6-C3E8-45D8-8ED4-4DF0AE97D279@redhat.com" type="cite" class="">
<blockquote type="cite" class="">
<pre wrap="" class="">On 15 Feb 2018, at 16:37, Jason Keltz <a class="moz-txt-link-rfc2396E" href="mailto:jas@cse.yorku.ca"><jas@cse.yorku.ca></a> wrote:
On 02/15/2018 08:48 AM, <a class="moz-txt-link-abbreviated" href="mailto:nicolas@devels.es">nicolas@devels.es</a> wrote:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Hi,
We upgraded one of our infrastructures to 4.2.0 recently and since then some of our machines have the "Console" button greyed-out in the Admin UI, like they were disabled.
I changed their compatibility to 4.2 but with no luck, as they're still disabled.
Is there a way to know why is that, and how to solve it?
I'm attaching a screenshot.
</pre>
</blockquote>
<pre wrap="" class="">Hi Nicolas.
I had the same problem with most of my VMs after the upgrade from 4.1 to 4.2.
See bugzilla here: <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1528868">https://bugzilla.redhat.com/show_bug.cgi?id=1528868</a>
(which admittedly was a mesh of a bunch of different issues that occurred)
</pre>
</blockquote>
<pre wrap="" class="">yeah, that’s not a good idea to mix more issues:)
Seems <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1528868#c26">https://bugzilla.redhat.com/show_bug.cgi?id=1528868#c26</a> is the last one relevant to the grayed out console problem in this email thread.
it’s also possible to check "VM Devices” subtab and list the graphical devices. If this is the same problem as from Nicolas then it would list cirrus and it would be great if you can confirm the conditionas are similar (i.e. originally a 3.6 VM)</pre>
</blockquote>
I believe it was originally a 3.6 VM. Is there anywhere I can
verify this info? If not, it would be helpful if oVirt kept track of
the version that created the VM for cases just like this.<br class=""></div></div></blockquote><div><br class=""></div>Hi,</div><div>well, we keep the date and who did that, but we can’t really keep all the logs forever. Well, you can if you archive them somewhere, but I guess that’s impractical for such a long time:-D</div><div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
VM Device subtab: (no Cirrus)</div></div></blockquote><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<span id="cid:part1.802471EC.76DEFB09@cse.yorku.ca"><eadpakjggeififdb.png></span><br class=""></div></div></blockquote><div><br class=""></div>so this is a screenshot from VM where the button is grayed out when you start it? </div><div>Hm..it doesn’t look wrong.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<blockquote cite="mid:2EA3B6C6-C3E8-45D8-8ED4-4DF0AE97D279@redhat.com" type="cite" class="">
<pre wrap="" class="">And then - if possible - describe some history of what happened. When was the VM created, when was cluster updated, when the system was upgraded and to what versions.
</pre>
</blockquote>
All I know is that everything was working fine, then I updated to
4.2, updated cluster version, and then most of my consoles were not
available. I can't remember if this happened before the cluster
upgrade or not. I suspect it was most and not all VMs since some of
them had been created later than 3.6, and this was an older one. I
only have this one VM left in this state because I had deleted the
other VMs and recreated them one at a time... <br class="">
I will wait to see if you want me to try Vineet's solution of making
it headless,<br class=""></div></div></blockquote><div><br class=""></div><div>Thanks.</div><div>Can you get engine.log and vdsm log when you attempt to start that VM ? just the relevant part is enough.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">michal</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<blockquote type="cite" class="">The before bringing it back up, unchecked
headless in the VM<br class="">
<br class="">
<div class="gmail_default" style="font-family:monospace,monospace">We
then had to do a Run-Once which failed<br class="">
</div>
<div class="gmail_default" style="font-family:monospace,monospace">Then
did a normal Run.<br class="">
<br class="">
</div>
<div class="gmail_default" style="font-family:monospace,monospace">Console
was available, and all hardware came back fine.<br class="">
<br class="">
</div>
</blockquote>
... but I won't try that yet in case you need additional information
from the VM first.<br class="">
<br class="">
Jason.<br class="">
</div>
_______________________________________________<br class="">Users mailing list<br class=""><a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">http://lists.ovirt.org/mailman/listinfo/users<br class=""></div></blockquote></div><br class=""></body></html>