2012/4/10 Mikael <mikael.tr...@gmail.com>

> Hi Jun -
>
> That's the problem - none of this can be done whatsoever with libvirt.
>
> The issue about libvirt is that it is a manager of virtualization programs
> running in separate OS processes. Doing the kind of tight interaction with
> several qemu instances in one userland process & thread, and full
> encapsulation of all the guests' IO into handlers in that app, would
> require Enormous amounts of IPC and OS context switching.



To the best of my knowledge, such an approach would mean an approx 1000%
> speed decrease in the qemu performance, compared to if it's used as a
> library as I queried for in the previous email.
>

Ah, that should have been 10 000% (100x).

Reply via email to