WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] domU network doesn't get IP

To: Edward Dunagin <edunagin@xxxxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU network doesn't get IP
From: Jayesh Salvi <jayeshsalvi@xxxxxxxxx>
Date: Tue, 3 Jan 2006 12:28:48 +1800
Delivery-date: Mon, 02 Jan 2006 18:33:52 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jcJ7QHz0wQDTB4Nq6lvU3Ftw3B5l1EoYZkszr8qjMydNV1ZhjyfK3XCvOLgQmdebUx2elpQKHnbPqo6AzlYvkrHH4AIGz63fsEs18z3dJHOZ3T6z3qpe+QFdonG94w0r/x8YsHr5u3+YcC6qfQat86gWjWrKa9RSGaNCQ1wKcg8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2af451740601021000i7e39b624l7e73be2e268d1cdf@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <871640aa0601020941h6861b505vb83c5c7ec1f73d59@xxxxxxxxxxxxxx> <2af451740601021000i7e39b624l7e73be2e268d1cdf@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Edward, I checked my firewall. It was already disabled. I also tried with SELinux disabled and enabled (just in case), but that also made no difference.

On 1/3/06, Edward Dunagin <edunagin@xxxxxxxxx> wrote:
try stopping your firewall.

On 1/2/06, Jayesh Salvi < jayeshsalvi@xxxxxxxxx> wrote:
Hi,

I have started domU successfully. I am using the default xend-config.sxp, it uses (network-script network-bridge). But my domU doesn't get any IP information, and it's disconnected from dom0 and rest of the world.

While booting domU, I get the following message:
...
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0... failed.
[FAILED]
....

At the same time, my /var/log/xen- hotplug.log records:

xenstore-read: couldn't read path backend/vbd/5/777/physical-device
xenstore-read: couldn't read path backend/vif/5/0/ip
xenstore-read: couldn't read path backend/vif/5/0/bridge
xenstore-read: couldn't read path backend/vbd/5/777/physical-device

My xm top looks like:
xentop - 11:34:45   Xen 3.0.0
2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 654652k total, 591216k used, 63436k free    CPUs: 1 @ 1295MHz
      NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) SSID
  Domain-0 -----r       3598    2.1     505872   77.3   no limit       n/a     1    8     5484    73881    0
Net0 RX: 75654769bytes   822377pkts        0err        0drop  TX:  5616372bytes    25553pkts        0err        0drop
Net1 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net2 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net3 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net4 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net5 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net6 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
Net7 RX:        0bytes        0pkts        0err        0drop  TX:        0bytes        0pkts        0err        0drop
  MyDomain --b---         14    0.0      65508   10.0      65536      10.0     1    1        2     1547    0
Net0 RX:  1584924bytes    24430pkts        0err      701drop  TX:     2394bytes        7pkts        0err        0drop

My ifconfig look like:
(Also I don't understand where the domU gets its MAC address 00:16:3E:56:79:71? Could anyone explain that as well?)
On domU -
[root@localhost netplug]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:56:79:71
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25470 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1652542 (1.5 MiB)  TX bytes:2394 (2.3 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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

On dom0 -
[root@orion xen]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0B:DB:DA:D6:42
          inet addr: 24.118.198.46  Bcast: 255.255.255.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:823139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25570 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:75712922 (72.2 MiB)  TX bytes:5620455 ( 5.3 MiB)

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:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32709 (31.9 KiB)  TX bytes:32709 (31.9 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:823121 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25587 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:79025183 (75.3 MiB)  TX bytes:5767221 (5.5 MiB)
          Interrupt:11

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25570 errors:0 dropped:0 overruns:0 frame:0
          TX packets:823139 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5620455 (5.3 MiB)  TX bytes:75712922 ( 72.2 MiB)

vif5.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25173 errors:0 dropped:704 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2394 (2.3 KiB)  TX bytes:1632487 (1.5 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:793251 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:40130862 (38.2 MiB)  TX bytes:0 ( 0.0 b)


pings from domU to outside world/dom0 IP fail.

I read networking issues in archives and other tutorials, but haven't yet found any solution.

Can anyone tell me what might be going wrong? Or at least where should I look to probe further?

Thanks a lot.

Jayesh

--
Jayesh


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




--
Edward Dunagin
4646 Glenwood Drive
Bozeman, MT 59718
mobile 406-570-0992



--
Jayesh

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>