hi,
i have made zero changes to the setup of the xend 2.0 code - everything
is as-is compiled from source off the sf.net site.
i ping 192.168.0.4 before starting /etc/init.d/xend, it hunky-dory.
i start xend: ping stops working as does everything else.
if i ping ftp.uk.debian.org, i get:
"eth0: received packet with own address as source address"
[including there being two spaces between with and own.]
yes, bridge is installed (no, i couldn't find any debian
packages for xen 2.0 so yes, i had to manually apt-get install
bridge. sorry, it's a debian thing: sometimes i can't quite
get my head round not having automatic dependency installs
for from-source builds :)
ifconfig shows that eth0 has a network address, that xen-br0 does not,
that lo does.
when i start a guest OS, that OS cannot ping the outside world.
ifconfig shows that eth0 has a network address, that xen-br0 does not,
that lo does.
if i then run dhclient3, such that xen-br0 is allocated an IP address,
then YES, sometimes i can get external access from the guest OS
(and sometimes the client becomes inaccessible, probably because the
network is taken down and back up).
the xen "master" OS still has no network access.
help?
all my experiences with this bridging thing (previously i tried
setting up tinc) have proved fruitless or demonstrated that something
was not quite right and beyond my ability to fix.
other than the networking weirdness i am genuinely impressed with xen,
esp. as i'm running an selinux kernel.
l.
--
--
<a href="http://lkcl.net";>http://lkcl.net</a>
--
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home