thr3ads.net - Xen users - network is only connected for a while when the domU is started [Jun 2012]

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

王卅

2012-Jun-07 10:52 UTC

network is only connected for a while when the domU is started

Hi ALL,

Here is a weird problem comfusing me for a long time. i''v installed xen
4.0.1 with linux kernel 3.1.0-rc9+
Everything works fine except i cannot ping to the gateway in a PVM domU.
i''v installed bridge-utils and brctl show like this

  bridge  name         bridge id                      STP          enabled
interfaces
eth0                      8000.00219b480d56     no             peth0

    vif11.0
virbr0                     8000.000000000000     yes

 The domU is supposed to get a IP from a DHCP server in our network so i
can access to it from any node in that network.
i made the eth0 bridge as a switch and the domU could access to the DHCP
server across it. it works fine on a HVM domU.

 The most weird part is the PVM could get an IP address every time i start
it and i could ping to the gateway too. But after just a few minutes, the
ping process is stuck, and the host become unreacheable. At the same time,
i restart the network, and the eth0 in domU could not get an IP address.

 i post the output here:

 133.133.133.40 is the IP address of gateway
133.133.134.171 is the IP address of the PVM domU

  [root@localhost ~]# ping 133.133.133.40
PING 133.133.133.40 (133.133.133.40) 56(84) bytes of data.
64 bytes from 133.133.133.40: icmp_seq=1 ttl=64 time=0.824 ms
64 bytes from 133.133.133.40: icmp_seq=2 ttl=64 time=0.491 ms
64 bytes from 133.133.133.40: icmp_seq=3 ttl=64 time=0.495 ms
64 bytes from 133.133.133.40: icmp_seq=4 ttl=64 time=0.437 ms
64 bytes from 133.133.133.40: icmp_seq=5 ttl=64 time=0.459 ms
64 bytes from 133.133.133.40: icmp_seq=6 ttl=64 time=1.16 ms
64 bytes from 133.133.133.40: icmp_seq=7 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=8 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=9 ttl=64 time=0.528 ms
64 bytes from 133.133.133.40: icmp_seq=10 ttl=64 time=0.447 ms
64 bytes from 133.133.133.40: icmp_seq=11 ttl=64 time=0.505 ms
64 bytes from 133.133.133.40: icmp_seq=12 ttl=64 time=0.398 ms
64 bytes from 133.133.133.40: icmp_seq=13 ttl=64 time=0.452 ms
64 bytes from 133.133.133.40: icmp_seq=14 ttl=64 time=0.504 ms
64 bytes from 133.133.133.40: icmp_seq=15 ttl=64 time=0.456 ms
64 bytes from 133.133.133.40: icmp_seq=16 ttl=64 time=0.451 ms
64 bytes from 133.133.133.40: icmp_seq=17 ttl=64 time=0.501 ms
64 bytes from 133.133.133.40: icmp_seq=18 ttl=64 time=0.446 ms
64 bytes from 133.133.133.40: icmp_seq=19 ttl=64 time=0.373 ms
64 bytes from 133.133.133.40: icmp_seq=20 ttl=64 time=0.413 ms
64 bytes from 133.133.133.40: icmp_seq=21 ttl=64 time=0.495 ms
64 bytes from 133.133.133.40: icmp_seq=22 ttl=64 time=0.452 ms
64 bytes from 133.133.133.40: icmp_seq=23 ttl=64 time=0.407 ms
64 bytes from 133.133.133.40: icmp_seq=24 ttl=64 time=0.505 ms
64 bytes from 133.133.133.40: icmp_seq=25 ttl=64 time=0.471 ms
64 bytes from 133.133.133.40: icmp_seq=26 ttl=64 time=0.458 ms
64 bytes from 133.133.133.40: icmp_seq=27 ttl=64 time=0.453 ms
64 bytes from 133.133.133.40: icmp_seq=28 ttl=64 time=0.453 ms
64 bytes from 133.133.133.40: icmp_seq=29 ttl=64 time=0.456 ms
64 bytes from 133.133.133.40: icmp_seq=30 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=31 ttl=64 time=0.424 ms
From 133.133.134.171 icmp_seq=85 Destination Host Unreachable
From 133.133.134.171 icmp_seq=86 Destination Host Unreachable
From 133.133.134.171 icmp_seq=87 Destination Host Unreachable
From 133.133.134.171 icmp_seq=89 Destination Host Unreachable
From 133.133.134.171 icmp_seq=90 Destination Host Unreachable
From 133.133.134.171 icmp_seq=91 Destination Host Unreachable

 i also post my configuration of PVM domU here:

  <domain type=''xen'' id=''12''>
 <name>centos-para</name>
 <uuid>67256e52-ac7d-a95e-fd58-8114475e454e</uuid>
 <memory>1048576</memory>
 <currentMemory>1048576</currentMemory>
 <vcpu>1</vcpu>
 <bootloader>/usr/bin/pygrub</bootloader>
 <os>
 <type>linux</type>
 </os>
 <clock offset=''utc''/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>restart</on_crash>
 <devices>
 <disk type=''file'' device=''disk''>
 <driver name=''file''/>
 <source file=''/root/vm/centos-para/centos-para.img''/>
 <target dev=''xvda'' bus=''xen''/>
 </disk>
 <interface type=''bridge''>
 <mac address=''00:16:3e:29:e4:9c''/>
 <source bridge=''eth0''/>
 <script path=''/etc/xen/scripts/vif-bridge''/>
 <target dev=''vif12.0''/>
 </interface>
 <console type=''pty'' tty=''/dev/pts/2''>
 <source path=''/dev/pts/2''/>
 <target port=''0''/>
 </console>
 </devices>
</domain>
 is there anyone could help me please？ i‘v googled lots of stuff but
nothing helped.


sa wang

2012-06-07
------------------------------
  --------------------------------------------------
Wang Sa（王卅）,Ph,D candidate
Technology Center of Software Engineering
Institute of Software, Chinese Academy of Sciences
P.O.Box 8718, Beijing 100190, China


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

王卅

2012-Jun-08 06:08 UTC

head link

network is only connected for a while when the domU is started

Hi ALL,

Here is a weird problem comfusing me for a long time. i''v installed xen
4.0.1 with linux kernel 3.1.0-rc9+
Everything works fine except i cannot ping to the gateway in a PVM domU.
i''v installed bridge-utils and brctl show like this

  bridge  name         bridge id                      STP          enabled
interfaces
eth0                      8000.00219b480d56     no             peth0

    vif11.0
virbr0                     8000.000000000000     yes

 The domU is supposed to get a IP from a DHCP server in our network so i
can access to it from any node in that network.
i made the eth0 bridge as a switch and the domU could access to the DHCP
server across it. it works fine on a HVM domU.

 The most weird part is the PVM could get an IP address every time i start
it and i could ping to the gateway too. But after just a few minutes, the
ping process is stuck, and the host become unreacheable. At the same time,
i restart the network, and the eth0 in domU could not get an IP address.

 i post the output here:

 133.133.133.40 is the IP address of gateway
133.133.134.171 is the IP address of the PVM domU

  [root@localhost ~]# ping 133.133.133.40
PING 133.133.133.40 (133.133.133.40) 56(84) bytes of data.
64 bytes from 133.133.133.40: icmp_seq=1 ttl=64 time=0.824 ms
64 bytes from 133.133.133.40: icmp_seq=2 ttl=64 time=0.491 ms
64 bytes from 133.133.133.40: icmp_seq=3 ttl=64 time=0.495 ms
64 bytes from 133.133.133.40: icmp_seq=4 ttl=64 time=0.437 ms
64 bytes from 133.133.133.40: icmp_seq=5 ttl=64 time=0.459 ms
64 bytes from 133.133.133.40: icmp_seq=6 ttl=64 time=1.16 ms
64 bytes from 133.133.133.40: icmp_seq=7 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=8 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=9 ttl=64 time=0.528 ms
64 bytes from 133.133.133.40: icmp_seq=10 ttl=64 time=0.447 ms
64 bytes from 133.133.133.40: icmp_seq=11 ttl=64 time=0.505 ms
64 bytes from 133.133.133.40: icmp_seq=12 ttl=64 time=0.398 ms
64 bytes from 133.133.133.40: icmp_seq=13 ttl=64 time=0.452 ms
64 bytes from 133.133.133.40: icmp_seq=14 ttl=64 time=0.504 ms
64 bytes from 133.133.133.40: icmp_seq=15 ttl=64 time=0.456 ms
64 bytes from 133.133.133.40: icmp_seq=16 ttl=64 time=0.451 ms
64 bytes from 133.133.133.40: icmp_seq=17 ttl=64 time=0.501 ms
64 bytes from 133.133.133.40: icmp_seq=18 ttl=64 time=0.446 ms
64 bytes from 133.133.133.40: icmp_seq=19 ttl=64 time=0.373 ms
64 bytes from 133.133.133.40: icmp_seq=20 ttl=64 time=0.413 ms
64 bytes from 133.133.133.40: icmp_seq=21 ttl=64 time=0.495 ms
64 bytes from 133.133.133.40: icmp_seq=22 ttl=64 time=0.452 ms
64 bytes from 133.133.133.40: icmp_seq=23 ttl=64 time=0.407 ms
64 bytes from 133.133.133.40: icmp_seq=24 ttl=64 time=0.505 ms
64 bytes from 133.133.133.40: icmp_seq=25 ttl=64 time=0.471 ms
64 bytes from 133.133.133.40: icmp_seq=26 ttl=64 time=0.458 ms
64 bytes from 133.133.133.40: icmp_seq=27 ttl=64 time=0.453 ms
64 bytes from 133.133.133.40: icmp_seq=28 ttl=64 time=0.453 ms
64 bytes from 133.133.133.40: icmp_seq=29 ttl=64 time=0.456 ms
64 bytes from 133.133.133.40: icmp_seq=30 ttl=64 time=0.454 ms
64 bytes from 133.133.133.40: icmp_seq=31 ttl=64 time=0.424 ms
From 133.133.134.171 icmp_seq=85 Destination Host Unreachable
From 133.133.134.171 icmp_seq=86 Destination Host Unreachable
From 133.133.134.171 icmp_seq=87 Destination Host Unreachable
From 133.133.134.171 icmp_seq=89 Destination Host Unreachable
From 133.133.134.171 icmp_seq=90 Destination Host Unreachable
From 133.133.134.171 icmp_seq=91 Destination Host Unreachable

 i also post my configuration of PVM domU here:

  <domain type=''xen'' id=''12''>
 <name>centos-para</name>
 <uuid>67256e52-ac7d-a95e-fd58-8114475e454e</uuid>
 <memory>1048576</memory>
 <currentMemory>1048576</currentMemory>
 <vcpu>1</vcpu>
 <bootloader>/usr/bin/pygrub</bootloader>
 <os>
 <type>linux</type>
 </os>
 <clock offset=''utc''/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>restart</on_crash>
 <devices>
 <disk type=''file'' device=''disk''>
 <driver name=''file''/>
 <source file=''/root/vm/centos-para/centos-para.img''/>
 <target dev=''xvda'' bus=''xen''/>
 </disk>
 <interface type=''bridge''>
 <mac address=''00:16:3e:29:e4:9c''/>
 <source bridge=''eth0''/>
 <script path=''/etc/xen/scripts/vif-bridge''/>
 <target dev=''vif12.0''/>
 </interface>
 <console type=''pty'' tty=''/dev/pts/2''>
 <source path=''/dev/pts/2''/>
 <target port=''0''/>
 </console>
 </devices>
</domain>
 is there anyone could help me please？ i‘v googled lots of stuff but
nothing helped.


sa wang

2012-06-07
------------------------------
  --------------------------------------------------
Wang Sa（王卅）,Ph,D candidate
Technology Center of Software Engineering
Institute of Software, Chinese Academy of Sciences
P.O.Box 8718, Beijing 100190, China


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

Reasonably Related Threads

Search for more reasonably related threads

Xen users - Jun 2012 - network is only connected for a while when the domU is started

network is only connected for a while when the domU is started

network is only connected for a while when the domU is started

Reasonably Related Threads