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@lists.xensource.com
http://lists.xensource.com/xen-users
>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. Try to manually configure the eth0 inside domU and see if it helps.>(Also I don''t understand where the domU gets its MAC address00:16:3E:56:79:71? Could >anyone explain that as well?) You can setup a custom mac address by using the option vif [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. Substitute the mac address after the mac= for the desired mac address. -- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> wrote:> > try stopping your firewall. > > On 1/2/06, Jayesh Salvi <jayeshsalvi@gmail.com> 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@lists.xensource.com > > 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@lists.xensource.com http://lists.xensource.com/xen-users
> Try to manually configure the eth0 inside domU and see if it helps.Sorry, I don''t know exactly how to do it. Could you elaborate on how to manually configure eth0? Thanks for pointing out the custom mac address question. Can anyone tell me about these error messages from xend-hotplug.log 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 [After I shutdown the domain I further get] xenstore-read: couldn''t read path backend/vif/5/0/ip xenstore-read: couldn''t read path backend/vif/5/0/bridge interface vif5.0 does not exist! I think "couldn''t read path backend/vif/5/0/ip " should really have to do with this IP problem. But I don''t understand which path is this? Is it a path somewhere on root file system? On 1/3/06, Anand <xen.mails@gmail.com> wrote:> > >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. > > Try to manually configure the eth0 inside domU and see if it helps. > > >(Also I don''t understand where the domU gets its MAC address > 00:16:3E:56:79:71? Could >anyone explain that as well?) > > You can setup a custom mac address by using the option vif > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. > Substitute the mac address after the mac= for the desired mac address. > > -- > > regards, > > Anand-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Make sure your firewall is disabled. Disable selinux. Manual configuration of eth0 can be done as follows: ifconfig eth0 192.168.1.1 netmask 255.255.255.0 ifconfig eth0 up Now try to ping the interface. Which version of xen are you using ? On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > > Try to manually configure the eth0 inside domU and see if it helps. > Sorry, I don''t know exactly how to do it. Could you elaborate on how to > manually configure eth0? > > Thanks for pointing out the custom mac address question. > > Can anyone tell me about these error messages from xend-hotplug.log > > 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 > [After I shutdown the domain I further get] > xenstore-read: couldn''t read path backend/vif/5/0/ip > xenstore-read: couldn''t read path backend/vif/5/0/bridge > interface vif5.0 does not exist! > > I think "couldn''t read path backend/vif/5/0/ip " should really have to do > with this IP problem. But I don''t understand which path is this? Is it a > path somewhere on root file system? > On 1/3/06, Anand <xen.mails@gmail.com> wrote: > > > > >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. > > > > Try to manually configure the eth0 inside domU and see if it helps. > > > > >(Also I don''t understand where the domU gets its MAC address > > 00:16:3E:56:79:71? Could >anyone explain that as well?) > > > > You can setup a custom mac address by using the option vif > > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. > > Substitute the mac address after the mac= for the desired mac address. > > > > -- > > > > regards, > > > > Anand > > > > > -- > Jayesh > >-- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
OK. Now both firewall and SELinux are disabled. I created a domU with MAC
AA:00:00:00:00:11.
Then I did manual configuration of eth0 as you told.
Here is the trace:
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:895 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:58557 (57.1 KiB) 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)
[root@localhost ~]# ifconfig eth0 192.168.1.1 netmask 255.255.255.0
[root@localhost ~]# ifconfig eth0 up
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1191 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:78311 (76.4 KiB) TX bytes:2436 (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)
Even after this I can''t see dom0 from domU. My dom0''s IP is
24.118.198.46
So when I ping my dom0 from domU, I can''t reach it:
[root@localhost ~]# ping 24.118.198.46
connect: Network is unreachable
When I ping the IP address 192.168.1.1 from dom0, I get
[root@orion xen]# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.>From 10.230.64.1 icmp_seq=3 Packet filtered
>From 10.230.64.1 icmp_seq=6 Packet filtered
>From 10.230.64.1 icmp_seq=8 Packet filtered
--- 192.168.1.1 ping statistics ---
11 packets transmitted, 0 received, +3 errors, 100% packet loss, time
10137ms
, pipe 2
Thanks Anand for your suggestions so far.
I want to clarify few more thing:
In my domain config file, I now set mac address myself, instead of default.
So my vif is now:
vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ]
What about DHCP option? Should I turn it on/off? I tried it both ways, but
that didn''t help - my dom0 gets its IP by DHCP from my ISP provider.
I don''t set nics, because by default it is 1.
I also don''t set netmask, gateway, hostname in my domain config file.
Should
I set these variables?
Let me know.
Thanks,
Jayesh
On 1/3/06, Anand <xen.mails@gmail.com> wrote:>
> Make sure your firewall is disabled. Disable selinux.
>
> Manual configuration of eth0 can be done as follows:
>
> ifconfig eth0 192.168.1.1 netmask 255.255.255.0
>
> ifconfig eth0 up
>
> Now try to ping the interface.
>
> Which version of xen are you using ?
>
> On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote:
> >
> > > Try to manually configure the eth0 inside domU and see if it
helps.
> > Sorry, I don''t know exactly how to do it. Could you elaborate
on how to
> > manually configure eth0?
> >
> > Thanks for pointing out the custom mac address question.
> >
> > Can anyone tell me about these error messages from xend-hotplug.log
> >
> > 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
> > [After I shutdown the domain I further get]
> > xenstore-read: couldn''t read path backend/vif/5/0/ip
> > xenstore-read: couldn''t read path backend/vif/5/0/bridge
> > interface vif5.0 does not exist!
> >
> > I think "couldn''t read path backend/vif/5/0/ip "
should really have to
> > do with this IP problem. But I don''t understand which path is
this? Is it a
> > path somewhere on root file system?
> > On 1/3/06, Anand < xen.mails@gmail.com> wrote:
> > >
> > > >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.
> > >
> > > Try to manually configure the eth0 inside domU and see if it
helps.
> > >
> > > >(Also I don''t understand where the domU gets its MAC
address
> > > 00:16:3E:56:79:71? Could >anyone explain that as well?)
> > >
> > > You can setup a custom mac address by using the option vif >
> > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the
domU config file.
> > > Substitute the mac address after the mac= for the desired mac
address.
> > >
> > > --
> > >
> > > regards,
> > >
> > > Anand
> >
> >
> >
> >
> > --
> > Jayesh
> >
> >
>
>
> --
>
> regards,
>
> Anand
--
Jayesh
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
And yes I am using Xen 3.0 On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > OK. Now both firewall and SELinux are disabled. I created a domU with MAC > AA:00:00:00:00:11. > Then I did manual configuration of eth0 as you told. > Here is the trace: > [root@localhost ~]# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:895 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:58557 (57.1 KiB) 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) > > [root@localhost ~]# ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > [root@localhost ~]# ifconfig eth0 up > [root@localhost ~]# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1191 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:78311 (76.4 KiB) TX bytes:2436 (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) > > > Even after this I can''t see dom0 from domU. My dom0''s IP is 24.118.198.46 > > So when I ping my dom0 from domU, I can''t reach it: > [root@localhost ~]# ping 24.118.198.46 > connect: Network is unreachable > > When I ping the IP address 192.168.1.1 from dom0, I get > [root@orion xen]# ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > From 10.230.64.1 icmp_seq=3 Packet filtered > From 10.230.64.1 icmp_seq=6 Packet filtered > From 10.230.64.1 icmp_seq=8 Packet filtered > > --- 192.168.1.1 ping statistics --- > 11 packets transmitted, 0 received, +3 errors, 100% packet loss, time > 10137ms > , pipe 2 > > Thanks Anand for your suggestions so far. > > I want to clarify few more thing: > In my domain config file, I now set mac address myself, instead of > default. So my vif is now: > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] > What about DHCP option? Should I turn it on/off? I tried it both ways, but > that didn''t help - my dom0 gets its IP by DHCP from my ISP provider. > I don''t set nics, because by default it is 1. > I also don''t set netmask, gateway, hostname in my domain config file. > Should I set these variables? > > Let me know. > Thanks, > Jayesh > On 1/3/06, Anand <xen.mails@gmail.com> wrote: > > > > Make sure your firewall is disabled. Disable selinux. > > > > Manual configuration of eth0 can be done as follows: > > > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > > > > ifconfig eth0 up > > > > Now try to ping the interface. > > > > Which version of xen are you using ? > > > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote: > > > > > > > Try to manually configure the eth0 inside domU and see if it helps. > > > Sorry, I don''t know exactly how to do it. Could you elaborate on how > > > to manually configure eth0? > > > > > > Thanks for pointing out the custom mac address question. > > > > > > Can anyone tell me about these error messages from xend-hotplug.log > > > > > > 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 > > > [After I shutdown the domain I further get] > > > xenstore-read: couldn''t read path backend/vif/5/0/ip > > > xenstore-read: couldn''t read path backend/vif/5/0/bridge > > > interface vif5.0 does not exist! > > > > > > I think "couldn''t read path backend/vif/5/0/ip " should really have > > > to do with this IP problem. But I don''t understand which path is this? Is > > > it a path somewhere on root file system? > > > On 1/3/06, Anand < xen.mails@gmail.com> wrote: > > > > > > > > >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. > > > > > > > > Try to manually configure the eth0 inside domU and see if it helps. > > > > > > > > >(Also I don''t understand where the domU gets its MAC address > > > > 00:16:3E:56:79:71? Could >anyone explain that as well?) > > > > > > > > You can setup a custom mac address by using the option vif > > > > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. > > > > Substitute the mac address after the mac= for the desired mac address. > > > > > > > > -- > > > > > > > > regards, > > > > > > > > Anand > > > > > > > > > > > > > > > -- > > > Jayesh > > > > > > > > > > > > -- > > > > regards, > > > > Anand > > > > > -- > Jayesh > >-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The 192.168.1.1 was an example. You should use the ip address which you wanted to assign to the interface (and provided to you by your isp). Also ensure that proper gateway is setup inside /etc/sysconfig/network-scripts/ifcfg-eth0. No need for dhcp if you want to assign a static ip. The hostname and other options are not required. On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > OK. Now both firewall and SELinux are disabled. I created a domU with MAC > AA:00:00:00:00:11. > Then I did manual configuration of eth0 as you told. > Here is the trace: > [root@localhost ~]# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:895 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:58557 (57.1 KiB) 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) > > [root@localhost ~]# ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > [root@localhost ~]# ifconfig eth0 up > [root@localhost ~]# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1191 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:78311 (76.4 KiB) TX bytes:2436 (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) > > > Even after this I can''t see dom0 from domU. My dom0''s IP is 24.118.198.46 > > So when I ping my dom0 from domU, I can''t reach it: > [root@localhost ~]# ping 24.118.198.46 > connect: Network is unreachable > > When I ping the IP address 192.168.1.1 from dom0, I get > [root@orion xen]# ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > From 10.230.64.1 icmp_seq=3 Packet filtered > From 10.230.64.1 icmp_seq=6 Packet filtered > From 10.230.64.1 icmp_seq=8 Packet filtered > > --- 192.168.1.1 ping statistics --- > 11 packets transmitted, 0 received, +3 errors, 100% packet loss, time > 10137ms > , pipe 2 > > Thanks Anand for your suggestions so far. > > I want to clarify few more thing: > In my domain config file, I now set mac address myself, instead of > default. So my vif is now: > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] > What about DHCP option? Should I turn it on/off? I tried it both ways, but > that didn''t help - my dom0 gets its IP by DHCP from my ISP provider. > I don''t set nics, because by default it is 1. > I also don''t set netmask, gateway, hostname in my domain config file. > Should I set these variables? > > Let me know. > Thanks, > Jayesh > On 1/3/06, Anand <xen.mails@gmail.com> wrote: > > > > Make sure your firewall is disabled. Disable selinux. > > > > Manual configuration of eth0 can be done as follows: > > > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > > > > ifconfig eth0 up > > > > Now try to ping the interface. > > > > Which version of xen are you using ? > > > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote: > > > > > > > Try to manually configure the eth0 inside domU and see if it helps. > > > Sorry, I don''t know exactly how to do it. Could you elaborate on how > > > to manually configure eth0? > > > > > > Thanks for pointing out the custom mac address question. > > > > > > Can anyone tell me about these error messages from xend-hotplug.log > > > > > > 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 > > > [After I shutdown the domain I further get] > > > xenstore-read: couldn''t read path backend/vif/5/0/ip > > > xenstore-read: couldn''t read path backend/vif/5/0/bridge > > > interface vif5.0 does not exist! > > > > > > I think "couldn''t read path backend/vif/5/0/ip " should really have > > > to do with this IP problem. But I don''t understand which path is this? Is > > > it a path somewhere on root file system? > > > On 1/3/06, Anand < xen.mails@gmail.com> wrote: > > > > > > > > >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. > > > > > > > > Try to manually configure the eth0 inside domU and see if it helps. > > > > > > > > >(Also I don''t understand where the domU gets its MAC address > > > > 00:16:3E:56:79:71? Could >anyone explain that as well?) > > > > > > > > You can setup a custom mac address by using the option vif > > > > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. > > > > Substitute the mac address after the mac= for the desired mac address. > > > > > > > > -- > > > > > > > > regards, > > > > > > > > Anand > > > > > > > > > > > > > > > -- > > > Jayesh > > > > > > > > > > > > -- > > > > regards, > > > > Anand > > > > > -- > Jayesh > >-- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yeah, I thought 192.168.*.* are private addresses so any will do. My ISP has
provided me a single IP address that too dynamic, so I guess I can only use
IP addresses that are reserved for private use. So now I am using
192.168.20.20 (maybe 192.168.1.1 is a special (router) address, not sure)
In addition, I tried some other thing. Instead of configuring eth0 from
inside domU I configured vifx.0 from dom0. So it looked like:
[root@orion hotplug]# ifconfig vif11.0 192.168.20.20 netmask 255.255.254.0
(I used this netmask because that''s what is set in my dom0)
[root@orion hotplug]# ifconfig vif11.0 up
[root@orion hotplug]# ifconfig
...
vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.20.20 Bcast:192.168.21.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:2169 errors:0 dropped:164 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1878 (1.8 KiB) TX bytes:141298 (137.9 KiB)
...
I had also updated /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:
[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
GATEWAY=24.118.198.1
IPADDR=192.168.20.20
NETMASK=255.255.254.0
Then the ping of domU from dom0 was successful, but telnet failed:
[root@orion hotplug]# ping 192.168.20.20
PING 192.168.20.20 (192.168.20.20) 56(84) bytes of data.
64 bytes from 192.168.20.20: icmp_seq=0 ttl=64 time=0.046 ms
64 bytes from 192.168.20.20: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 192.168.20.20: icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from 192.168.20.20: icmp_seq=3 ttl=64 time=0.039 ms
64 bytes from 192.168.20.20: icmp_seq=4 ttl=64 time=0.038 ms
--- 192.168.20.20 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4017ms
rtt min/avg/max/mdev = 0.031/0.038/0.046/0.006 ms, pipe 2
[root@orion hotplug]# telnet 192.168.20.20
Trying 192.168.20.20...
telnet: connect to address 192.168.20.20: Connection refused
telnet: Unable to connect to remote host: Connection refused
And this did not help the view from within domU. It still has network
unreachable.
Thanks for giving the idea about ifcfg-eth0.
Jayesh
On 1/3/06, Anand <xen.mails@gmail.com> wrote:>
> The 192.168.1.1 was an example. You should use the ip address which you
> wanted to assign to the interface (and provided to you by your isp).
>
> Also ensure that proper gateway is setup inside
> /etc/sysconfig/network-scripts/ifcfg-eth0.
>
> No need for dhcp if you want to assign a static ip. The hostname and other
> options are not required.
>
> On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote:
> >
> > OK. Now both firewall and SELinux are disabled. I created a domU with
> > MAC AA:00:00:00:00:11.
> > Then I did manual configuration of eth0 as you told.
> > Here is the trace:
> > [root@localhost ~]# ifconfig
> > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:895 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:58557 (57.1 KiB) 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)
> >
> > [root@localhost ~]# ifconfig eth0 192.168.1.1 netmask 255.255.255.0
> > [root@localhost ~]# ifconfig eth0 up
> > [root@localhost ~]# ifconfig
> > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
> > inet addr:192.168.1.1 Bcast: 192.168.1.255
Mask:255.255.255.0
> >
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1191 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:78311 (76.4 KiB) TX bytes:2436 (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)
> >
> >
> > Even after this I can''t see dom0 from domU. My
dom0''s IP is
> > 24.118.198.46
> >
> > So when I ping my dom0 from domU, I can''t reach it:
> > [root@localhost ~]# ping 24.118.198.46
> > connect: Network is unreachable
> >
> > When I ping the IP address 192.168.1.1 from dom0, I get
> > [root@orion xen]# ping 192.168.1.1
> > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> > From 10.230.64.1 icmp_seq=3 Packet filtered
> > From 10.230.64.1 icmp_seq=6 Packet filtered
> > From 10.230.64.1 icmp_seq=8 Packet filtered
> >
> > --- 192.168.1.1 ping statistics ---
> > 11 packets transmitted, 0 received, +3 errors, 100% packet loss, time
> > 10137ms
> > , pipe 2
> >
> > Thanks Anand for your suggestions so far.
> >
> > I want to clarify few more thing:
> > In my domain config file, I now set mac address myself, instead of
> > default. So my vif is now:
> > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ]
> > What about DHCP option? Should I turn it on/off? I tried it both ways,
> > but that didn''t help - my dom0 gets its IP by DHCP from my
ISP provider.
> > I don''t set nics, because by default it is 1.
> > I also don''t set netmask, gateway, hostname in my domain
config file.
> > Should I set these variables?
> >
> > Let me know.
> > Thanks,
> > Jayesh
> > On 1/3/06, Anand <xen.mails@gmail.com> wrote:
> > >
> > > Make sure your firewall is disabled. Disable selinux.
> > >
> > > Manual configuration of eth0 can be done as follows:
> > >
> > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0
> > >
> > > ifconfig eth0 up
> > >
> > > Now try to ping the interface.
> > >
> > > Which version of xen are you using ?
> > >
> > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote:
> > > >
> > > > > Try to manually configure the eth0 inside domU and see
if it
> > > > helps.
> > > > Sorry, I don''t know exactly how to do it. Could you
elaborate on how
> > > > to manually configure eth0?
> > > >
> > > > Thanks for pointing out the custom mac address question.
> > > >
> > > > Can anyone tell me about these error messages from
xend-hotplug.log
> > > >
> > > > 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
> > > > [After I shutdown the domain I further get]
> > > > xenstore-read: couldn''t read path
backend/vif/5/0/ip
> > > > xenstore-read: couldn''t read path
backend/vif/5/0/bridge
> > > > interface vif5.0 does not exist!
> > > >
> > > > I think "couldn''t read path backend/vif/5/0/ip
" should really have
> > > > to do with this IP problem. But I don''t understand
which path is this? Is
> > > > it a path somewhere on root file system?
> > > > On 1/3/06, Anand < xen.mails@gmail.com> wrote:
> > > > >
> > > > > >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.
> > > > >
> > > > > Try to manually configure the eth0 inside domU and see
if it
> > > > > helps.
> > > > >
> > > > > >(Also I don''t understand where the domU
gets its MAC address
> > > > > 00:16:3E:56:79:71? Could >anyone explain that as
well?)
> > > > >
> > > > > You can setup a custom mac address by using the option
vif > > > > > [''mac=FF:FE:00:18:98:FB,
bridge=xenbr0''] inside the domU config file.
> > > > > Substitute the mac address after the mac= for the
desired mac address.
> > > > >
> > > > > --
> > > > >
> > > > > regards,
> > > > >
> > > > > Anand
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jayesh
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > regards,
> > >
> > > Anand
> >
> >
> >
> >
> > --
> > Jayesh
> >
> >
>
>
> --
>
> regards,
>
> Anand
--
Jayesh
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
You need to setup eth0 from inside domU and not from outside. Here is a sample ifcfg-eth0 for your domU. I still errors in your ifcfg-eth0 for domU. TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes BROADCAST=192.168.1.255 IPADDR=192.168.1.240 NETMASK=255.255.255.0 NETWORK=192.168.1.0 GATEWAY=192.168.1.1 Substitute the ip address you want to allocate to the domU in the above settings. On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > Yeah, I thought 192.168.*.* are private addresses so any will do. My ISP > has provided me a single IP address that too dynamic, so I guess I can only > use IP addresses that are reserved for private use. So now I am using > 192.168.20.20 (maybe 192.168.1.1 is a special (router) address, not sure) > > In addition, I tried some other thing. Instead of configuring eth0 from > inside domU I configured vifx.0 from dom0. So it looked like: > > [root@orion hotplug]# ifconfig vif11.0 192.168.20.20 netmask 255.255.254.0 > (I used this netmask because that''s what is set in my dom0) > [root@orion hotplug]# ifconfig vif11.0 up > [root@orion hotplug]# ifconfig > ... > vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:192.168.20.20 Bcast: 192.168.21.255 Mask: > 255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:9 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2169 errors:0 dropped:164 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1878 (1.8 KiB) TX bytes:141298 (137.9 KiB) > ... > > I had also updated /etc/sysconfig/network-scripts/ifcfg-eth0 as follows: > [root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > TYPE=Ethernet > GATEWAY=24.118.198.1 > IPADDR= 192.168.20.20 > NETMASK=255.255.254.0 > > > Then the ping of domU from dom0 was successful, but telnet failed: > [root@orion hotplug]# ping 192.168.20.20 > PING 192.168.20.20 (192.168.20.20) 56(84) bytes of data. > 64 bytes from 192.168.20.20: icmp_seq=0 ttl=64 time= 0.046 ms > 64 bytes from 192.168.20.20: icmp_seq=1 ttl=64 time=0.031 ms > 64 bytes from 192.168.20.20: icmp_seq=2 ttl=64 time=0.037 ms > 64 bytes from 192.168.20.20: icmp_seq=3 ttl=64 time=0.039 ms > 64 bytes from 192.168.20.20: icmp_seq=4 ttl=64 time=0.038 ms > > --- 192.168.20.20 ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 4017ms > rtt min/avg/max/mdev = 0.031/0.038/0.046/0.006 ms, pipe 2 > [root@orion hotplug]# telnet 192.168.20.20 > Trying 192.168.20.20... > telnet: connect to address 192.168.20.20: Connection refused > telnet: Unable to connect to remote host: Connection refused > > And this did not help the view from within domU. It still has network > unreachable. > > Thanks for giving the idea about ifcfg-eth0. > > Jayesh > > On 1/3/06, Anand <xen.mails@gmail.com> wrote: > > > > The 192.168.1.1 was an example. You should use the ip address which you > > wanted to assign to the interface (and provided to you by your isp). > > > > Also ensure that proper gateway is setup inside > > /etc/sysconfig/network-scripts/ifcfg-eth0. > > > > No need for dhcp if you want to assign a static ip. The hostname and > > other options are not required. > > > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote: > > > > > > OK. Now both firewall and SELinux are disabled. I created a domU with > > > MAC AA:00:00:00:00:11. > > > Then I did manual configuration of eth0 as you told. > > > Here is the trace: > > > [root@localhost ~]# ifconfig > > > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:895 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:58557 (57.1 KiB) 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) > > > > > > [root@localhost ~]# ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > > > [root@localhost ~]# ifconfig eth0 up > > > [root@localhost ~]# ifconfig > > > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > > > inet addr:192.168.1.1 Bcast: 192.168.1.255 Mask:255.255.255.0 > > > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:1191 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:78311 (76.4 KiB) TX bytes:2436 (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) > > > > > > > > > Even after this I can''t see dom0 from domU. My dom0''s IP is > > > 24.118.198.46 > > > > > > So when I ping my dom0 from domU, I can''t reach it: > > > [root@localhost ~]# ping 24.118.198.46 > > > connect: Network is unreachable > > > > > > When I ping the IP address 192.168.1.1 from dom0, I get > > > [root@orion xen]# ping 192.168.1.1 > > > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > > > From 10.230.64.1 icmp_seq=3 Packet filtered > > > From 10.230.64.1 icmp_seq=6 Packet filtered > > > From 10.230.64.1 icmp_seq=8 Packet filtered > > > > > > --- 192.168.1.1 ping statistics --- > > > 11 packets transmitted, 0 received, +3 errors, 100% packet loss, time > > > 10137ms > > > , pipe 2 > > > > > > Thanks Anand for your suggestions so far. > > > > > > I want to clarify few more thing: > > > In my domain config file, I now set mac address myself, instead of > > > default. So my vif is now: > > > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] > > > What about DHCP option? Should I turn it on/off? I tried it both ways, > > > but that didn''t help - my dom0 gets its IP by DHCP from my ISP provider. > > > I don''t set nics, because by default it is 1. > > > I also don''t set netmask, gateway, hostname in my domain config file. > > > Should I set these variables? > > > > > > Let me know. > > > Thanks, > > > Jayesh > > > On 1/3/06, Anand <xen.mails@gmail.com> wrote: > > > > > > > > Make sure your firewall is disabled. Disable selinux. > > > > > > > > Manual configuration of eth0 can be done as follows: > > > > > > > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0 > > > > > > > > ifconfig eth0 up > > > > > > > > Now try to ping the interface. > > > > > > > > Which version of xen are you using ? > > > > > > > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote: > > > > > > > > > > > Try to manually configure the eth0 inside domU and see if it > > > > > helps. > > > > > Sorry, I don''t know exactly how to do it. Could you elaborate on > > > > > how to manually configure eth0? > > > > > > > > > > Thanks for pointing out the custom mac address question. > > > > > > > > > > Can anyone tell me about these error messages from > > > > > xend-hotplug.log > > > > > > > > > > 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 > > > > > [After I shutdown the domain I further get] > > > > > xenstore-read: couldn''t read path backend/vif/5/0/ip > > > > > xenstore-read: couldn''t read path backend/vif/5/0/bridge > > > > > interface vif5.0 does not exist! > > > > > > > > > > I think "couldn''t read path backend/vif/5/0/ip " should really > > > > > have to do with this IP problem. But I don''t understand which path is this? > > > > > Is it a path somewhere on root file system? > > > > > On 1/3/06, Anand < xen.mails@gmail.com> wrote: > > > > > > > > > > > > >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. > > > > > > > > > > > > Try to manually configure the eth0 inside domU and see if it > > > > > > helps. > > > > > > > > > > > > >(Also I don''t understand where the domU gets its MAC address > > > > > > 00:16:3E:56:79:71? Could >anyone explain that as well?) > > > > > > > > > > > > You can setup a custom mac address by using the option vif > > > > > > [''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU config file. > > > > > > Substitute the mac address after the mac= for the desired mac address. > > > > > > > > > > > > -- > > > > > > > > > > > > regards, > > > > > > > > > > > > Anand > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Jayesh > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > regards, > > > > > > > > Anand > > > > > > > > > > > > > > > -- > > > Jayesh > > > > > > > > > > > > -- > > > > regards, > > > > Anand > > > > > -- > Jayesh > >-- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks to your sample file, I got a little success.
I used those values in my ifcfg-eth0, and one first reboot it did not work.
Then I changed IP address to something else and halted domU, started again
and it gave error even before:
Bringing up interface eth0: RTNETLINK answers: Network is unreachable
[ OK ]
So I reverted the change of IP address, halted domU and started again. And
now I think the changes have taken effect. Immediately after booting up, if
I do ifconfig, I see the IP address assigned:
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
inet addr:192.168.1.240 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:250 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16907 (16.5 KiB) TX bytes:210 (210.0 b)
However pings still fail. Ping from dom0 to domU fails as before. ping from
domU to outside world at least sends some packets and then says host
unreachable.
[root@localhost ~]# ping 24.118.198.46
PING 24.118.198.46 (24.118.198.46) 56(84) bytes of data.>From 192.168.1.240 icmp_seq=0 Destination Host Unreachable
>From 192.168.1.240 icmp_seq=1 Destination Host Unreachable
Previously it used to just say network unreachable. I think it has to do
with the IP assignment.
Thanks Anand for patiently following this thread :)
I will post more updates as I play around. If you have any more ideas,
kindly suggest.
Thanks,
Jayesh
On 1/3/06, Anand <xen.mails@gmail.com> wrote:>
> You need to setup eth0 from inside domU and not from outside.
>
> Here is a sample ifcfg-eth0 for your domU. I still errors in your
> ifcfg-eth0 for domU.
>
> TYPE=Ethernet
> DEVICE=eth0
> BOOTPROTO=static
> ONBOOT=yes
> BROADCAST=192.168.1.255
> IPADDR=192.168.1.240
> NETMASK=255.255.255.0
> NETWORK= 192.168.1.0
> GATEWAY=192.168.1.1
>
> Substitute the ip address you want to allocate to the domU in the above
> settings.
>
> On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:
> >
> > Yeah, I thought 192.168.*.* are private addresses so any will do. My
ISP
> > has provided me a single IP address that too dynamic, so I guess I can
only
> > use IP addresses that are reserved for private use. So now I am using
> > 192.168.20.20 (maybe 192.168.1.1 is a special (router) address, not
> > sure)
> >
> > In addition, I tried some other thing. Instead of configuring eth0
from
> > inside domU I configured vifx.0 from dom0. So it looked like:
> >
> > [root@orion hotplug]# ifconfig vif11.0 192.168.20.20 netmask
> > 255.255.254.0
> > (I used this netmask because that''s what is set in my dom0)
> > [root@orion hotplug]# ifconfig vif11.0 up
> > [root@orion hotplug]# ifconfig
> > ...
> > vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> > inet addr: 192.168.20.20 Bcast: 192.168.21.255
Mask:255.255.254.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:9 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2169 errors:0 dropped:164 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:1878 (1.8 KiB) TX bytes:141298 (137.9 KiB)
> > ...
> >
> > I had also updated /etc/sysconfig/network-scripts/ifcfg-eth0 as
follows:
> >
> > [root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
> > DEVICE=eth0
> > BOOTPROTO=none
> > ONBOOT=yes
> > TYPE=Ethernet
> > GATEWAY= 24.118.198.1
> > IPADDR= 192.168.20.20
> > NETMASK=255.255.254.0
> >
> >
> > Then the ping of domU from dom0 was successful, but telnet failed:
> > [root@orion hotplug]# ping 192.168.20.20
> > PING 192.168.20.20 ( 192.168.20.20) 56(84) bytes of data.
> > 64 bytes from 192.168.20.20: icmp_seq=0 ttl=64 time= 0.046 ms
> > 64 bytes from 192.168.20.20: icmp_seq=1 ttl=64 time=0.031 ms
> > 64 bytes from 192.168.20.20: icmp_seq=2 ttl=64 time=0.037 ms
> > 64 bytes from 192.168.20.20: icmp_seq=3 ttl=64 time=0.039 ms
> > 64 bytes from 192.168.20.20: icmp_seq=4 ttl=64 time=0.038 ms
> >
> > --- 192.168.20.20 ping statistics ---
> > 5 packets transmitted, 5 received, 0% packet loss, time 4017ms
> > rtt min/avg/max/mdev = 0.031/0.038/0.046/0.006 ms, pipe 2
> > [root@orion hotplug]# telnet 192.168.20.20
> > Trying 192.168.20.20...
> > telnet: connect to address 192.168.20.20: Connection refused
> > telnet: Unable to connect to remote host: Connection refused
> >
> > And this did not help the view from within domU. It still has network
> > unreachable.
> >
> > Thanks for giving the idea about ifcfg-eth0.
> >
> > Jayesh
> >
> > On 1/3/06, Anand < xen.mails@gmail.com> wrote:
> > >
> > > The 192.168.1.1 was an example. You should use the ip address
which
> > > you wanted to assign to the interface (and provided to you by
your isp).
> > >
> > > Also ensure that proper gateway is setup inside
> > > /etc/sysconfig/network-scripts/ifcfg-eth0.
> > >
> > > No need for dhcp if you want to assign a static ip. The hostname
and
> > > other options are not required.
> > >
> > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com> wrote:
> > > >
> > > > OK. Now both firewall and SELinux are disabled. I created a
domU
> > > > with MAC AA:00:00:00:00:11.
> > > > Then I did manual configuration of eth0 as you told.
> > > > Here is the trace:
> > > > [root@localhost ~]# ifconfig
> > > > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
> > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > > RX packets:895 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:58557 (57.1 KiB) 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)
> > > >
> > > > [root@localhost ~]# ifconfig eth0 192.168.1.1 netmask
255.255.255.0
> > > > [root@localhost ~]# ifconfig eth0 up
> > > > [root@localhost ~]# ifconfig
> > > > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11
> > > > inet addr:192.168.1.1 Bcast: 192.168.1.255
Mask:255.255.255.0
> > > >
> > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > > RX packets:1191 errors:0 dropped:0 overruns:0
frame:0
> > > > TX packets:8 errors:0 dropped:0 overruns:0
carrier:0
> > > > collisions:0 txqueuelen:1000
> > > > RX bytes:78311 (76.4 KiB) TX bytes:2436 (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)
> > > >
> > > >
> > > > Even after this I can''t see dom0 from domU. My
dom0''s IP is
> > > > 24.118.198.46
> > > >
> > > > So when I ping my dom0 from domU, I can''t reach it:
> > > > [root@localhost ~]# ping 24.118.198.46
> > > > connect: Network is unreachable
> > > >
> > > > When I ping the IP address 192.168.1.1 from dom0, I get
> > > > [root@orion xen]# ping 192.168.1.1
> > > > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> > > > From 10.230.64.1 icmp_seq=3 Packet filtered
> > > > From 10.230.64.1 icmp_seq=6 Packet filtered
> > > > From 10.230.64.1 icmp_seq=8 Packet filtered
> > > >
> > > > --- 192.168.1.1 ping statistics ---
> > > > 11 packets transmitted, 0 received, +3 errors, 100% packet
loss,
> > > > time 10137ms
> > > > , pipe 2
> > > >
> > > > Thanks Anand for your suggestions so far.
> > > >
> > > > I want to clarify few more thing:
> > > > In my domain config file, I now set mac address myself,
instead of
> > > > default. So my vif is now:
> > > > vif = [ ''mac=aa:00:00:00:00:11,
bridge=xenbr0'' ]
> > > > What about DHCP option? Should I turn it on/off? I tried it
both
> > > > ways, but that didn''t help - my dom0 gets its IP by
DHCP from my ISP
> > > > provider.
> > > > I don''t set nics, because by default it is 1.
> > > > I also don''t set netmask, gateway, hostname in my
domain config
> > > > file. Should I set these variables?
> > > >
> > > > Let me know.
> > > > Thanks,
> > > > Jayesh
> > > > On 1/3/06, Anand <xen.mails@gmail.com> wrote:
> > > > >
> > > > > Make sure your firewall is disabled. Disable selinux.
> > > > >
> > > > > Manual configuration of eth0 can be done as follows:
> > > > >
> > > > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0
> > > > >
> > > > > ifconfig eth0 up
> > > > >
> > > > > Now try to ping the interface.
> > > > >
> > > > > Which version of xen are you using ?
> > > > >
> > > > > On 1/3/06, Jayesh Salvi < jayeshsalvi@gmail.com>
wrote:
> > > > > >
> > > > > > > Try to manually configure the eth0 inside
domU and see if it
> > > > > > helps.
> > > > > > Sorry, I don''t know exactly how to do it.
Could you elaborate on
> > > > > > how to manually configure eth0?
> > > > > >
> > > > > > Thanks for pointing out the custom mac address
question.
> > > > > >
> > > > > > Can anyone tell me about these error messages from
> > > > > > xend-hotplug.log
> > > > > >
> > > > > > 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
> > > > > > [After I shutdown the domain I further get]
> > > > > > xenstore-read: couldn''t read path
backend/vif/5/0/ip
> > > > > > xenstore-read: couldn''t read path
backend/vif/5/0/bridge
> > > > > > interface vif5.0 does not exist!
> > > > > >
> > > > > > I think "couldn''t read path
backend/vif/5/0/ip " should really
> > > > > > have to do with this IP problem. But I
don''t understand which path is this?
> > > > > > Is it a path somewhere on root file system?
> > > > > > On 1/3/06, Anand < xen.mails@gmail.com>
wrote:
> > > > > > >
> > > > > > > >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.
> > > > > > >
> > > > > > > Try to manually configure the eth0 inside
domU and see if it
> > > > > > > helps.
> > > > > > >
> > > > > > > >(Also I don''t understand where
the domU gets its MAC address
> > > > > > > 00:16:3E:56:79:71? Could >anyone explain
that as well?)
> > > > > > >
> > > > > > > You can setup a custom mac address by using
the option vif > > > > > > >
[''mac=FF:FE:00:18:98:FB, bridge=xenbr0''] inside the domU
config file.
> > > > > > > Substitute the mac address after the mac= for
the desired mac address.
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > regards,
> > > > > > >
> > > > > > > Anand
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Jayesh
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > regards,
> > > > >
> > > > > Anand
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jayesh
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > regards,
> > >
> > > Anand
> >
> >
> >
> >
> > --
> > Jayesh
> >
> >
>
>
> --
>
> regards,
>
> Anand
--
Jayesh
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> If you are routing through the dom0 does it have forwarding enabled?This is interesting and something I don''t know. How do I check the forwarding? I will provide answer to your other questions when I get home. Thanks, Jayesh On 1/2/06, Ted Kaczmarek <tedkaz@optonline.net> wrote:> > On Tue, 2006-01-03 at 16:02 +0000, Jayesh Salvi wrote: > > Thanks to your sample file, I got a little success. > > > > I used those values in my ifcfg-eth0, and one first reboot it did not > > work. Then I changed IP address to something else and halted domU, > > started again and it gave error even before: > > Bringing up interface eth0: RTNETLINK answers: Network is unreachable > > [ OK ] > > What does "brctl show" return? > > What does xm network-list "ID of domU" return? > > Post the ifconfig from your domU and dom0? > > What does ping from the domU to its default gateway return? > > If you are routing through the dom0 does it have forwarding enabled? > > Also is you don''t top post it may get you better return on your smtp > packets. > > Regards, > Ted > > > >-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>What does "brctl show" return?[root@orion hotplug]# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif14.0>What does xm network-list "ID of domU" return?[root@orion hotplug]# xm network-list 14 (0 ((backend-id 0) (mac aa:00:00:00:00:11) (handle 0) (state 4) (backend /local/domain/0/backend/vif/14/0) (tx-ring-ref 521) (rx-ring-ref 522) (event-channel 7)))>Post the ifconfig from your domU and dom0? >From domU:[root@localhost ~]# ifconfig eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 inet addr:192.168.1.240 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:166249 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11139144 (10.6 MiB) TX bytes:1218 (1.1 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:41 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3888 (3.7 KiB) TX bytes:3888 (3.7 KiB)>From dom0:[root@orion hotplug]# 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:1131601 errors:0 dropped:0 overruns:0 frame:0 TX packets:45945 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:105704532 (100.8 MiB) TX bytes:11787028 (11.2 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:148 errors:0 dropped:0 overruns:0 frame:0 TX packets:148 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:33649 (32.8 KiB) TX bytes:33649 (32.8 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1131496 errors:0 dropped:0 overruns:0 frame:0 TX packets:46049 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:110279930 (105.1 MiB) TX bytes:12095888 (11.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:45945 errors:0 dropped:0 overruns:0 frame:0 TX packets:1131601 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11787028 (11.2 MiB) TX bytes:105704532 (100.8 MiB) vif14.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:166346 errors:0 dropped:2927 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1218 (1.1 KiB) TX bytes:11145961 (10.6 MiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1080611 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:55207509 (52.6 MiB) TX bytes:0 (0.0 b)>What does ping from the domU to its default gateway return?ping from domU to its gateway returns "Destination Host Unreachable">If you are routing through the dom0 does it have forwarding enabled?I think forwarding is not relevant in my case, because I am using bridging. Isn''t that right? Thanks, Jayesh On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > > If you are routing through the dom0 does it have forwarding enabled? > This is interesting and something I don''t know. How do I check the > forwarding? > > I will provide answer to your other questions when I get home. > Thanks, > Jayesh > > On 1/2/06, Ted Kaczmarek <tedkaz@optonline.net> wrote: > > > > On Tue, 2006-01-03 at 16:02 +0000, Jayesh Salvi wrote: > > > Thanks to your sample file, I got a little success. > > > > > > I used those values in my ifcfg-eth0, and one first reboot it did not > > > work. Then I changed IP address to something else and halted domU, > > > started again and it gave error even before: > > > Bringing up interface eth0: RTNETLINK answers: Network is unreachable > > > [ OK ] > > > > What does "brctl show" return? > > > > What does xm network-list "ID of domU" return? > > > > Post the ifconfig from your domU and dom0? > > > > What does ping from the domU to its default gateway return? > > > > If you are routing through the dom0 does it have forwarding enabled? > > > > Also is you don''t top post it may get you better return on your smtp > > packets. > > > > Regards, > > Ted > > > > > > > > > > > -- > Jayesh > >-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This things seems to be wrong. [root@orion hotplug]# brctl showmacs xenbr0 port no mac addr is local? ageing timer 1 00:0b:db:da:d6:42 no 33.21 2 00:0b:fc:40:1c:54 no 0.86 2 00:0b:fc:40:1c:a8 no 0.03 1 fe:ff:ff:ff:ff:ff yes 0.00 My domU''s MAC address is AA:00:00:00:00:11. The bridge doesn''t know about domU''s MAC at all. I am looking at the network-bridge script. Jayesh On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote:> > >What does "brctl show" return? > [root@orion hotplug]# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif14.0 > > >What does xm network-list "ID of domU" return? > [root@orion hotplug]# xm network-list 14 > (0 ((backend-id 0) (mac aa:00:00:00:00:11) (handle 0) (state 4) (backend > /local/domain/0/backend/vif/14/0) (tx-ring-ref 521) (rx-ring-ref 522) > (event-channel 7))) > > >Post the ifconfig from your domU and dom0? > From domU: > [root@localhost ~]# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:11 > inet addr:192.168.1.240 Bcast:192.168.1.255 Mask: > 255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:166249 errors:0 dropped:0 overruns:0 frame:0 > TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:11139144 (10.6 MiB) TX bytes:1218 (1.1 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:41 errors:0 dropped:0 overruns:0 frame:0 > TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3888 (3.7 KiB) TX bytes:3888 (3.7 KiB) > > From dom0: > [root@orion hotplug]# 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:1131601 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45945 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:105704532 (100.8 MiB) TX bytes:11787028 ( 11.2 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:148 errors:0 dropped:0 overruns:0 frame:0 > TX packets:148 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:33649 (32.8 KiB) TX bytes:33649 ( 32.8 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:1131496 errors:0 dropped:0 overruns:0 frame:0 > TX packets:46049 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:110279930 (105.1 MiB) TX bytes:12095888 (11.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:45945 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1131601 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:11787028 (11.2 MiB) TX bytes:105704532 ( 100.8 MiB) > > vif14.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:29 errors:0 dropped:0 overruns:0 frame:0 > TX packets:166346 errors:0 dropped:2927 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1218 (1.1 KiB) TX bytes:11145961 (10.6 MiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1080611 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:55207509 (52.6 MiB) TX bytes:0 ( 0.0 b) > > >What does ping from the domU to its default gateway return? > ping from domU to its gateway returns "Destination Host Unreachable" > > > >If you are routing through the dom0 does it have forwarding enabled? > I think forwarding is not relevant in my case, because I am using > bridging. Isn''t that right? > > Thanks, > Jayesh > > On 1/3/06, Jayesh Salvi <jayeshsalvi@gmail.com> wrote: > > > > > If you are routing through the dom0 does it have forwarding enabled? > > This is interesting and something I don''t know. How do I check the > > forwarding? > > > > I will provide answer to your other questions when I get home. > > Thanks, > > Jayesh > > > > On 1/2/06, Ted Kaczmarek < tedkaz@optonline.net> wrote: > > > > > > On Tue, 2006-01-03 at 16:02 +0000, Jayesh Salvi wrote: > > > > Thanks to your sample file, I got a little success. > > > > > > > > I used those values in my ifcfg-eth0, and one first reboot it did > > > not > > > > work. Then I changed IP address to something else and halted domU, > > > > started again and it gave error even before: > > > > Bringing up interface eth0: RTNETLINK answers: Network is > > > unreachable > > > > [ OK ] > > > > > > What does "brctl show" return? > > > > > > What does xm network-list "ID of domU" return? > > > > > > Post the ifconfig from your domU and dom0? > > > > > > What does ping from the domU to its default gateway return? > > > > > > If you are routing through the dom0 does it have forwarding enabled? > > > > > > Also is you don''t top post it may get you better return on your smtp > > > packets. > > > > > > Regards, > > > Ted > > > > > > > > > > > > > > > > > > -- > > Jayesh > > > > > > > -- > Jayesh > >-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Make sure port forwarding is on in dom0 echo 1 > /proc/sys/net/ipv4/ip_forward The above will enable port forwarding in dom0. -- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-01-03 at 23:38 +0000, Jayesh Salvi wrote:> This things seems to be wrong. > [root@orion hotplug]# brctl showmacs xenbr0 > port no mac addr is local? ageing timer > 1 00:0b:db:da:d6:42 no 33.21 > 2 00:0b:fc:40:1c:54 no 0.86 > 2 00:0b:fc:40:1c:a8 no 0.03 > 1 fe:ff:ff:ff:ff:ff yes 0.00 > > My domU''s MAC address is AA:00:00:00:00:11. The bridge doesn''t know > about domU''s MAC at all. I am looking at the network-bridge script.Please don''t top post. http://www.onysd.wednet.edu/internet_etiquette.html What happens if you put your domU in the same broadcast domain as your dom0? Try this before you start xend and bring up the dom0. On your dom0, "ifconfig eth0:1 192.168.1.241" (or whatever ip is available on that subnet). Start xend, fire up the domU, and from the domU ping the ip interface you created in the above line. Ted _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Try running dhclient inside the domU. regards, steve --------------------------------- Yahoo! DSL Something to write home about. Just $16.99/mo. or less _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> What happens if you put your domU in the same broadcast domain as your > dom0?It still can''t ping from domU to dom0. On your dom0, "ifconfig eth0:1 192.168.1.241" (or whatever ip is> available on that subnet). > > Start xend, fire up the domU, and from the domU ping the ip interface > you created in the above line.No. This didn''t work. I get ''Destination Host Unreachable'' when I ping from domU to the IP of eth0. However now that I have restarted dom0, and domU, my bridge doesn''t see my native mac address, but it does see vif''s mac address. [root@orion ~]# brctl showmacs xenbr0 port no mac addr is local? ageing timer 1 aa:00:00:00:00:11 no 234.48 1 fe:ff:ff:ff:ff:ff yes 0.00 My native mac is 00:0B:DB:DA:D6:42. vif''s mac is aa:00:00:00:00:11 . Thanks, Jayesh Ted> > >-- Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I resolved this issue. I could not get it working using network-bridge script, but NAT worked. So I changed the xend-config.sxp so that it would execute: (network-script network-nat) (vif-script vif-nat) Restarted xend, launched domU. I found that this script uses dhcp and vif interface got an IP address when seen from dom0. i.e. ''route -n'' from dom0 shows: [root@orion ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.8.1 0.0.0.0 255.255.255.255 UH 0 0 0 vif8.0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 24.118.198.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 24.118.198.1 0.0.0.0 UG 0 0 0 eth0 And I can ping to 10.0.8.1 even though my domU doesn''t have its IP yet. When I booted domU however it did not get the IP address at boot time. Determining IP information for eth0... failed. [FAILED] ifconfig showed eth0, but with now ip. So I manually assigned IP to eth0 by running: ifconfig eth0 10.0.8.1 netmask 255.255.255.0 Further I added a route in the IP routing table: route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.8.1 So now my IP table looks like: [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.8.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 lo 0.0.0.0 10.0.8.1 0.0.0.0 UG 0 0 0 eth0 Now I can ping to dom0 from domU, as well as I can ping to IPs of google and yahoo. So now domU can see the world. Interesting thing is, if I assign an IP of 10.0.8.20 to eth0 in domU and add a route ''route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.8.1'', that doesn''t work. pings won''t work to dom0. I will figure that out later. Thanks for all the suggestions. Jayesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users