Re: [ovirt-users] Console button greyed out (4.2)

On 02/20/2018 12:17 PM, Michal Skrivanek wrote: On 19 Feb 2018, at 23:36, Jason Keltz > wrote: Hi Michal, On 2/15/2018 12:05 PM, Michal Skrivanek wrote: On 15 Feb 2018, at 16:37, Jason Keltz wrote: On 02/15/2018 08:48 AM,nico...@devels.es wrote: Hi, We upgraded

Re: [ovirt-users] Console button greyed out (4.2)

> On 19 Feb 2018, at 23:36, Jason Keltz wrote: > > Hi Michal, > > On 2/15/2018 12:05 PM, Michal Skrivanek wrote: > >>> On 15 Feb 2018, at 16:37, Jason Keltz >>> wrote: >>> >>> On 02/15/2018 08:48 AM, nico...@devels.es wrote: Hi, >>

Re: [ovirt-users] Console button greyed out (4.2)

Hi Michal, On 2/15/2018 12:05 PM, Michal Skrivanek wrote: On 15 Feb 2018, at 16:37, Jason Keltz wrote: On 02/15/2018 08:48 AM, nico...@devels.es wrote: 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 t

Re: [ovirt-users] Console button greyed out (4.2)

Thanks guys, setting the VM to headless and then removing this option seemed to do the trick. Indeed, this VM was created back in 3.6, however it had QXL set in options. Seems that despite this something was not migrated correctly. I think I have more machines in this situation, in case the oV

Re: [ovirt-users] Console button greyed out (4.2)

Hello. Just had the same issue @ 4.1, upgraded to 4.2(.1) Updated cluster compatibility, then, data centre compatibility All VMs lost their hardware (NICs (showed attached but unplugged), disks (status changed to disabled) and console) Our solution was simply to connect the NICs, activate the dis

Re: [ovirt-users] Console button greyed out (4.2)

On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek wrote: > > >> On 15 Feb 2018, at 15:58, John Taylor wrote: >> >> Hi Nicolas, >> I had the same problem and it looked like it was because of some older >> vms (I believe from 3.6) that were configured with console with video >> type of CIRRUS and

Re: [ovirt-users] Console button greyed out (4.2)

> On 15 Feb 2018, at 16:37, Jason Keltz wrote: > > On 02/15/2018 08:48 AM, nico...@devels.es wrote: >> 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. >

Re: [ovirt-users] Console button greyed out (4.2)

> On 15 Feb 2018, at 15:58, John Taylor wrote: > > Hi Nicolas, > I had the same problem and it looked like it was because of some older > vms (I believe from 3.6) that were configured with console with video > type of CIRRUS and protocol VNC. 3.6 had cirrus indeed. That should work. Can you so

Re: [ovirt-users] Console button greyed out (4.2)

On 02/15/2018 08:48 AM, nico...@devels.es wrote: 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

Re: [ovirt-users] Console button greyed out (4.2)

Hi Nicolas, I had the same problem and it looked like it was because of some older vms (I believe from 3.6) that were configured with console with video type of CIRRUS and protocol VNC. Tracing it out it showed that the vm libvirt xml was begin set to headless. I tried different settings but the

[ovirt-users] Console button greyed out (4.2)

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 th