From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: ravi kerur <rkerur@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Q on netfront/netback driver
Date: Mon, 1 Feb 2010 12:37:14 -0500 [thread overview]
Message-ID: <20100201173714.GA26825@phenom.dumpdata.com> (raw)
In-Reply-To: <dfc283f41001310829g6ab5af10q8eb3335c3d90bfce@mail.gmail.com>
On Sun, Jan 31, 2010 at 08:29:04AM -0800, ravi kerur wrote:
> Hello all,
>
> I am trying to understand when and how netback and netfront drivers gets
> instantiated and does netfront exist in domU's?
I would recommend you look in the source code to understand its
handshake mechanism. Or better yet, pick up the 'Definitive Guide to the
Xen hypervisor".
Netfront will exist in DomU's if it is compiled in or as a module
depending on the distro.
>
> I do see the drivers available in following directory in dom0 but nothing in
> domU...
>
> $ pwd
> /lib/modules/2.6.18-128.1.6.el5.xs5.5.0.496.1012xen/kernel/drivers/xen
>
> $ ls
> pciback scsiback scsifront sfc_netback sfc_netfront sfc_netutil
> tpmback
>
> However, I do not see the drivers listed when "lsmod" is executed on dom0 or
> domU.
It might be very well compiled in, at which point it is not a module.
Look in your .config file for NETBACK.
>
> Inputs appreciated.
>
> Thanks
> -RK
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-02-01 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 16:29 Q on netfront/netback driver ravi kerur
2010-01-31 17:43 ` ravi kerur
2010-02-01 17:37 ` Konrad Rzeszutek Wilk [this message]
2010-02-01 19:56 ` ravi kerur
2010-02-01 21:16 ` Konrad Rzeszutek Wilk
2010-02-03 4:14 ` ravi kerur
2010-02-03 15:49 ` Konrad Rzeszutek Wilk
2010-02-03 17:43 ` Daniel Stodden
2010-02-03 23:22 ` ravi kerur
2010-02-04 0:31 ` Daniel Stodden
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=20100201173714.GA26825@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=rkerur@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.