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

Re: [Xen-users] Get Network on DomU


  • To: xen-users@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Thu, 12 Sep 2013 14:24:02 -0500
  • Delivery-date: Thu, 12 Sep 2013 19:24:55 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hello again.

El 12/09/13 06:24, Dorian escribió:
Now about my network:
My hypervisor is configured with a working bridge
[...]
 >> brctl show
bridge name    bridge id        STP enabled    interfaces
pan0        8000.feffffffffff    no        vif1.0
                             vif2.0
xenbr0 8000.002655c46159    no        eth0
You VM's network seems to be attached to a pan0, and there is no physical interface to the outside world in that bridge. If you mean your VM's to have a network interface within the same network as your Dom0's eth0, change their's config files. Make them to be attached to xenbr0.

 From the DomU guest I got the following and no internet:
xm console Machin-chose-cpt.net
[ 1737.324143] Setting capacity to 8388608
[ 1737.326271] Setting capacity to 1048576
[ 1737.327052] Setting capacity to 8388608
[ 1737.373784] Setting capacity to 1048576

root@Machin-chose-cpt:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3e:5f:81:78
           inet6 addr: fe80::216:3eff:fe5f:8178/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:40 errors:0 dropped:0 overruns:0 frame:0
           TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:8262 (8.0 KiB)  TX bytes:17568 (17.1 KiB)
           Interrupt:19

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           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)

# grep -E -v '^(#)' /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Unless one your VM's have a DHCP server, this won't work aether. If you attach you VM to xenbr0 AND there is a working DHCP server on your network, nothing need to be changed here, your VM will get a address form you regular DHCP server.

I've to inform that upon creation of this DomU, the system advices about
Networking will not work since there is a missing network-script or
vif-script.
Here is what I have in root@debian:/home/dorian#
  grep -E -v ^# /etc/xen/xend-config.sxp

  (vif-script vif-bridge)

A common approach, at least on Debian, is to drop Xen's stock network scripts and create the necessary bridges by OS's means, from /etc/network/interfaces. This would give you more solid and predictible setup.

There are plenty of examples in this list's archive.

Greetings.

--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

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