All of lore.kernel.org
 help / color / mirror / Atom feed
From: ravi kerur <rkerur@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Q on netfront/netback driver
Date: Tue, 2 Feb 2010 20:14:53 -0800	[thread overview]
Message-ID: <dfc283f41002022014t2ab88bfcm4dc98be77906dca@mail.gmail.com> (raw)
In-Reply-To: <20100201211602.GC2756@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1324 bytes --]

Hi Konrad,

I thought Citrix Xenserver is based on Xen kernel and it inherited all of
Xen mgmt cli and other tools.

I have downloaded source code from
http://www.citrix.com/lang/English/lp/lp_1688623.asp
and have looked into product cd 1(in which I found netfront and netback
source code), product cd 4(probably tools). Unfortunately don't find
anything related to /xen/tools/hotplug... Any inputs?

Thanks
-RK

On Mon, Feb 1, 2010 at 1:16 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> >  In addition, I had follow-up question on creation of "vif"
> interface(this
> > is what I was referring to when I mentioned about instantiation of
> > netfront/netback), if I were to change this "vif" name to something else,
> > which part of the code should be modified. I have been searching for this
>
> You definitly will need to modify the udev rules and potentially a bunch
> of shell scripts in: xen/tools/hotplug/Linux
>
> If you mean the source code of the kernel, look in
> drivers/xen/netback/* files.
> .. snip ..
> > > > 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.
> Ah, I was incorrect. It is CONFIG_XEN_NETDEV_BACKEND.
>

[-- Attachment #1.2: Type: text/html, Size: 1863 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-02-03  4:14 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
2010-02-01 19:56   ` ravi kerur
2010-02-01 21:16     ` Konrad Rzeszutek Wilk
2010-02-03  4:14       ` ravi kerur [this message]
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=dfc283f41002022014t2ab88bfcm4dc98be77906dca@mail.gmail.com \
    --to=rkerur@gmail.com \
    --cc=konrad.wilk@oracle.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.