From: Ivan Peikov <vanio@netclime.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: No route to localhost in virtual domains
Date: Wed, 23 Feb 2005 17:25:29 +0200 [thread overview]
Message-ID: <200502231725.29633.vanio@netclime.com> (raw)
In-Reply-To: <200502231706.38982.vanio@netclime.com>
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
prev parent reply other threads:[~2005-02-23 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 15:06 No route to localhost in virtual domains Ivan Peikov
2005-02-23 15:25 ` Ivan Peikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200502231725.29633.vanio@netclime.com \
--to=vanio@netclime.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.