On Jul 14, 2014, at 6:30 AM, Omer Frenkel <[email protected]> wrote:
> > > ----- Original Message ----- >> From: "Darrell Budic" <[email protected]> >> To: "Omer Frenkel" <[email protected]> >> Cc: "users" <[email protected]>, "Roy Golan" <[email protected]> >> Sent: Wednesday, July 9, 2014 6:20:16 PM >> Subject: Re: [ovirt-users] video driver selection for VNC consoles >> >> Nice, I missed this somewhere along the line. >> >> Unfortunately, it’s not working for me. I created a 10-osinfo.properties in >> /usr/share/ovirt-engine/conf and symlinked it into >> /etc/ovirt-engine/osinfo.conf.d for good measure, restarted jboss-as and >> ovirt-engine, and started up a VM but it still got a -vga cirrus device. >> >> Contents of my 10-osinfo.properties: >> os.other.devices.display.protocols.value = vnc/vga,qxl/qxl >> >> I notice I didn’t have an os.other.devices.display.protocols in my existing >> 00-defaults.properties. I’m running 3.3.4 on this cluster, is this fully >> supported in that version? >> > > well i forgot to mention that this will only work for new vms, or if you edit > the vm and switch the display type (to spice and after that again to vnc) > because this value is saved in the db the moment the display device is > created (add vm or update of display type) > > please pay attention that win8,win8x64,win2012x64 override this value also Yeap, discovered that this weekend. Also updated to 3.4.3 and now have a default entry for this in the 00-defaults.properties. Now working as expected, thanks! I see there are some checks for these values at VM start, my one win8x64 vm with a SPICE console wouldn’t start because of the new default entry. Seems odd that it only partially applies at VM start, I’d expect it to be all or nothing at that state (Ie, if it only changes at device creation, why does it check at other times as well?). Not a huge deal though. _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
