Hi Christophe
El lun, 23-10-2017 a las 14:29 +0200, Christophe Fergeau escribió:
> Hey,
>
> On Mon, Oct 23, 2017 at 09:51:51AM +0200, Javier Celaya wrote:
> > Hello list,
> >
> > Recently, we updated the Qemu version being used by flexVDI. We
> > were
> > using a pre-3.3 QXL device, so it did not
Hi Frediano
El lun, 23-10-2017 a las 07:31 -0400, Frediano Ziglio escribió:
> Hi
>
> El lun, 23-10-2017 a las 06:57 -0400, Frediano Ziglio escribió:
>
> Hello list,
>
> Recently, we updated the Qemu version being used by flexVDI. We were
> using a pre-3.3 QXL device, so it did not provide the
>
Hey,
On Mon, Oct 23, 2017 at 09:51:51AM +0200, Javier Celaya wrote:
> Hello list,
>
> Recently, we updated the Qemu version being used by flexVDI. We were
> using a pre-3.3 QXL device, so it did not provide the
> client_monitors_config callback and that message was getting through to
> the VDAgen
> Hi
> El lun, 23-10-2017 a las 06:57 -0400, Frediano Ziglio escribió:
> > > Hello list,
> >
>
> > > Recently, we updated the Qemu version being used by flexVDI. We were
> > > using
> > > a
> > > pre-3.3 QXL device, so it did not provide the client_monitors_config
> > > callback and that messa
Hi
El lun, 23-10-2017 a las 06:57 -0400, Frediano Ziglio escribió:
> Hello list,
>
> Recently, we updated the Qemu version being used by flexVDI. We were
> using a pre-3.3 QXL device, so it did not provide the
> client_monitors_config callback and that message was getting through
> to the VDAgent,
> Hello list,
> Recently, we updated the Qemu version being used by flexVDI. We were using a
> pre-3.3 QXL device, so it did not provide the client_monitors_config
> callback and that message was getting through to the VDAgent, which in turn
> changed the resolution of the guest. This was working
