Fwd: netback (Network backend) in domU

All of lore.kernel.org
 help / color / mirror / Atom feed

* Fwd: netback (Network backend) in domU
       [not found] <CAGj-7pXQuEhfZcWmpmUkp7VdnqbbP3qZh0ZqS_TMVg8FrXd0Rw@mail.gmail.com>
@ 2012-06-19 13:49 ` Shakeel Butt
  2012-06-19 16:41   ` Konrad Rzeszutek Wilk
  2012-06-20 11:53   ` Ian Campbell
  0 siblings, 2 replies; 9+ messages in thread
From: Shakeel Butt @ 2012-06-19 13:49 UTC (permalink / raw)
  To: xen-devel

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.

---------- 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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  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-20 11:53   ` Ian Campbell
  1 sibling, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2012-06-19 16:41 UTC (permalink / raw)
  To: Shakeel Butt; +Cc: xen-devel

On Tue, Jun 19, 2012 at 09:49:12AM -0400, 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.

Wow. That is quite ancient. Do you see the same problem with the latest
Linux kernel?

> 
> 
> ---------- 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.

Looks like a bug in the old code.
> 
> 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)

No.
> 
> thanks,
> Shakeel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-19 16:41   ` Konrad Rzeszutek Wilk
@ 2012-06-19 17:12     ` Shakeel Butt
  2012-06-19 17:34       ` Pasi Kärkkäinen
  0 siblings, 1 reply; 9+ messages in thread
From: Shakeel Butt @ 2012-06-19 17:12 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

On Tue, Jun 19, 2012 at 12:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Jun 19, 2012 at 09:49:12AM -0400, 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.
>
> Wow. That is quite ancient. Do you see the same problem with the latest
> Linux kernel?
>
I didn't try with newer kernel but will do it now.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-19 17:12     ` Shakeel Butt
@ 2012-06-19 17:34       ` Pasi Kärkkäinen
  2012-06-27 21:19         ` Shakeel Butt
  0 siblings, 1 reply; 9+ messages in thread
From: Pasi Kärkkäinen @ 2012-06-19 17:34 UTC (permalink / raw)
  To: Shakeel Butt; +Cc: xen-devel, Konrad Rzeszutek Wilk

On Tue, Jun 19, 2012 at 01:12:54PM -0400, Shakeel Butt wrote:
> On Tue, Jun 19, 2012 at 12:41 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Tue, Jun 19, 2012 at 09:49:12AM -0400, 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.
> >
> > Wow. That is quite ancient. Do you see the same problem with the latest
> > Linux kernel?
> >
> I didn't try with newer kernel but will do it now.
> 

And while you're at it try new Xen aswell :)
So Xen 4.1.2+ and Linux 3.4.2+.

-- Pasi

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-19 17:34       ` Pasi Kärkkäinen
@ 2012-06-27 21:19         ` Shakeel Butt
  0 siblings, 0 replies; 9+ messages in thread
From: Shakeel Butt @ 2012-06-27 21:19 UTC (permalink / raw)
  To: Pasi Kärkkäinen; +Cc: xen-devel, Konrad Rzeszutek Wilk

> And while you're at it try new Xen aswell :)
> So Xen 4.1.2+ and Linux 3.4.2+.
>
I tried the same scenario with Xen 4.1.2 and Linux 3.4.3 and it
worked. The only different thing I did was to create the bridges in
dom0 and netback-domU manually instead of using Xen script
'network-bridge'.

Shakeel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-19 13:49 ` Fwd: netback (Network backend) in domU Shakeel Butt
  2012-06-19 16:41   ` Konrad Rzeszutek Wilk
@ 2012-06-20 11:53   ` Ian Campbell
  2012-06-21 16:42     ` Shakeel Butt
  1 sibling, 1 reply; 9+ messages in thread
From: Ian Campbell @ 2012-06-20 11:53 UTC (permalink / raw)
  To: Shakeel Butt; +Cc: xen-devel

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-20 11:53   ` Ian Campbell
@ 2012-06-21 16:42     ` Shakeel Butt
  2012-06-21 18:17       ` Shakeel Butt
  0 siblings, 1 reply; 9+ messages in thread
From: Shakeel Butt @ 2012-06-21 16:42 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel

My mistake, I should have given more detail. I have included all the
necessary details in this email. I used network-bridge for creating
bridge in netback-domU and dom0 uses the same script on bootup. While
I think vif-bridge is used in both dom0 and netback-domU for hotplug
script.

The network configuration of netback-domU is

vif = ['mac=00:16:3e:00:00:94, bridge=eth0, ip=135.207.223.70']

while for other-domU is

vif = ['mac=00:16:3e:00:00:96, bridge=eth0, ip=135.207.223.71,
backend=test-domU-SD']

Detail of Dom0:
-----------------
-bash-3.2# xenstore-ls
local = ""
 domain = ""
  0 = ""
   backend = ""
    vif = ""
     1 = ""
      0 = ""
       bridge = "eth0"
       domain = "test-domU-SD"
       handle = "0"
       uuid = "d9f2c904-becd-9bcc-fa4f-4c9a800e585a"
       script = "/etc/xen/scripts/vif-bridge"
       ip = "135.207.223.70"
       state = "4"
       frontend = "/local/domain/1/device/vif/0"
       mac = "00:16:3e:00:00:94"
       online = "1"
       frontend-id = "1"
       feature-sg = "1"
       feature-gso-tcpv4 = "1"
       feature-rx-copy = "1"
       hotplug-status = "connected"
--------
  1 = ""
   device = ""
    vif = ""
     0 = ""
      mac = "00:16:3e:00:00:94"
      handle = "0"
      protocol = "x86_64-abi"
      backend-id = "0"
      state = "4"
      backend = "/local/domain/0/backend/vif/1/0"
      tx-ring-ref = "768"
      rx-ring-ref = "769"
      event-channel = "11"
      request-rx-copy = "0"
      feature-rx-notify = "1"
      feature-no-csum-offload = "0"
      feature-sg = "1"
      feature-gso-tcpv4 = "1"
   backend = ""
    vif = ""
     2 = ""
      0 = ""
       bridge = "eth0"
       domain = "test-domU"
       handle = "0"
       uuid = "2314d790-5223-cf26-59b2-1c0d6d053fe0"
       script = "/etc/xen/scripts/vif-bridge"
       ip = "135.207.223.71"
       state = "4"
       frontend = "/local/domain/2/device/vif/0"
       mac = "00:16:3e:00:00:96"
       online = "1"
       frontend-id = "2"
       feature-sg = "1"
       feature-gso-tcpv4 = "1"
       feature-rx-copy = "1"
       feature-rx-flip = "0"
       hotplug-status = "connected"
-------
  2 = ""
   device = ""
    vif = ""
     0 = ""
      mac = "00:16:3e:00:00:96"
      handle = "0"
      protocol = "x86_64-abi"
      backend-id = "1"
      state = "4"
      backend = "/local/domain/1/backend/vif/2/0"
      tx-ring-ref = "768"
      rx-ring-ref = "769"
      event-channel = "11"
      request-rx-copy = "1"
      feature-rx-notify = "1"
      feature-no-csum-offload = "0"
      feature-sg = "1"
      feature-gso-tcpv4 = "1"

-bash-3.2# brctl show
bridge name	bridge id		STP enabled	interfaces
eth0		8000.00219b9006ec	no		peth0
            							vif1.0
-bash-3.2# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:21:9b:90:06:ec
          inet addr:135.207.223.69  Bcast:135.207.223.255  Mask:255.255.255.0
          inet6 addr: fe80::221:9bff:fe90:6ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10596 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2707 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:776291 (758.0 KiB)  TX bytes:439416 (429.1 KiB)

lo ---

peth0     Link encap:Ethernet  HWaddr 00:21:9b:90:06:ec
          inet6 addr: fe80::221:9bff:fe90:6ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11737 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2851 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1046046 (1021.5 KiB)  TX bytes:465670 (454.7 KiB)
          Interrupt:18 Memory:d6000000-d6012800

veth0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vif0.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:146 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4460 errors:0 dropped:33 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:11978 (11.6 KiB)  TX bytes:401242 (391.8 KiB)


Detail of netback-domU:
-----------------------
-bash-3.2# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3E:00:00:94
          inet addr:135.207.223.70  Bcast:135.207.223.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3960 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:293401 (286.5 KiB)  TX bytes:10323 (10.0 KiB)

lo        Link encap:Local Loopback  0  Metric:1
          RX packets:3957 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:348942 (340.7 KiB)  TX bytes:11041 (10.7 KiB)

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2036 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:1334 (1.3 KiB)  TX bytes:176630 (172.4 KiB)

-bash-3.2# brctl show
bridge name	bridge id		STP enabled	interfaces
eth0		8000.00163e000094	no		vif2.0
            							peth0
-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:94
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.70
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

Detail of other-domU:
-----------------------
-bash-3.2# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3E:00:00:96
          inet addr:135.207.223.71  Bcast:135.207.223.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2187 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:192417 (187.9 KiB)  TX bytes:1670 (1.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

-bash-3.2# brctl show
bridge name	bridge id		STP enabled	interfaces
-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:96
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.71
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

------------------------------------------------------------------------
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

peth0     Link encap:Ethernet  HWaddr 00:16:3E:00:00:94
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3957 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:348942 (340.7 KiB)  TX bytes:11041 (10.7 KiB)

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2036 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:1334 (1.3 KiB)  TX bytes:176630 (172.4 KiB)

-bash-3.2# brctl show
bridge name	bridge id		STP enabled	interfaces
eth0		8000.00163e000094	no		vif2.0
            							peth0
-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:94
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.70
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

Detail of other-domU:
-----------------------
-bash-3.2# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3E:00:00:96
          inet addr:135.207.223.71  Bcast:135.207.223.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2187 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:192417 (187.9 KiB)  TX bytes:1670 (1.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

-bash-3.2# brctl show
bridge name	bridge id		STP enabled	interfaces
-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:96
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.71
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

------------------------------------------------------------------------

Shakeel

On Wed, Jun 20, 2012 at 7:53 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> 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
>
>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-21 16:42     ` Shakeel Butt
@ 2012-06-21 18:17       ` Shakeel Butt
  2012-06-22 11:30         ` Ian Campbell
  0 siblings, 1 reply; 9+ messages in thread
From: Shakeel Butt @ 2012-06-21 18:17 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel

I have messed up my copy/paste on details of netback-domU and
other-domU. So, for these two the clear details are below:

Detail of netback-domU:
-----------------------
-bash-3.2# ifconfig -a
eth0     Link encap:Ethernet  HWaddr 00:16:3E:00:00:94
         inet addr:135.207.223.70  Bcast:135.207.223.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3960 errors:0 dropped:0 overruns:0 frame:0
         TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:293401 (286.5 KiB)  TX bytes:10323 (10.0 KiB)

lo       Link encap:Local Loopback  0  Metric:1
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

peth0     Link encap:Ethernet  HWaddr 00:16:3E:00:00:94
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3957 errors:0 dropped:0 overruns:0 frame:0
         TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:348942 (340.7 KiB)  TX bytes:11041 (10.7 KiB)

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:24 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2036 errors:0 dropped:2 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:1334 (1.3 KiB)  TX bytes:176630 (172.4 KiB)


-bash-3.2# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00163e000094       no              vif2.0

         peth0


-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:94
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.70
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

Detail of other-domU:
-----------------------
-bash-3.2# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3E:00:00:96
         inet addr:135.207.223.71  Bcast:135.207.223.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:2187 errors:0 dropped:0 overruns:0 frame:0
         TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:192417 (187.9 KiB)  TX bytes:1670 (1.6 KiB)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

-bash-3.2# brctl show
bridge name     bridge id               STP enabled     interfaces

-bash-3.2# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:16:3e:00:00:96
ONBOOT=yes
TYPE=Ethernet
IPADDR=135.207.223.71
NETMASK=255.255.255.0
GATEWAY=135.207.223.1

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Fwd: netback (Network backend) in domU
  2012-06-21 18:17       ` Shakeel Butt
@ 2012-06-22 11:30         ` Ian Campbell
  0 siblings, 0 replies; 9+ messages in thread
From: Ian Campbell @ 2012-06-22 11:30 UTC (permalink / raw)
  To: Shakeel Butt; +Cc: xen-devel

Please don't top post, makes it harder to follow the conversation.

On Thu, 2012-06-21 at 19:17 +0100, Shakeel Butt wrote:
> I have messed up my copy/paste on details of netback-domU and
> other-domU. So, for these two the clear details are below:
> 
> Detail of netback-domU:
> -----------------------
[...]
> Detail of other-domU:
> -----------------------
[...]

So if I understand correctly netback-domU's route to the outside world
if via a virtual interface connected to dom0 -- is that right?

If so then I'm afraid I think this doesn't work -- you can bridge
several netback devices together or you can bridge netfront devices
together but in the current implementation of netfront/netback I believe
it is not possible to bridge a mixture of the two.

The reason is that the netfront/back protocol currently does not make
use of "transitive grants" which are necessary for the netback-domU
domain to forward pages from a netfront to the netback running in dom0.
Trying to forward in this way without using a "transitive grant" is what
results in your original "grant_table.c:387:d0 Could not pin grant frame
9d44e" message. I'm afraid I don't know of anyone who is currently
working on implementing this feature.

The more normal configuration (which is what I thought you were using at
first) would be to pass a physical NIC to netback-domU using PCI
passthrough and then optionally create a VIF on dom0 in order to give it
access. Perhaps that would be suitable for your usecase?

Ian.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2012-06-27 21:19 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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
2012-06-21 16:42     ` Shakeel Butt
2012-06-21 18:17       ` Shakeel Butt
2012-06-22 11:30         ` Ian Campbell

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.