Re: [Qemu-devel] Re: Spice project is now open

[Izik Eidus <ieidus@redhat.com>]

On Sat, 12 Dec 2009 18:18:01 -0600
Anthony Liguori <anthony@codemonkey.ws> wrote:

> Andrea Arcangeli wrote:
> > On Sat, Dec 12, 2009 at 05:52:49PM -0600, Anthony Liguori wrote:
> >   
> >> This is the bit that confuses me.  VNC is not a driver.  When I
> >> say it cannot crash the guest, I mean that if the VNC server makes
> >> a mistake, there may be a SEGV in qemu or it may just result in a
> >> VNC client seeing corruption.  The guest does not see a bad VGA
> >> register content though or something like that.  VNC is a host
> >> driver or backend service or whatever you want to call it.  VNC
> >> does not have migration state because it has no guest visible
> >> state. 
> >
> > Again, a guest crash because of qlx interaction is not what I
> > mean. And the reason I wasn't even thinking about this scenario is
> > that the kind of paravirt-driver related guest crash you are talking
> > about, if it can happen, can happen even if spice lib in the qemu
> > side lives in a separate address space.
> 
> Yes, that's absolutely true.
> 
> >  This is why this case of pure guest
> > crash through qlx is not relevant to decide if to have spice lib
> > inside our outside of qemu address space, I think that is more about
> > the qlx driver and not spice on the qemu side.
> >   
> 
> The guest visible state thing has nothing to do with where it lives.  
> Sorry if that's gotten mixed in with this discussion.

The guest visible state is just the qxl device.
It is pci device..., and it migrate just like any other pci device
inside qemu...

What am I missing here?