On (Fri) Sep 18 2009 [12:55:20], Anthony Liguori wrote: >> So you need a tiny kernel side driver to unpack it into a meaningful >> fs, or just a user-user channel with a daemon each end and a protocol >> over it - nothing kernel in that. >> > > I think there's some confusion over what this driver actually is. > > From my perspective, this is a paravirtual serial device and nothing > more. All the discussion of things like guest copy/paste support is a > bit silly. This is the wrong way to approach that sort of thing because > it's not something that belongs in the kernel at all. Furthermore, the > current proposal doesn't handle anything like save/restore which is > needed for live migration. You're mistaken. If you see the patches, I'm only providing a transport in the kernel. No intelligence in the kernel as to what kind of data actually flows through. The save/restore support has to come from userspace, in this case qemu. And that support is very much present. Amit -- http://log.amitshah.net/ _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
