Re: [RFC PATCH v2 00/20] Monitor ID rework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Hi,

> There's not a new channel type, but there is a new channel, because
> there are two devices. Both the QXL device and the vGPU have their own
> Display channels. 
>  * channel #0 is the QXL device and only displays stuff at boot time
>    (or when switching to a VT)
>  * channel #1 is the nvidia device, which displays the desktop session
>    after X starts

What is channel #1?  The video stream from the guest agent?
What channel is used for the vgpu vnc console?

> Note that X only knows about the nvidia device, and from X's
> perspective, that device had a xrandr id of 0. So when (for example) we
> send mouse events for channel #1 to the vdagent, the vdagent will say:
> I don't know any dislay with id #1, I only know about display #0, and
> it will ignore those events.

Yes.  The guest needs some way to figure which channel is linked to
which device.

cheers,
  Gerd

_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux Virtualization]     [Linux Virtualization]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]