thr3ads.net - Xen users - No network after restore of PV domU [Jan 2013]

If this information is useful, please help other people find it:
Share via:

Cédric TINTANET

2013-Jan-25 09:18 UTC

No network after restore of PV domU

Hi.
When i shutdown my dom0 (debian squeeze kernel 2.6.32-5) all the domU 
are saved.
When the dom0 restart all the DomU domains are restored. --> Normal

But for the PVs domU, when they are restored I have no network anymore.
I need to type these commands to put the network up

xm console domuPV
(login ...)
ping gateway -->( no response)
ifdown eth0
ifup eth0
ping gateway --> ok

Is there a work around to this bug ?

  * Here is my PV domu config file:

bootloader=''/usr/lib/xen-default/bin/pygrub''
memory=1024
name="vmdev"
vcpus=1
vif = [ ''mac=00:16:3E:07:00:08 , bridge=xenbr0'' ]
disk = [ ''phy:/dev/mapper/vgvm-system,xvda,w'' ]

* Here is my dom0 network config file (/etc/network/interfaces):
auto eth0
iface eth0 inet manual
up sleep 5; ethtool -s eth0 autoneg off speed 1000 duplex full

auto xenbr0
iface xenbr0 inet static
         address 172.16.128.135
         netmask 255.255.0.0
         network 172.16.0.0
         broadcast 172.16.255.255
         gateway 172.16.0.254
         # dns-* options are implemented by the resolvconf package, if 
installed
         dns-nameservers 172.16.128.28 172.16.128.32
     bridge_ports eth0
     bridge_fd 0

* Here is my domu network config file:

auto eth0
iface eth0 inet static
         address 172.16.128.144
         netmask 255.255.0.0
         network 172.16.0.0
         broadcast 172.16.255.255
         gateway 172.16.0.254


Cédric T



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-Jan-25 10:34 UTC

head link

Re: No network after restore of PV domU

On Fri, 2013-01-25 at 09:18 +0000, Cédric TINTANET
wrote:> Hi.
> When i shutdown my dom0 (debian squeeze kernel 2.6.32-5) all the domU 
> are saved.
> When the dom0 restart all the DomU domains are restored. --> Normal
> 
> But for the PVs domU, when they are restored I have no network anymore.
> I need to type these commands to put the network up
> 
> xm console domuPV
> (login ...)
> ping gateway -->( no response)
> ifdown eth0
> ifup eth0
> ping gateway --> ok
> 
> Is there a work around to this bug ?
IIRC some versions of the kernel, including the original Squeeze kernel
but not the latest, needed you to set a sysctl in order to send the
gratuitous ARP after migration/restore, look for arp_notify in sysctl in
the guest.

Not sure if this is related to that though, since outgoing traffic isn't
typically affected. Would be interesting to see `brctl` in dom0 and
`ifconfig -a` in both dom0 and domU before and after you apply the
workaround you describe.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Cédric TINTANET

2013-Jan-25 12:55 UTC

head link

Re: No network after restore of PV domU

Le 25/01/2013 11:34, Ian Campbell a écrit :> On Fri, 2013-01-25 at 09:18 +0000, Cédric TINTANET wrote:
>> Hi.
>> When i shutdown my dom0 (debian squeeze kernel 2.6.32-5) all the domU
>> are saved.
>> When the dom0 restart all the DomU domains are restored. --> Normal
>>
>> But for the PVs domU, when they are restored I have no network anymore.
>> I need to type these commands to put the network up
>>
>> xm console domuPV
>> (login ...)
>> ping gateway -->( no response)
>> ifdown eth0
>> ifup eth0
>> ping gateway --> ok
>>
>> Is there a work around to this bug ?
> IIRC some versions of the kernel, including the original Squeeze kernel
> but not the latest, needed you to set a sysctl in order to send the
> gratuitous ARP after migration/restore, look for arp_notify in sysctl in
> the guest.
>
> Not sure if this is related to that though, since outgoing traffic
isn''t
> typically affected. Would be interesting to see `brctl` in dom0 and
> `ifconfig -a` in both dom0 and domU before and after you apply the
> workaround you describe.
>
> Ian.
>In the guest

vmdev:~# sysctl net.ipv4.conf.eth0.arp_notify=1
net.ipv4.conf.eth0.arp_notify = 1
vmdev:~# sysctl net.ipv4.conf.lo.arp_notify=1
net.ipv4.conf.lo.arp_notify = 1

vmdev:~# sysctl -a | grep notify

net.ipv4.conf.all.arp_notify = 1
net.ipv4.conf.default.arp_notify = 1
net.ipv4.conf.lo.arp_notify = 1
net.ipv4.conf.eth0.arp_notify = 1


logout

---------------------
In dom0
--------------------
xm save vmdev /var/lib/xen/vmdev.save
xm restore /var/lib/xen/vmsev.save

*** BEFORE WORKAROUND ***

ping vmdev --> (broken)

Dom0:~# brctl show
bridge name    bridge id        STP enabled    interfaces
xenbr0        8000.002219682deb    no        eth0
                             tap1.0
                             tap4.0
                             vif1.0
                             vif11.0
                             vif2.0
                             vif3.0
                             vif4.0
                             vif5.0

Dom0:~# xm list
...
vmdev                                  11  3072     2     -b---- 0.3
...
vif11.0 corresponds to domU with iD 11 = vmdev

Dom0:~# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:22:19:68:2d:eb
           adr inet6: fe80::222:19ff:fe68:2deb/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:529295 errors:0 dropped:0 overruns:0 frame:0
           TX packets:45629 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:1000
           RX bytes:70138635 (66.8 MiB)  TX bytes:8675697 (8.2 MiB)
           Interruption:36 Mémoire:d6000000-d6012800

eth1      Link encap:Ethernet  HWaddr 00:22:19:68:2d:ed
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:48 Mémoire:d8000000-d8012800

eth2      Link encap:Ethernet  HWaddr 00:22:19:68:2d:ef
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:32 Mémoire:da000000-da012800

eth3      Link encap:Ethernet  HWaddr 00:22:19:68:2d:f1
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:42 Mémoire:dc000000-dc012800

lo        Link encap:Boucle locale
           inet adr:127.0.0.1  Masque:255.0.0.0
           adr inet6: ::1/128 Scope:Hôte
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:39 errors:0 dropped:0 overruns:0 frame:0

           TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:0
           RX bytes:3734 (3.6 KiB)  TX bytes:3734 (3.6 KiB)

tap1.0    Link encap:Ethernet  HWaddr da:68:c0:f8:0e:13
           adr inet6: fe80::d868:c0ff:fef8:e13/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:415658 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:500
           RX bytes:0 (0.0 B)  TX bytes:40432652 (38.5 MiB)

tap4.0    Link encap:Ethernet  HWaddr 6e:80:58:ab:fd:a0
           adr inet6: fe80::6c80:58ff:feab:fda0/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:23147 errors:0 dropped:0 overruns:0 frame:0
           TX packets:440071 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:500
           RX bytes:1912695 (1.8 MiB)  TX bytes:55369766 (52.8 MiB)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
           adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:9228 errors:0 dropped:0 overruns:0 frame:0
           TX packets:425144 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:32
           RX bytes:4799798 (4.5 MiB)  TX bytes:41875041 (39.9 MiB)

vif11.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
           adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:5727 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:32
           RX bytes:0 (0.0 B)  TX bytes:559075 (545.9 KiB)



vif11.0 appears in the interfaces and belongs to xenbr0

--------------
In guest
--------------

vmdev:~# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3e:ff:ff:03
           inet adr:172.16.128.182  Bcast:172.16.255.255 Masque:255.255.0.0
           adr inet6: fe80::216:3eff:feff:ff03/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:219765 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2209 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:1000
           RX bytes:18271666 (17.4 MiB)  TX bytes:227030 (221.7 KiB)
           Interruption:18

lo        Link encap:Boucle locale
           inet adr:127.0.0.1  Masque:255.0.0.0
           adr inet6: ::1/128 Scope:Hôte
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:43 errors:0 dropped:0 overruns:0 frame:0
           TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:0
           RX bytes:3875 (3.7 KiB)  TX bytes:3875 (3.7 KiB)

ping gateway ---> (broken)

*** AFTER WORKAROUND (ifdown , ifup ) ***

-----------
In guest
-----------


vmdev:~# /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3e:ff:ff:03
           inet adr:172.16.128.182  Bcast:172.16.255.255 Masque:255.255.0.0
           adr inet6: fe80::216:3eff:feff:ff03/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:344830 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2773 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:1000
           RX bytes:28888073 (27.5 MiB)  TX bytes:275588 (269.1 KiB)
           Interruption:18

lo        Link encap:Boucle locale
           inet adr:127.0.0.1  Masque:255.0.0.0
           adr inet6: ::1/128 Scope:Hôte
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:1215 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:0
           RX bytes:129604 (126.5 KiB)  TX bytes:129604 (126.5 KiB)

ping gateway --> OK

-----------
In dom0
-----------
ping vmdev --> OK

/sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:22:19:68:2d:eb
           adr inet6: fe80::222:19ff:fe68:2deb/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:547200 errors:0 dropped:0 overruns:0 frame:0
           TX packets:47214 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:1000
           RX bytes:72179844 (68.8 MiB)  TX bytes:8874857 (8.4 MiB)
           Interruption:36 Mémoire:d6000000-d6012800

eth1      Link encap:Ethernet  HWaddr 00:22:19:68:2d:ed
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:48 Mémoire:d8000000-d8012800

eth2      Link encap:Ethernet  HWaddr 00:22:19:68:2d:ef
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:32 Mémoire:da000000-da012800

eth3      Link encap:Ethernet  HWaddr 00:22:19:68:2d:f1
           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 lg file transmission:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interruption:42 Mémoire:dc000000-dc012800

lo        Link encap:Boucle locale
           inet adr:127.0.0.1  Masque:255.0.0.0
           adr inet6: ::1/128 Scope:Hôte
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:39 errors:0 dropped:0 overruns:0 frame:0
           TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:0
           RX bytes:3734 (3.6 KiB)  TX bytes:3734 (3.6 KiB)

tap1.0    Link encap:Ethernet  HWaddr da:68:c0:f8:0e:13
           adr inet6: fe80::d868:c0ff:fef8:e13/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:430085 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:500
           RX bytes:0 (0.0 B)  TX bytes:41922644 (39.9 MiB)

tap4.0    Link encap:Ethernet  HWaddr 6e:80:58:ab:fd:a0
           adr inet6: fe80::6c80:58ff:feab:fda0/64 Scope:Lien
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:23733 errors:0 dropped:0 overruns:0 frame:0
           TX packets:455073 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:500
           RX bytes:1952795 (1.8 MiB)  TX bytes:56909965 (54.2 MiB)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
           adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:9509 errors:0 dropped:0 overruns:0 frame:0
           TX packets:439855 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:32
           RX bytes:4864011 (4.6 MiB)  TX bytes:43409867 (41.3 MiB)

vif11.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
           adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
           RX packets:396 errors:0 dropped:0 overruns:0 frame:0
           TX packets:20112 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 lg file transmission:32
           RX bytes:28977 (28.2 KiB)  TX bytes:2057645 (1.9 MiB)


dom0:~# /sbin/brctl show
bridge name    bridge id        STP enabled    interfaces
xenbr0        8000.002219682deb    no        eth0
                             tap1.0
                             tap4.0
                             vif1.0
                             vif11.0
                             vif2.0
                             vif3.0
                             vif4.0
                             vif5.0



Cedric T









_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-Jan-25 13:43 UTC

head link

Re: No network after restore of PV domU

On Fri, 2013-01-25 at 12:55 +0000, Cédric TINTANET wrote:
> vif11.0 corresponds to domU with iD 11 = vmdev
[...snip...]

Thanks for all that, unfortunately it all looks the same before and
after (apart from the TX/RX counters, which is expected), so it hasn't
helped much, sorry.

I noticed that the guest's MAC address doesn't match the config file
example you gave originally -- was that the actual config or just a
representative example? Would be nice to see the literal config file,
just in case. Or perhaps something in the guest is changing the MAC
address (udev or a local script perhaps?). It probably doesn't matter
but its an anomaly so worth pursuing a bit I think.

Other things to check would be the routing tables both in the guest and
in dom0 and any firewall rules both within and without.

Then I'm afraid you're on to running tcpdump on each of the the devices
in dom0, vif11.0 xenbr0 and eth0 to see how far the traffic is getting
before it is getting lost.

Another thing to check would be the xenstore directories for the front
and backend device before and after the workaround.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Xen users - Jan 2013 - No network after restore of PV domU

No network after restore of PV domU

Re: No network after restore of PV domU

Re: No network after restore of PV domU

Re: No network after restore of PV domU