From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] trace an incoming network packet of data ?
Date: Wed, 16 Aug 2006 11:16:32 +0200 [thread overview]
Message-ID: <b921df970608160216m52ac58cfhb8d8b156ee91d33c@mail.gmail.com> (raw)
In-Reply-To: <3ed52ec0608140717s60f7be4enf02489de29880418@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Hi,
I am interesting to understand qemu network manage too. I search and find
this document:
http://www.h7.dion.ne.jp/~qemu-win/HowToNetwork-en.html
Look if it can help you (I read it very fast but I think it's very
interesting).
2006/8/14, S. P. T. Krishnan <sptkrishnan@gmail.com>:
>
> Hi,
>
> I would like to know how a network packet of data is received by qemu
> and delivered to the guest OS ?
>
> I need to debug/print the incoming data at the qemu-level before it
> reaches the guest OS.
> Can you give me a few hints at what files and structs should I be
> spending some time on ?
>
> I saw vl.c to be of some importance along with /hw/ne2000.c which
> emulates the network card. However, I want to know the method
> (flow-chart ?) which qemu uses to interact with the host OS and
> transfers the packets of data to the guest OS ?
>
> Many thanks in advance for your time.
>
> regards,
> Krishnan
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
[-- Attachment #2: Type: text/html, Size: 1571 bytes --]
prev parent reply other threads:[~2006-08-16 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 14:17 [Qemu-devel] trace an incoming network packet of data ? S.P.T.Krishnan
2006-08-16 9:16 ` Alessandro Corradi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b921df970608160216m52ac58cfhb8d8b156ee91d33c@mail.gmail.com \
--to=ale.corradi@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).