[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] domU Networking Issues


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
  • Date: Mon, 14 Jun 2010 23:08:37 +0530
  • Delivery-date: Mon, 14 Jun 2010 10:40:09 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=gwTtCJTFji4sONlD6hJNpU0d37SLEBRIEo67MM2T679xAfsMQzR87kR0W5J5ap3Nse L37HM6GfVv9JPbY2oA05QwdYgIN7tNsZLs0ufziXMW/u60hxolQv5L00/vbXqxFLkpg4 Nu6FxK1MlDs4Y0wk/7E+NjOYHknRXBcCOfk00=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Is IP forwarding enabled on Dom0
echo 1 > /proc/sys/net/ipv4/ip_forward
I assume it is /etc/sysctl.conf (If not then do it)

I see a problem in your brctl show output

# brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       yes
xenbr0          8000.feffffffffff       no              vif2.0
                                                       vif1.0
                                                       peth0
                                                       vif0.0


is peth0 a separate bridge or included in bridge if you see the output of


of ifconfig on the dom0: from your message your peth0 is running in
PROMISC mode and it seems to be included in bridge in the brctl show
output.
I do not think that this is right when you

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1

Note the line PROMISC in above output peth0 is the bridge in which
remaining VM ethernets should be included in it  and not in

virbr0 or xenbr0

peth0 is running in promiscous mode while xenbr0 is  not.

Try to change your network topology disable the bridges which are not
required and bring rest of the VM bridges in this peth0 bridge and
remove the eth0 thing,

The IP should be assigned to your bridge unless you have separate lan
cards and different bridges attached to them.

Running  more than one bridge on same lan card is not appropriate.

http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge

Following is a sample  bridge configuration


# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
        address 192.168.0.100
        network 192.168.0.0
        netmask 255.255.255.0
        broadcast 192.168.0.255
        gateway 192.168.0.1
        bridge_ports eth0
        bridge_fd 9
        bridge_hello 2
        bridge_maxage 12
        bridge_stp off

add rest of the Virtual Machine ethernets to this bridge.
Delete the unnecessary bridges on your machine.

post route -n and what have you specified Gateway for your VMs.
Also check there are two xml files
var/lib/xend/state two files cpu.xml and host.xml are they corrupt.


Check this page
http://wiki.xensource.com/xenwiki/CoolConfigurations
http://www.debian-administration.org/articles/360
http://kbase.redhat.com/faq/docs/DOC-29713
Do they help or not let us know.
I am assuming you read this page
http://wiki.xensource.com/xenwiki/XenNetworking
Check this page
http://www.howtoforge.com/virtualization-with-kvm-on-ubuntu-8.10
for a correct ifconfig output when using a bridge.

Pastebin the logs xend.log daemon.log xen.log
-- 
Tapas
http://mightydreams.blogspot.com
http://wiki.xensource.com/xenwiki/Xen_on_4_app_servers

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.