xen network problems

Discussion in 'Server Operation' started by ralph, Jan 20, 2008.

  1. ralph

    ralph New Member

    ive followed the howtoforge guide for debian etch repository xen install.

    ive got two network interfaces, for which eth1 is the one online.

    So i define (network-bridge network-script netdev=eth1) in xend-config.sxp.

    The problem is when i then boot up the xen kernel i cant get online with host(dom0) but the domains(domU) gets online. What have i forgotten?
     
  2. falko

    falko Super Moderator Howtoforge Staff

    What's the output of
    Code:
    ifconfig
    and
    Code:
    route -nee
    on dom0? Any errors in the logs?
     
  3. ralph

    ralph New Member

    cant copy/paste so i will give as much info as possible:

    ifconfig shows:

    eth1 - public ip adress
    lo - 127.0.0.1
    peth1 - no ip adress
    vif0.1, vif1.0, vif 2.0 and xenbr1 - no ipadresses

    route -nee shows eth1 in routes. one from gateway and one to gateway.

    cant understand how the vms can be online but not the host.
     
  4. falko

    falko Super Moderator Howtoforge Staff

    What's in /etc/network/interfaces on dom0?
     
  5. ralph

    ralph New Member

    allow-hotplug eth1
    iface eth1 inet static
    address <publicip>
    netmask 255.255.255.0
    broadcast <broadcastip>
    gateway <gatewayip>

    was thinking about debugging the network-bridge script to see if i can get any errors.
     
  6. falko

    falko Super Moderator Howtoforge Staff

    That's all? No loopback device (lo)?
     
  7. ralph

    ralph New Member

    yeah sorry forgot that. lo as by default installed. any hints to what could be wrong. Should be the bridge right?
     
  8. falko

    falko Super Moderator Howtoforge Staff

    Are there spaces in front of address, broadcast, netmask, and gateway? Can you post the whole file again and wrap it in code tags here (that's the # button in the editor here)?
     
  9. ralph

    ralph New Member

    it works when im not booting xen kernel so i guess the problem has to lie somewhere else.
     

Share This Page