[Spice-devel] [RFC PATCH v2 00/20] Monitor ID rework

[Gerd Hoffmann]

  Hi,

> > Well, "vnc console" is how the nvidia guys name it, the term doesn't
> > really match.  It's basically a simple framebuffer where the nvidia
> > driver renders the guest display, and a vfio interface for qemu to
> > access it.  From spice point of view it looks very simliar to the qemu
> > standard vga, i.e. it is a classic display channel.
> > 
> > The nvidia driver renders to it at a low framerate (10fps).  It is
> > intended to be used in case the streaming agent doesn't work
> > (installation, trouble shooting, ...).
> 
> Oh, I see... So it has nothing to do with VNC. One has to wonder about
> the subtle implications though. Why didn't they name it the SPICE
> console? :D

Historical reasons I guess.  They have the same thing on Xen too, and
Xen is (or used to be?) vnc only.

> Anyway, this doesn't seem to change the situation at all then? From
> SPICE PoV, it matters little if it's a QXL device or this (non-)VNC
> console. It's a VGA-like device that has it's own display channel.

Well, with the current protocol not.

But if we attach some extra information to the display channels (both
classic and streaming), like a device path of the device to allow
linking channels to devices, then it is possible to figure that the vgpu
vnc console and the vgpu streaming channel are actually backed by the
same guest device.