[Lguest] Some Queries

[siva sankar padhy]

Hi,

Thanks for replying.. it feels really very nice when i gets reply from your
team.

my project seems to be done very quickly and smoothly with all your
co-operation.:)

We also implemented many guest using lguest and it stands very
friendly...and also qemu footprint as you say is very high.

we are going to run 8 guest machine on a 8 core Linux machine as our client
demands to use QEMU-KVM hence we are going for it.

As far i have analyzed qemu uses softmmu technology and resister the address
space and exposes the pci cofig space to the guest for further
communication.The "find_vq" implementation of your virtio_pci interface asks
for the corresponding virtqueues
created by the host hypervisor through this shared space.

please clarify me if i am wrong with the analysis.


With Regards,
Siva Sankar Padhy


On Mon, Sep 13, 2010 at 7:57 PM, ron minnich <rminnich at gmail.com> wrote:

> just FYI, the qemu memory footprint for kvm guests is huge (several
> tens of Mbytes). Is there some perceived advantage to having qemu
> instead of the simple lguest program as it stands now?
>
> Also, the lguest program very cleverly makes the guest part of its
> memory space -- how would you propose to get this same effect if you
> used qemu?
>
> One reason we use lguest instead of kvm at sandia for our project is
> we can easily boot 1200 guests on an $877 desktop with 12 GB, which
> would not be possible were we using qemu (we tried).
>
> What is the compelling reason to want qemu?
>
> ron
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/lguest/attachments/20100922/6329db20/attachment-0001.html>