[Lguest] Some Queries

[siva sankar padhy]

Hi,
Thanks a lot for replying.have gone through the implementation and i got the
idea how it works and its really great work done by you. i really appreciate
your hard work.

*one more clarification:-

*Can it be the same with QEMU-KVM implementation.
i mean front-end drivers will use your virtio frame work and use the Vring
implemented APIs (add_buf, get_buf...)to interact with Vqueue.
QEMU will have the back-end driver implementation and will consume the
buffer and handover to underlying respective physical driver.
(Is the QEMU behaves the same way as the lguest launcher behaves)

i will be thankful for your reply...

With Regards,
Siva Sankar Padhy


On Sat, Sep 11, 2010 at 7:46 AM, Rusty Russell <rusty at rustcorp.com.au>wrote:

> On Wed, 18 Aug 2010 02:03:43 pm siva sankar padhy wrote:
> > hi,
> >
> > we are going to implement the virtualisation technique using Lguest in
> our
> > project..
>
> Hi,
>
>   Sorry for the delayed response.
>
> > i have gone through all the document and related docs but got confused
> about
> > the back end and frontend implementation..launching guest making
> virtqueue
> > and vring all those lies in back end part right. ?? then what about back
> end
> > drivers and front end drivers how do they map with virtqueue and vring.
>
> The "back end" == host.   The "front end" == guest.  Silly duplicate
> terminology, really.
>
> The host sets up the devices' vrings and tells the guest where they are.
>
> > please help me... otherwise my manager going to kill me...
>
> I hope that didn't happen!
>
> Cheers,
> Rusty.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/lguest/attachments/20100913/f61bcfa1/attachment-0001.html>