Hi!
I''m running Xen 2.0.4 over patched 2.6.10 kernel and have problem with
routing
to loopback interface in virtual domains (can''t ping 127.0.0.1). Here
is how
it looks:
--------------
root@vm1:/tmp# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:5F:BB:9C
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:171856 errors:0 dropped:0 overruns:0 frame:0
TX packets:160196 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37456710 (35.7 Mb) TX bytes:51323199 (48.9 Mb)
lo Link encap:Local Loopback
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@vm1:/tmp# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default rtr.bg.nc 0.0.0.0 UG 0 0 0 eth0
--------------
When I attempt to add the route manually I get this:
--------------
root@vm1:/tmp# /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
SIOCADDRT: No such device
--------------
Routing through eth0 works fine.
Should I somehow export the loopback interface to virtual domains and how?
While still on the topic, I''d like to ask another (probably stupid)
networking
question.
I still can''t get the dom0''s network running. When virtual
machines get
started and xen-br0 bridge gets up, the MAC address of my NIC gets associated
with the bridge and no matter what I do, I can''t route no packets to
and from
dom0''s eth0 inteface. All the other virtual domains have no such
problem. Any
idea how do I solve this?
Thanks!!
Regards,
Ivan Peikov
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Ivan Peikov
2005-Feb-23 15:25 UTC
Re: [Xen-devel] No route to localhost in virtual domains
Hi again! Sorry for the first stupid question - while reading my email I saw that I didn''t give 127.0.0.1 IP to lo interface. Still the problem with domain0''s network persists. Any help would be greatly appreciated!! Thanks again! Regards, Ivan Peikov On Wednesday 23 February 2005 17:06, Ivan Peikov wrote:> Hi! > I''m running Xen 2.0.4 over patched 2.6.10 kernel and have problem with > routing to loopback interface in virtual domains (can''t ping 127.0.0.1). > Here is how it looks: > > -------------- > root@vm1:/tmp# ifconfig > eth0 Link encap:Ethernet HWaddr AA:00:00:5F:BB:9C > inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:171856 errors:0 dropped:0 overruns:0 frame:0 > TX packets:160196 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:37456710 (35.7 Mb) TX bytes:51323199 (48.9 Mb) > > lo Link encap:Local Loopback > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > root@vm1:/tmp# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface 192.168.0.0 * 255.255.255.0 U 0 0 > 0 eth0 default rtr.bg.nc 0.0.0.0 UG 0 0 > 0 eth0 -------------- > > When I attempt to add the route manually I get this: > > -------------- > root@vm1:/tmp# /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo > SIOCADDRT: No such device > -------------- > > Routing through eth0 works fine. > Should I somehow export the loopback interface to virtual domains and how? > > While still on the topic, I''d like to ask another (probably stupid) > networking question. > I still can''t get the dom0''s network running. When virtual machines get > started and xen-br0 bridge gets up, the MAC address of my NIC gets > associated with the bridge and no matter what I do, I can''t route no > packets to and from dom0''s eth0 inteface. All the other virtual domains > have no such problem. Any idea how do I solve this? > > Thanks!! > > Regards, > Ivan Peikov > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel