thr3ads.net - Xen users - [Xen-users] Network routing setup problem; domU won''t start [Dec 2007]

If this information is useful, please help other people find it:
Share via:

Rich Wales

2007-Dec-10 04:35 UTC

[Xen-users] Network routing setup problem; domU won''t start

Hi.  I''m new to Xen.  I have an Athlon (XP 2700+) box, running Ubuntu
7.10, on which I''m hoping to run several domains in a routed networking
configuration.

My initial setup of xen-utils-3.1 (version 3.1.0-0ubuntu18) went just
fine, and my dom0 is running without problems.  And I was also able to
use xen-create-image to build a guest virtual machine, which (once it
works) I plan to use as a template image for building my other domains.

But when I try to run this new VM as a domU, using "xm create", it
fails with the following error message:

Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route
failed; error detected.

Here''s some info about my setup -- hopefully enough to help someone see
whatever it is that I''m doing wrong.

Here''s my xend-config.sxp file (with comments stripped out):

(xen-api-server ((unix)))
(xend-http-server yes)
(xend-unix-server yes)
(xend-relocation-server no)
(xend-port 8000)
(xend-address '''')
(xend-relocation-hosts-allow '''')
(network-script network-route)
(vif-script vif-route)
(dom0-min-mem 196)
(dom0-cpus 0)

Here''s my xen-tools.conf file (again, with comments stripped out):

lvm = vg1
install-method = debootstrap
size = 20Gb
memory = 384Mb
swap = 1024Mb
fs = ext3
dist = etch
image = sparse
gateway = 172.31.53.1
netmask = 255.255.255.0
broadcast = 172.31.53.255
accounts = 1
kernel = /boot/vmlinuz-`uname -r`
initrd = /boot/initrd.img-`uname -r`
mirror_gutsy=http://archive.ubuntu.com/ubuntu

Here''s the configuration file for my domU:

kernel      = ''/boot/vmlinuz-2.6.22-14-xen''
ramdisk     = ''/boot/initrd.img-2.6.22-14-xen''
memory      = ''384''
root        = ''/dev/hda1 ro''
disk        = [ ''phy:vg1/template-disk,hda1,w'',
''phy:vg1/template-swap,hda2,w'' ]
name        = ''template''
vif         = [ ''mac=f2:01:72:31:53:ff, ip=172.31.53.254'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''

Here''s the output from "cat /proc/cpuinfo":

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 8
model name      : AMD Athlon(tm) XP 2700+
stepping        : 1
cpu MHz         : 2162.728
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 mmx
fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips        : 4327.29
clflush size    : 32

Here''s the output from "uname -a":

Linux whodunit 2.6.22-14-xen #1 SMP Mon Oct 15 00:35:38 GMT 2007 i686 GNU/Linux

And here''s the excerpt from /boot/grub/menu.lst that I used to boot
Xen:

title           Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen
root            (hd0,0)
kernel          /xen-3.1.gz dom0_mem=256M
module          /vmlinuz-2.6.22-14-xen
root=UUID=2c8d1c7c-4211-4497-9cc3-85cf4521c438 ro console=tty0
module          /initrd.img-2.6.22-14-xen
quiet

Any suggestions?

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Rich Wales

2007-Dec-11 02:50 UTC

head link

Re: [Xen-users] Network routing setup problem; domU won''t start

One more point which I should probably have mentioned earlier:

The computer I''m trying to get Xen working on has two physical network
interfaces.  I''m currently using eth1 and reserving eth0 for possible
future use if I expand this box to include my firewall.

Do I need to add some parameters (in xend-config.sxp?) in order to tell
Xen about dom0''s network infrastructure?

In particular, do I need to do something explicit in xend-config.sxp
to set up the internal bridge that will link my dom0 and domU''s, before
I try to start up a domU?  (I plan to use 172.31.53.0/24 on the bridge,
with 172.31.53.1 assigned to dom0.)

Here''s what I get when I do "ifconfig -a".

dummy0    Link encap:Ethernet  HWaddr AE:89:F9:0C:51:AC
          BROADCAST NOARP  MTU:1500  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)

eth0      Link encap:Ethernet  HWaddr 00:13:D4:23:58:6B
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0xc000

eth1      Link encap:Ethernet  HWaddr 00:13:D4:23:71:66
          inet addr:172.29.0.53  Bcast:172.29.0.255  Mask:255.255.255.0
          inet6 addr: fe80::213:d4ff:fe23:7166/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:66065 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6569 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6218661 (5.9 MB)  TX bytes:586232 (572.4 KB)
          Interrupt:5

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)

veth0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

veth1     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

veth2     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

veth3     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Rich Wales

2007-Dec-12 05:56 UTC

head link

Re: [Xen-users] Network routing setup problem; domU won''t start

Getting back to my "xm create" network failure:

I think I figured out at least part of what was going wrong.  I
needed to add a "netdev=" parameter in my "vif-script" line.
Once
I did this, the domU came up OK.

However, I''ve still got a problem.  The new domU does not seem to
be accessible via the net -- not even from the dom0.

Here''s what I have so far.  (I moved the "ifconfig" settings
for
dom0''s dummy interface to my internal bridge out of my custom
network script and into /etc/network/interfaces.)

I notice, BTW, that none of the vif#.#''s in my dom0 have been
assigned the IP address of my domU.  I thought that was supposed
to happen; or am I misunderstanding how the networking works?

/etc/xen/xend-config.sxp
--------------------------------------
(xen-api-server ((unix)))
(xend-http-server yes)
(xend-unix-server yes)
(xend-relocation-server no)
(xend-port 8000)
(xend-address '''')
(xend-relocation-hosts-allow '''')
(network-script network-whodunit)
(vif-script ''vif-route netdev=dummy0'')
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '''')

/etc/xen/scripts/network-whodunit
--------------------------------------
#!/bin/sh
XENDIR="/etc/xen/scripts"
$XENDIR/network-bridge "$@" netdev=eth0   bridge=xenbr0 vifnum=0
$XENDIR/network-bridge "$@" netdev=eth1   bridge=xenbr1 vifnum=1
$XENDIR/network-bridge "$@" netdev=dummy0 bridge=xenbr2 vifnum=2

/etc/xen/template.cfg
--------------------------------------
kernel      = ''/boot/vmlinuz-2.6.22-14-xen''
ramdisk     = ''/boot/initrd.img-2.6.22-14-xen''
memory      = ''384''
root        = ''/dev/hda1 ro''
disk        = [ ''phy:vg1/template-disk,hda1,w'',
''phy:vg1/template-swap,hda2,w'' ]
name        = ''template''
vif         = [ ''mac=f2:01:72:31:53:ff, ip=172.31.53.254,
bridge=xenbr2'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''

/etc/network/interfaces
--------------------------------------
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
    address 172.29.0.53
    netmask 255.255.255.0
    gateway 172.29.0.2
    post-up ethtool -K eth1 tx off

auto dummy0
iface dummy0 inet static
    address 172.31.53.1
    netmask 255.255.255.0

output of "ifconfig -a"
--------------------------------------
dummy0    Link encap:Ethernet  HWaddr 7E:0E:19:BD:A7:D6
          inet addr:172.31.53.1  Bcast:172.31.53.255  Mask:255.255.255.0
          inet6 addr: fe80::7c0e:19ff:febd:a7d6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:140 (140.0 b)  TX bytes:3307 (3.2 KB)

eth0      Link encap:Ethernet  HWaddr 00:13:D4:23:58:6B
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0xe000

eth1      Link encap:Ethernet  HWaddr 00:13:D4:23:71:66
          inet addr:172.29.0.53  Bcast:172.29.0.255  Mask:255.255.255.0
          inet6 addr: fe80::213:d4ff:fe23:7166/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1437 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1245151 (1.1 MB)  TX bytes:124550 (121.6 KB)

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:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:448 (448.0 b)  TX bytes:448 (448.0 b)

pdummy0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:3727 (3.6 KB)

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:15929 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1445 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1313653 (1.2 MB)  TX bytes:137238 (134.0 KB)
          Interrupt:5

veth0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

veth3     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1437 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:124550 (121.6 KB)  TX bytes:1245291 (1.1 MB)

vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3307 (3.2 KB)  TX bytes:210 (210.0 b)

vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:172.31.53.1  Bcast:172.31.255.255  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:9 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 b)  TX bytes:2779 (2.7 KB)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:90 (90.0 b)

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14063 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:916374 (894.8 KB)  TX bytes:300 (300.0 b)

xenbr2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3027 (2.9 KB)  TX bytes:238 (238.0 b)

output of "netstat -rn"
--------------------------------------
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
172.31.53.254   0.0.0.0         255.255.255.255 UH        0 0          0 vif1.0
172.31.53.0     0.0.0.0         255.255.255.0   U         0 0          0 dummy0
172.29.0.0      0.0.0.0         255.255.255.0   U         0 0          0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth1
0.0.0.0         172.29.0.2      0.0.0.0         UG        0 0          0 eth1

output of "iptables -n -L"
--------------------------------------
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     0    --  172.31.53.254        0.0.0.0/0           PHYSDEV match
--physdev-in vif1.0
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif1.0 udp spt:68 dpt:67

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

output of "xm network-list 1"
--------------------------------------
Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
0   0  f2:01:72:31:53:ff    0     4      8     768  /769
/local/domain/0/backend/vif/1/0

relevant piece of /boot/grub/menu.lst
--------------------------------------
title           Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen
root            (hd0,0)
kernel          /xen-3.1.gz dom0_mem=256M
module          /vmlinuz-2.6.22-14-xen
root=UUID=2c8d1c7c-4211-4497-9cc3-85cf4521c438 ro console=tty0
module          /initrd.img-2.6.22-14-xen
quiet

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Artur Linhart - Linux communication

2007-Dec-12 08:09 UTC

head link

RE: [Xen-users] Network routing setup problem; domU won''t start

Hello,

	Did You specify also the given IP 172.31.53.254 in your DomU? If the
DomU is not accessible from Dom0, I suppose it is also in the opposite way -
Dom0 is not accessible from Dom0? Are there also any error messages in the
Dom0 log files or any other error messages in DomU?

	With best regards

		Archie

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Rich Wales
Sent: Wednesday, December 12, 2007 6:57 AM
To: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Network routing setup problem; domU won''t
start

Getting back to my "xm create" network failure:

I think I figured out at least part of what was going wrong.  I
needed to add a "netdev=" parameter in my "vif-script" line.
Once
I did this, the domU came up OK.

However, I''ve still got a problem.  The new domU does not seem to
be accessible via the net -- not even from the dom0.

Here''s what I have so far.  (I moved the "ifconfig" settings
for
dom0''s dummy interface to my internal bridge out of my custom
network script and into /etc/network/interfaces.)

I notice, BTW, that none of the vif#.#''s in my dom0 have been
assigned the IP address of my domU.  I thought that was supposed
to happen; or am I misunderstanding how the networking works?

/etc/xen/xend-config.sxp
--------------------------------------
(xen-api-server ((unix)))
(xend-http-server yes)
(xend-unix-server yes)
(xend-relocation-server no)
(xend-port 8000)
(xend-address '''')
(xend-relocation-hosts-allow '''')
(network-script network-whodunit)
(vif-script ''vif-route netdev=dummy0'')
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '''')

/etc/xen/scripts/network-whodunit
--------------------------------------
#!/bin/sh
XENDIR="/etc/xen/scripts"
$XENDIR/network-bridge "$@" netdev=eth0   bridge=xenbr0 vifnum=0
$XENDIR/network-bridge "$@" netdev=eth1   bridge=xenbr1 vifnum=1
$XENDIR/network-bridge "$@" netdev=dummy0 bridge=xenbr2 vifnum=2

/etc/xen/template.cfg
--------------------------------------
kernel      = ''/boot/vmlinuz-2.6.22-14-xen''
ramdisk     = ''/boot/initrd.img-2.6.22-14-xen''
memory      = ''384''
root        = ''/dev/hda1 ro''
disk        = [ ''phy:vg1/template-disk,hda1,w'',
''phy:vg1/template-swap,hda2,w'' ]
name        = ''template''
vif         = [ ''mac=f2:01:72:31:53:ff, ip=172.31.53.254,
bridge=xenbr2'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''

/etc/network/interfaces
--------------------------------------
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
    address 172.29.0.53
    netmask 255.255.255.0
    gateway 172.29.0.2
    post-up ethtool -K eth1 tx off

auto dummy0
iface dummy0 inet static
    address 172.31.53.1
    netmask 255.255.255.0

output of "ifconfig -a"
--------------------------------------
dummy0    Link encap:Ethernet  HWaddr 7E:0E:19:BD:A7:D6
          inet addr:172.31.53.1  Bcast:172.31.53.255  Mask:255.255.255.0
          inet6 addr: fe80::7c0e:19ff:febd:a7d6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:140 (140.0 b)  TX bytes:3307 (3.2 KB)

eth0      Link encap:Ethernet  HWaddr 00:13:D4:23:58:6B
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0xe000

eth1      Link encap:Ethernet  HWaddr 00:13:D4:23:71:66
          inet addr:172.29.0.53  Bcast:172.29.0.255  Mask:255.255.255.0
          inet6 addr: fe80::213:d4ff:fe23:7166/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1437 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1245151 (1.1 MB)  TX bytes:124550 (121.6 KB)

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:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:448 (448.0 b)  TX bytes:448 (448.0 b)

pdummy0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:3727 (3.6 KB)

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:15929 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1445 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1313653 (1.2 MB)  TX bytes:137238 (134.0 KB)
          Interrupt:5

veth0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

veth3     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  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)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1437 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:124550 (121.6 KB)  TX bytes:1245291 (1.1 MB)

vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3307 (3.2 KB)  TX bytes:210 (210.0 b)

vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  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)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:172.31.53.1  Bcast:172.31.255.255  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:9 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 b)  TX bytes:2779 (2.7 KB)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:90 (90.0 b)

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14063 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:916374 (894.8 KB)  TX bytes:300 (300.0 b)

xenbr2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3027 (2.9 KB)  TX bytes:238 (238.0 b)

output of "netstat -rn"
--------------------------------------
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
172.31.53.254   0.0.0.0         255.255.255.255 UH        0 0          0
vif1.0
172.31.53.0     0.0.0.0         255.255.255.0   U         0 0          0
dummy0
172.29.0.0      0.0.0.0         255.255.255.0   U         0 0          0
eth1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0
eth1
0.0.0.0         172.29.0.2      0.0.0.0         UG        0 0          0
eth1

output of "iptables -n -L"
--------------------------------------
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     0    --  172.31.53.254        0.0.0.0/0           PHYSDEV match
--physdev-in vif1.0
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif1.0 udp spt:68 dpt:67

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

output of "xm network-list 1"
--------------------------------------
Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
0   0  f2:01:72:31:53:ff    0     4      8     768  /769
/local/domain/0/backend/vif/1/0

relevant piece of /boot/grub/menu.lst
--------------------------------------
title           Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen
root            (hd0,0)
kernel          /xen-3.1.gz dom0_mem=256M
module          /vmlinuz-2.6.22-14-xen
root=UUID=2c8d1c7c-4211-4497-9cc3-85cf4521c438 ro console=tty0
module          /initrd.img-2.6.22-14-xen
quiet

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

__________ Informace od NOD32 2714 (20071210) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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

Rich Wales

2007-Dec-12 08:26 UTC

head link

Re: [Xen-users] Network routing setup problem; domU won''t start

Artur Linhart asked:
> Did you specify also the given IP 172.31.53.254 in your DomU?
Yes.  Here''s the /etc/network/interfaces file on my domU:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
 address 172.31.53.254
 gateway 172.31.53.1
 netmask 255.255.255.0


 # post-up  ethtool -K eth0 tx off

#
# The commented out line above will disable TCP checksumming which
# might resolve problems for some users.  It is disabled by default
#
> If the DomU is not accessible from Dom0, I suppose it is also in
> the opposite way - Dom0 is not accessible from Dom0?  Are there
> also any error messages in the Dom0 log files or any other error
> messages in DomU?
I don''t see anything in the log files on my dom0 that appear to be
error messages about networking.  And when I mount the domU''s disk
to examine it (when the domU is down), there isn''t ANYTHING AT ALL
written to any of the domU''s /var/log files (except /var/log/wtmp)
since I originally created the domU''s disk image a few days ago.

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Rich Wales

2007-Dec-16 04:14 UTC

head link

Re: [Xen-users] Network routing setup problem; domU won''t start

I''m still unable to get a domU to start up completely and be accessible
via a network connection.

In addition to the configuration file contents and command output which
I''ve already posted on this topic (please see my earlier e-mail),
here''s
some more output from various commands which I ran on my dom0 after my
(attempted) creation of a domU.

============================================================================
[19:35 whodunit /etc/xen 147] xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   256     1     r-----    287.5
template                                   3   384     1     ------   1693.6
[20:04 whodunit /etc/xen 148] brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1
xenbr2          8000.feffffffffff       no              vif0.2
                                                        pdummy0
[20:04 whodunit /etc/xen 149] brctl showmacs xenbr2
port no mac addr                is local?       ageing timer
  1     fe:ff:ff:ff:ff:ff       yes                0.00
[20:04 whodunit /etc/xen 150] xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   256     1     r-----    289.0
template                                   3   384     1     ------   1827.0
[20:06 whodunit /etc/xen 151] brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1
xenbr2          8000.feffffffffff       no              vif0.2
                                                        pdummy0
[20:06 whodunit /etc/xen 152] brctl showmacs xenbr0
port no mac addr                is local?       ageing timer
[20:06 whodunit /etc/xen 153] brctl showmacs xenbr1
port no mac addr                is local?       ageing timer
  2     00:0d:87:4d:58:b8       no                 1.80
  2     00:10:60:24:e7:fe       no                 8.15
  2     00:10:60:26:6b:9d       no                39.83
  2     00:10:60:26:e7:88       no                 7.74
  2     00:11:d9:03:a5:01       no                18.54
  2     00:12:17:55:98:f4       no                27.45
  1     00:13:d4:23:71:66       no                 0.00
  2     00:18:f8:0e:7b:e1       no                56.75
  2     00:80:c8:c1:c8:c6       no                 2.44
  2     02:20:78:f0:7d:19       no                 0.03
  2     02:50:8d:49:b9:1e       no                 0.00
  1     fe:ff:ff:ff:ff:ff       yes                0.00
[20:06 whodunit /etc/xen 154] brctl showmacs xenbr2
port no mac addr                is local?       ageing timer
  1     fe:ff:ff:ff:ff:ff       yes                0.00
[20:06 whodunit /etc/xen 155]

============================================================================
Note, in the output of "brctl show", that both bridges xenbr1 and
xenbr2
are shown with the same "bridge id" value.  Is this a cause for
concern?

I would really appreciate any assistance here -- even a vague pointer to
something else to investigate.  Xen sounds like something I would very
much like to use -- but until/unless I can get the networking to work,
it''s of no use to me at all.

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Rich Wales

2007-Dec-17 02:41 UTC

head link

[Xen-users] How to see a domU''s console (without a working network connection)?

Sorry if this is an elementary question, but . . . .

Is there a way for me to see the console output from a domU without
depending on the domU having a working network connection?

I''m still trying to figure out why a domU simply is not reachable via
a network bridge.  I''m hoping maybe being able to see what is going on
in the domU, via its console output, might help, but I''m worried that
the lack of a working network connection to the domU might make it
difficult or impossible for me to see its console.

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@richw.org
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

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

Xen users - Dec 2007 - Network routing setup problem; domU won''t start

[Xen-users] Network routing setup problem; domU won''t start

Re: [Xen-users] Network routing setup problem; domU won''t start

Re: [Xen-users] Network routing setup problem; domU won''t start

RE: [Xen-users] Network routing setup problem; domU won''t start

Re: [Xen-users] Network routing setup problem; domU won''t start

Re: [Xen-users] Network routing setup problem; domU won''t start

[Xen-users] How to see a domU''s console (without a working network connection)?