> On 15 Feb 2018, at 15:58, John Taylor <[email protected]> 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 somehow confirm it was really a 3.6 VM and it stopped working in 4.2? The exact steps are important, unfortunately. > Tracing it out it showed that the vm libvirt xml was begin set to > headless. do you at least recall what cluster level version it was when it stopped working? The VM definition should have been changed to VGA when you move the VM from 3.6 cluster to a 4.0+ > I tried different settings but the only thing that seemed > to work was to set them to headless, then reopen config and set them > to something else. > > -John > > On Thu, Feb 15, 2018 at 8:48 AM, <[email protected]> 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 still >> disabled. >> >> Is there a way to know why is that, and how to solve it? >> >> I'm attaching a screenshot. >> >> Thanks. >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >> > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
