> On Fri, Aug 24, 2018 at 09:16:09AM -0400, Frediano Ziglio wrote:
> > >
> > > On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> > > > > Yes, we want this for sure. One channel per display.
> > > >
> > > > For sure? This deserves a justification.
> > >
> > > That is the way modern
On Fri, Aug 24, 2018 at 03:38:07PM +0200, Lukáš Hrázký wrote:
> On Fri, 2018-08-24 at 14:25 +0200, Gerd Hoffmann wrote:
> > On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> > > On Thu, 2018-08-23 at 22:42 +0200, Gerd Hoffmann wrote:
> > > > Hi,
> > > >
> > > > > "we only support"
On Fri, Aug 24, 2018 at 09:16:09AM -0400, Frediano Ziglio wrote:
> >
> > On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> > > > Yes, we want this for sure. One channel per display.
> > >
> > > For sure? This deserves a justification.
> >
> > That is the way modern display archite
On Fri, 2018-08-24 at 14:39 +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > Yes, we want this for sure. One channel per display.
> >
> > Maybe you cut too much context. Who is "we" in the above sentence?
> > Why "we want"?
>
> See other reply.
>
> > > Yes. *That* is the underlying problem. There
On Fri, 2018-08-24 at 14:25 +0200, Gerd Hoffmann wrote:
> On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> > On Thu, 2018-08-23 at 22:42 +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > "we only support" seems to just state the use cases before adding
> > > > vGPU but we are tr
>
> On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> > On Thu, 2018-08-23 at 22:42 +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > "we only support" seems to just state the use cases before adding
> > > > vGPU but we are trying to support vGPU cases.
> > > > If even we decide
Hi,
> > Yes, we want this for sure. One channel per display.
>
> Maybe you cut too much context. Who is "we" in the above sentence?
> Why "we want"?
See other reply.
> > Yes. *That* is the underlying problem. There is no guest-visible link
> > between display device and spice channel. Exc
On Fri, Aug 24, 2018 at 11:12:43AM +0200, Lukáš Hrázký wrote:
> On Thu, 2018-08-23 at 22:42 +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > "we only support" seems to just state the use cases before adding
> > > vGPU but we are trying to support vGPU cases.
> > > If even we decide that for vGPU ca
Hi,
> > Long-term there should be no need to have a separate QXL device for
> > boot messages.
>
> Interesting, why do you think so?
Well, there is the vnc console for the nvidia vgpu. Which wasn't
mentioned in this thread yet, how does it fit into the picture btw? I
guess there will be two
>
> Hi,
>
> > "we only support" seems to just state the use cases before adding
> > vGPU but we are trying to support vGPU cases.
> > If even we decide that for vGPU cards we always have monitor_id == 0
>
> Yes, we want this for sure. One channel per display.
>
Maybe you cut too much context.
On Thu, 2018-08-23 at 22:42 +0200, Gerd Hoffmann wrote:
> Hi,
>
> > "we only support" seems to just state the use cases before adding
> > vGPU but we are trying to support vGPU cases.
> > If even we decide that for vGPU cards we always have monitor_id == 0
>
> Yes, we want this for sure. One c
Hi Gerd,
On Thu, 2018-08-23 at 22:56 +0200, Gerd Hoffmann wrote:
> Hi,
>
> > 1. The logic used to switch something for something and when - You need
> > to define somehow you have this QXL device that is showing the boot in
> > client display 1 and then you start X and want to replace client
>
12 matches
Mail list logo
