Avi Kivity wrote:
I disagree. A driver domain is shared between multiple guests, and if one of the guests manages to break into qemu then it can see other guest's data.
You still don't strictly need to do things in the kernel if this is your concern. You can have another process map both guest's address spaces and do the copying on behalf of each guest if you're paranoid about escaping into QEMU.
[Driver domains are a horrible idea IMO, but that's another story]
I don't disagree :-) Regards, Anthony Liguori _______________________________________________ Lguest mailing list Lguest@ozlabs.org https://ozlabs.org/mailman/listinfo/lguest
