From: Ian Campbell <Ian.Campbell@citrix.com>
To: Shakeel Butt <shakeel.butt@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Fwd: netback (Network backend) in domU
Date: Wed, 20 Jun 2012 12:53:50 +0100 [thread overview]
Message-ID: <1340193230.4906.45.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <CAGj-7pVpoePA=RDMNL3c4hpGhOdFMZDW83piVCMYO--pELFqmg@mail.gmail.com>
On Tue, 2012-06-19 at 14:49 +0100, Shakeel Butt wrote:
> I previously email at xen-user list but didn't get any response. I am
> using Xen-3.4.0 and 2.6.18 as dom0 kernel and facing below problem.
Apart from the ancient version the main thing which I think is missing
is all the configuration detail specifics.
What are the actual network configuration in dom0 and domU? How are your
bridges setup? What hotplug scripts are you using? Are they triggering?
etc. What I'm looking for here is specific details like the outputs of
"ifconfig -a" "brctl show" the contents of files like ifcfg-*
or /etc/network/interfaces (depending on distro) in all the involved
domains.
Also how are you starting the netback-domU guest (command line), what is
its configuration file?
Same for the other-domU.
How are you attaching the vif to dom0, what command are you running to
make that happen?
When the system is setup with all domains running what does "xenstore-ls
-fp" contain? This will contain details of which device if attached to
which.
>
>
> ---------- Forwarded message ----------
> From: Shakeel Butt <shakeel.butt@gmail.com>
> Date: Mon, Jun 18, 2012 at 10:06 AM
> Subject: netback (Network backend) in domU
> To: xen-users@lists.xen.org
>
>
> Hi,
>
> I am trying to setup a domU as a network backend for some other domUs.
> I configured bridge in netback-domU using network-bridge script (not a
> driver domain). I am assigning static ip addresses to all domUs.
> Something like dom0 <-> netback-domU <-> other-domU.
>
> In the setup, netback-domU and other-domU are able to ping each other
> but whenever I tried to ping dom0 from other-domU, I get a XEN error
> message "grant_table.c:387:d0 Could not pin grant frame 9d44e" and in
> dom0 kernel "#### netback grant fails".
>
> I didn't check if dom0 is trying to pin grant frame of other-domU but
> why dom0 would do it. Please any help will be appreciated.
>
> BTW does the bridge in dom0 needs to know that one of its interface is
> connected to another bridge in netback-domU? (don't know how or why)
>
> thanks,
> Shakeel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-20 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGj-7pXQuEhfZcWmpmUkp7VdnqbbP3qZh0ZqS_TMVg8FrXd0Rw@mail.gmail.com>
2012-06-19 13:49 ` Fwd: netback (Network backend) in domU Shakeel Butt
2012-06-19 16:41 ` Konrad Rzeszutek Wilk
2012-06-19 17:12 ` Shakeel Butt
2012-06-19 17:34 ` Pasi Kärkkäinen
2012-06-27 21:19 ` Shakeel Butt
2012-06-20 11:53 ` Ian Campbell [this message]
2012-06-21 16:42 ` Shakeel Butt
2012-06-21 18:17 ` Shakeel Butt
2012-06-22 11:30 ` Ian Campbell
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=1340193230.4906.45.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=shakeel.butt@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 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).