YEVGENIY GOLDBERG
2007-Apr-28 22:47 UTC
[Xen-users] Need help setting up guest''s networking
Greetings!
I finally got the install done for a couple of gust OSs (Win 2003 server &
Suse Enterprise 10)
Bothe gusts are up and running, but - no networking.
My setup:
Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB
NICs
Host OS- Suse Linux Enterprise server 10
Xen - 3.0.2_09749-0.4
Config file for Win 2003 server guest:
# -*- mode: python; -*-
#===========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#===========================================================================
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen/boot/hvmloader"
# The domain build function. HVM domain uses ''hvm''.
builder=''hvm''
# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
# memory errors. The domain needs enough memory to boot kernel
# and modules. Allocating less than 32MBs is not recommended.
memory = 512
# Shadow pagetable memory for the domain, in MB.
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
# A name for your domain. All domains must have different names.
name = "win2003server"
# 128-bit UUID for the domain. The default behavior is to generate a new UUID
# on each call to ''xm create''.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
#-----------------------------------------------------------------------------
# the number of cpus guest platform has, default=1
#vcpus=1
# enable/disable HVM guest PAE, default=0 (disabled)
#pae=0
# enable/disable HVM guest ACPI, default=0 (disabled)
#acpi=0
# enable/disable HVM guest APIC, default=0 (disabled)
#apic=0
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0'' ]
# type=ioemu specify the NIC is an ioemu device not netfront
#vif = [ ''type=ioemu, bridge=xenbr0'' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
#disk = [ ''phy:hda1,hda1,r'' ]
disk = [ ''file:/var/lib/xen/images/windisk.img,ioemu:hda,w'',
''phy:/dev/hda,hdb,r'' ]
cdrom="/media/disk/iso/win2003server.iso"
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three
''reasons''
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of
the old
# one;
# "preserve", meaning that no clean-up is done until the
domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up,
but is
# renamed and a new domain started in its place.
#
# The default is
#
on_poweroff = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = ''onreboot'' means on_poweroff =
''destroy''
# on_reboot = ''restart''
# on_crash = ''destroy''
#
# restart = ''always'' means on_poweroff =
''restart''
# on_reboot = ''restart''
# on_crash = ''restart''
#
# restart = ''never'' means on_poweroff =
''destroy''
# on_reboot = ''destroy''
# on_crash = ''destroy''
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
#===========================================================================
# New stuff
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="c"
#-----------------------------------------------------------------------------
# write to temporary files instead of disk image files
#snapshot=1
#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
sdl=1
#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=0
#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use ''vnc-listen'' setting from
/etc/xen/xend-config.sxp
#vnclisten="127.0.0.1"
#----------------------------------------------------------------------------
# set VNC display number, default = domid
#vncdisplay=1
#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
#vncunused=1
#----------------------------------------------------------------------------
# enable spawning vncviewer for domain''s console
# (only valid when vnc=1), default = 0
#vncconsole=0
vncviewer=0
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=0
#-----------------------------------------------------------------------------
# serial port re-direct to pty deivce, /dev/pts/n
# then xm console or minicom can connect
serial=''pty''
#-----------------------------------------------------------------------------
# enable sound card support, [sb16|es1370|all|..,..], default none
#soundhw=''sb16''
#-----------------------------------------------------------------------------
# set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1
#-----------------------------------------------------------------------------
# start in full screen
#full-screen=1
#-----------------------------------------------------------------------------
# Enable USB support (specific devices specified at runtime through the
# monitor window)
#usb=1
# Enable USB mouse support (only enable one of the following, `mouse''
for
# PS/2 protocol relative mouse, `tablet''
for
# absolute mouse)
#usbdevice=''mouse''
#usbdevice=''tablet''
Config file for Suse Linux Enterprise 10 guest:
disk = [ ''file:/var/lib/xen/images/OraDb1/hda,hda,w'',
''phy:/dev/hda,hdb,r'' ]
memory = 1024
vcpus = 2
builder = ''linux''
name = ''OraDb1''
vif = [
''mac=00:16:3e:f3:64:e9'',''bridge=xenbr0'']
localtime = 0
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
extra = '' TERM=xterm''
bootloader = ''/usr/lib/xen/boot/domUloader.py''
bootentry = ''hda2:/boot/vmlinuz-xen,/boot/initrd-xen''
boot="c"
out put of brctl show:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feae66791813 no vif0.0
peth0
vif2.1
vif2.0
tun0
vif3.0
Output of ifconfig on the host:
eth0 Link encap:Ethernet HWaddr 00:50:8D:94:71:4A
inet addr:67.184.153.5 Bcast:255.255.255.255 Mask:255.255.248.0
inet6 addr: fe80::250:8dff:fe94:714a/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:172324 errors:0 dropped:0 overruns:0 frame:0
TX packets:1904 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12503150 (11.9 Mb) TX bytes:371462 (362.7 Kb)
eth1 Link encap:Ethernet HWaddr 00:50:8D:94:71:4B
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:5 Base address:0xa000
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:502 errors:0 dropped:0 overruns:0 frame:0
TX packets:502 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:49132 (47.9 Kb) TX bytes:49132 (47.9 Kb)
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 MTU:1500 Metric:1
RX packets:172405 errors:0 dropped:0 overruns:0 frame:0
TX packets:1953 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12507544 (11.9 Mb) TX bytes:377357 (368.5 Kb)
Interrupt:11 Base address:0x4000
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
tun0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13
inet6 addr: fe80::fcae:66ff:fe79:1813/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:843 errors:0 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:500
RX bytes:4101 (4.0 Kb) TX bytes:52246 (51.0 Kb)
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)
veth4 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)
veth5 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)
veth6 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)
veth7 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
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1904 errors:0 dropped:0 overruns:0 frame:0
TX packets:172324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:371462 (362.7 Kb) TX bytes:12503150 (11.9 Mb)
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)
vif0.4 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.5 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.6 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.7 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)
vif2.0 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:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:148584 errors:0 dropped:1800 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468 (468.0 b) TX bytes:9013081 (8.5 Mb)
vif2.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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:150390 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif3.0 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:0 errors:0 dropped:861 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:170009 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:7939155 (7.5 Mb) TX bytes:0 (0.0 b)
I''ll be happy to provide any other information to help identify the
issue.
Best regards,
-Eugene
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-29 00:55 UTC
Re: [Xen-users] Need help setting up guest''s networking - update
Just a quick update - The windows 2003 server networking is now working. Not sure what have changed. The Suse guest still does not have a network. -Eugene. On Apr 28, 2007, at 5:47 PM, YEVGENIY GOLDBERG wrote:> Greetings! > > I finally got the install done for a couple of gust OSs (Win 2003 > server & Suse Enterprise 10) > Bothe gusts are up and running, but - no networking. > > My setup: > > Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 > onboard GB NICs > Host OS- Suse Linux Enterprise server 10 > Xen - 3.0.2_09749-0.4 > > Config file for Win 2003 server guest: > > # -*- mode: python; -*- > #===================================================================== > ======> # Python configuration setup for ''xm create''. > # This script sets the parameters used when a domain is created > using ''xm create''. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > #===================================================================== > ======> > import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > > #--------------------------------------------------------------------- > ------- > # Kernel image file. > kernel = "/usr/lib/xen/boot/hvmloader" > > # The domain build function. HVM domain uses ''hvm''. > builder=''hvm'' > > # Initial memory allocation (in megabytes) for the new domain. > # > # WARNING: Creating a domain with insufficient memory may cause out of > # memory errors. The domain needs enough memory to boot > kernel > # and modules. Allocating less than 32MBs is not recommended. > memory = 512 > > # Shadow pagetable memory for the domain, in MB. > # Should be at least 2KB per MB of domain memory, plus a few MB per > vcpu. > shadow_memory = 8 > > # A name for your domain. All domains must have different names. > name = "win2003server" > > # 128-bit UUID for the domain. The default behavior is to generate > a new UUID > # on each call to ''xm create''. > #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" > > #--------------------------------------------------------------------- > -------- > # the number of cpus guest platform has, default=1 > #vcpus=1 > > # enable/disable HVM guest PAE, default=0 (disabled) > #pae=0 > > # enable/disable HVM guest ACPI, default=0 (disabled) > #acpi=0 > > # enable/disable HVM guest APIC, default=0 (disabled) > #apic=0 > > # List of which CPUS this domain is allowed to use, default Xen picks > #cpus = "" # leave to Xen to pick > #cpus = "0" # all vcpus run on CPU0 > #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 > > # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0'' ] > # type=ioemu specify the NIC is an ioemu device not netfront > #vif = [ ''type=ioemu, bridge=xenbr0'' ] > > #--------------------------------------------------------------------- > ------- > # Define the disk devices you want the domain to have access to, and > # what you want them accessible as. > # Each disk entry is of the form phy:UNAME,DEV,MODE > # where UNAME is the device, DEV is the device name the domain will > see, > # and MODE is r for read-only, w for read-write. > > #disk = [ ''phy:hda1,hda1,r'' ] > disk = [ ''file:/var/lib/xen/images/windisk.img,ioemu:hda,w'', ''phy:/ > dev/hda,hdb,r'' ] > cdrom="/media/disk/iso/win2003server.iso" > > #--------------------------------------------------------------------- > ------- > # Configure the behaviour when a domain exits. There are three > ''reasons'' > # for a domain to stop: poweroff, reboot, and crash. For each of > these you > # may specify: > # > # "destroy", meaning that the domain is cleaned up as normal; > # "restart", meaning that a new domain is started in place > of the old > # one; > # "preserve", meaning that no clean-up is done until the > domain is > # manually destroyed (using xm destroy, for > example); or > # "rename-restart", meaning that the old domain is not cleaned > up, but is > # renamed and a new domain started in its place. > # > # The default is > # > on_poweroff = ''destroy'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > # > # For backwards compatibility we also support the deprecated option > restart > # > # restart = ''onreboot'' means on_poweroff = ''destroy'' > # on_reboot = ''restart'' > # on_crash = ''destroy'' > # > # restart = ''always'' means on_poweroff = ''restart'' > # on_reboot = ''restart'' > # on_crash = ''restart'' > # > # restart = ''never'' means on_poweroff = ''destroy'' > # on_reboot = ''destroy'' > # on_crash = ''destroy'' > > #on_poweroff = ''destroy'' > #on_reboot = ''restart'' > #on_crash = ''restart'' > > #===================================================================== > ======> > # New stuff > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > > #--------------------------------------------------------------------- > -------- > # boot on floppy (a), hard disk (c) or CD-ROM (d) > # default: hard disk, cd-rom, floppy > boot="c" > > #--------------------------------------------------------------------- > -------- > # write to temporary files instead of disk image files > #snapshot=1 > > #--------------------------------------------------------------------- > ------- > # enable SDL library for graphics, default = 0 > sdl=1 > > #--------------------------------------------------------------------- > ------- > # enable VNC library for graphics, default = 1 > vnc=0 > > #--------------------------------------------------------------------- > ------- > # address that should be listened on for the VNC server if vnc is set. > # default is to use ''vnc-listen'' setting from /etc/xen/xend-config.sxp > #vnclisten="127.0.0.1" > > #--------------------------------------------------------------------- > ------- > # set VNC display number, default = domid > #vncdisplay=1 > > #--------------------------------------------------------------------- > ------- > # try to find an unused port for the VNC server, default = 1 > #vncunused=1 > > #--------------------------------------------------------------------- > ------- > # enable spawning vncviewer for domain''s console > # (only valid when vnc=1), default = 0 > #vncconsole=0 > vncviewer=0 > > #--------------------------------------------------------------------- > ------- > # no graphics, use serial port > #nographic=0 > > #--------------------------------------------------------------------- > ------- > # enable stdvga, default = 0 (use cirrus logic device model) > stdvga=0 > > #--------------------------------------------------------------------- > -------- > # serial port re-direct to pty deivce, /dev/pts/n > # then xm console or minicom can connect > serial=''pty'' > > > #--------------------------------------------------------------------- > -------- > # enable sound card support, [sb16|es1370|all|..,..], default none > #soundhw=''sb16'' > > > #--------------------------------------------------------------------- > -------- > # set the real time clock to local time [default=0 i.e. set to utc] > #localtime=1 > > > #--------------------------------------------------------------------- > -------- > # start in full screen > #full-screen=1 > > > #--------------------------------------------------------------------- > -------- > # Enable USB support (specific devices specified at runtime > through the > # monitor window) > #usb=1 > > # Enable USB mouse support (only enable one of the following, > `mouse'' for > # PS/2 protocol relative mouse, > `tablet'' for > # absolute mouse) > #usbdevice=''mouse'' > #usbdevice=''tablet'' > > > > Config file for Suse Linux Enterprise 10 guest: > > disk = [ ''file:/var/lib/xen/images/OraDb1/hda,hda,w'', ''phy:/dev/ > hda,hdb,r'' ] > memory = 1024 > vcpus = 2 > builder = ''linux'' > name = ''OraDb1'' > vif = [ ''mac=00:16:3e:f3:64:e9'',''bridge=xenbr0''] > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = '' TERM=xterm'' > bootloader = ''/usr/lib/xen/boot/domUloader.py'' > bootentry = ''hda2:/boot/vmlinuz-xen,/boot/initrd-xen'' > boot="c" > > > > out put of brctl show: > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feae66791813 no vif0.0 > peth0 > vif2.1 > vif2.0 > tun0 > vif3.0 > > > Output of ifconfig on the host: > > > eth0 Link encap:Ethernet HWaddr 00:50:8D:94:71:4A > inet addr:67.184.153.5 Bcast:255.255.255.255 Mask: > 255.255.248.0 > inet6 addr: fe80::250:8dff:fe94:714a/64 Scope:Link > UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 > Metric:1 > RX packets:172324 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1904 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:12503150 (11.9 Mb) TX bytes:371462 (362.7 Kb) > > eth1 Link encap:Ethernet HWaddr 00:50:8D:94:71:4B > 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:5 Base address:0xa000 > > 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:502 errors:0 dropped:0 overruns:0 frame:0 > TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:49132 (47.9 Kb) TX bytes:49132 (47.9 Kb) > > 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 MTU:1500 Metric:1 > RX packets:172405 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1953 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:12507544 (11.9 Mb) TX bytes:377357 (368.5 Kb) > Interrupt:11 Base address:0x4000 > > sit0 Link encap:IPv6-in-IPv4 > NOARP MTU:1480 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) > > tun0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 > inet6 addr: fe80::fcae:66ff:fe79:1813/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:31 errors:0 dropped:0 overruns:0 frame:0 > TX packets:843 errors:0 dropped:0 overruns:2 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:4101 (4.0 Kb) TX bytes:52246 (51.0 Kb) > > 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) > > veth4 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) > > veth5 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) > > veth6 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) > > veth7 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 > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:1904 errors:0 dropped:0 overruns:0 frame:0 > TX packets:172324 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:371462 (362.7 Kb) TX bytes:12503150 (11.9 Mb) > > 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) > > vif0.4 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.5 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.6 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.7 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) > > vif2.0 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:6 errors:0 dropped:0 overruns:0 frame:0 > TX packets:148584 errors:0 dropped:1800 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:468 (468.0 b) TX bytes:9013081 (8.5 Mb) > > vif2.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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:150390 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > vif3.0 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:0 errors:0 dropped:861 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:170009 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:7939155 (7.5 Mb) TX bytes:0 (0.0 b) > > > I''ll be happy to provide any other information to help identify the > issue. > > Best regards, > > -Eugene > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2007-Apr-29 07:27 UTC
Re: [Xen-users] Need help setting up guest''s networking
YEVGENIY GOLDBERG wrote:> Greetings! > > I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) > Bothe gusts are up and running, but - no networking. > > My setup: > > Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs > Host OS- Suse Linux Enterprise server 10 > Xen - 3.0.2_09749-0.4 > > Config file for Win 2003 server guest: > > # -*- mode: python; -*- > #===========================================================================> # Python configuration setup for ''xm create''. > # This script sets the parameters used when a domain is created using ''xm create''. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > #===========================================================================> > import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > > #---------------------------------------------------------------------------- > # Kernel image file. > kernel = "/usr/lib/xen/boot/hvmloader" > > # The domain build function. HVM domain uses ''hvm''. > builder=''hvm'' > > # Initial memory allocation (in megabytes) for the new domain. > # > # WARNING: Creating a domain with insufficient memory may cause out of > # memory errors. The domain needs enough memory to boot kernel > # and modules. Allocating less than 32MBs is not recommended. > memory = 512 > > # Shadow pagetable memory for the domain, in MB. > # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. > shadow_memory = 8 > > # A name for your domain. All domains must have different names. > name = "win2003server" > > # 128-bit UUID for the domain. The default behavior is to generate a new UUID > # on each call to ''xm create''. > #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" > > #----------------------------------------------------------------------------- > # the number of cpus guest platform has, default=1 > #vcpus=1 > > # enable/disable HVM guest PAE, default=0 (disabled) > #pae=0 > > # enable/disable HVM guest ACPI, default=0 (disabled) > #acpi=0 > > # enable/disable HVM guest APIC, default=0 (disabled) > #apic=0 > > # List of which CPUS this domain is allowed to use, default Xen picks > #cpus = "" # leave to Xen to pick > #cpus = "0" # all vcpus run on CPU0 > #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 > > # Optionally define mac and/or bridge for the network interfaces. > # Random MACs are assigned if not given. > vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0'' ] > # type=ioemu specify the NIC is an ioemu device not netfront > #vif = [ ''type=ioemu, bridge=xenbr0'' ] > > #---------------------------------------------------------------------------- > # Define the disk devices you want the domain to have access to, and > # what you want them accessible as. > # Each disk entry is of the form phy:UNAME,DEV,MODE > # where UNAME is the device, DEV is the device name the domain will see, > # and MODE is r for read-only, w for read-write. > > #disk = [ ''phy:hda1,hda1,r'' ] > disk = [ ''file:/var/lib/xen/images/windisk.img,ioemu:hda,w'', ''phy:/dev/hda,hdb,r'' ] > cdrom="/media/disk/iso/win2003server.iso" > > #---------------------------------------------------------------------------- > # Configure the behaviour when a domain exits. There are three ''reasons'' > # for a domain to stop: poweroff, reboot, and crash. For each of these you > # may specify: > # > # "destroy", meaning that the domain is cleaned up as normal; > # "restart", meaning that a new domain is started in place of the old > # one; > # "preserve", meaning that no clean-up is done until the domain is > # manually destroyed (using xm destroy, for example); or > # "rename-restart", meaning that the old domain is not cleaned up, but is > # renamed and a new domain started in its place. > # > # The default is > # > on_poweroff = ''destroy'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > # > # For backwards compatibility we also support the deprecated option restart > # > # restart = ''onreboot'' means on_poweroff = ''destroy'' > # on_reboot = ''restart'' > # on_crash = ''destroy'' > # > # restart = ''always'' means on_poweroff = ''restart'' > # on_reboot = ''restart'' > # on_crash = ''restart'' > # > # restart = ''never'' means on_poweroff = ''destroy'' > # on_reboot = ''destroy'' > # on_crash = ''destroy'' > > #on_poweroff = ''destroy'' > #on_reboot = ''restart'' > #on_crash = ''restart'' > > #===========================================================================> > # New stuff > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > > #----------------------------------------------------------------------------- > # boot on floppy (a), hard disk (c) or CD-ROM (d) > # default: hard disk, cd-rom, floppy > boot="c" > > #----------------------------------------------------------------------------- > # write to temporary files instead of disk image files > #snapshot=1 > > #---------------------------------------------------------------------------- > # enable SDL library for graphics, default = 0 > sdl=1 > > #---------------------------------------------------------------------------- > # enable VNC library for graphics, default = 1 > vnc=0 > > #---------------------------------------------------------------------------- > # address that should be listened on for the VNC server if vnc is set. > # default is to use ''vnc-listen'' setting from /etc/xen/xend-config.sxp > #vnclisten="127.0.0.1" > > #---------------------------------------------------------------------------- > # set VNC display number, default = domid > #vncdisplay=1 > > #---------------------------------------------------------------------------- > # try to find an unused port for the VNC server, default = 1 > #vncunused=1 > > #---------------------------------------------------------------------------- > # enable spawning vncviewer for domain''s console > # (only valid when vnc=1), default = 0 > #vncconsole=0 > vncviewer=0 > > #---------------------------------------------------------------------------- > # no graphics, use serial port > #nographic=0 > > #---------------------------------------------------------------------------- > # enable stdvga, default = 0 (use cirrus logic device model) > stdvga=0 > > #----------------------------------------------------------------------------- > # serial port re-direct to pty deivce, /dev/pts/n > # then xm console or minicom can connect > serial=''pty'' > > > #----------------------------------------------------------------------------- > # enable sound card support, [sb16|es1370|all|..,..], default none > #soundhw=''sb16'' > > > #----------------------------------------------------------------------------- > # set the real time clock to local time [default=0 i.e. set to utc] > #localtime=1 > > > #----------------------------------------------------------------------------- > # start in full screen > #full-screen=1 > > > #----------------------------------------------------------------------------- > # Enable USB support (specific devices specified at runtime through the > # monitor window) > #usb=1 > > # Enable USB mouse support (only enable one of the following, `mouse'' for > # PS/2 protocol relative mouse, `tablet'' for > # absolute mouse) > #usbdevice=''mouse'' > #usbdevice=''tablet'' > > > > Config file for Suse Linux Enterprise 10 guest: > > disk = [ ''file:/var/lib/xen/images/OraDb1/hda,hda,w'', ''phy:/dev/hda,hdb,r'' ] > memory = 1024 > vcpus = 2 > builder = ''linux'' > name = ''OraDb1'' > vif = [ ''mac=00:16:3e:f3:64:e9'',''bridge=xenbr0''] > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = '' TERM=xterm'' > bootloader = ''/usr/lib/xen/boot/domUloader.py'' > bootentry = ''hda2:/boot/vmlinuz-xen,/boot/initrd-xen'' > boot="c" > > > > out put of brctl show: > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feae66791813 no vif0.0 > peth0 > vif2.1 > vif2.0 > tun0 > vif3.0 > > > Output of ifconfig on the host: > > > eth0 Link encap:Ethernet HWaddr 00:50:8D:94:71:4A > inet addr:67.184.153.5 Bcast:255.255.255.255 Mask:255.255.248.0 > inet6 addr: fe80::250:8dff:fe94:714a/64 Scope:Link > UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:172324 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1904 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:12503150 (11.9 Mb) TX bytes:371462 (362.7 Kb) > > eth1 Link encap:Ethernet HWaddr 00:50:8D:94:71:4B > 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:5 Base address:0xa000 > > 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:502 errors:0 dropped:0 overruns:0 frame:0 > TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:49132 (47.9 Kb) TX bytes:49132 (47.9 Kb) > > 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 MTU:1500 Metric:1 > RX packets:172405 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1953 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:12507544 (11.9 Mb) TX bytes:377357 (368.5 Kb) > Interrupt:11 Base address:0x4000 > > sit0 Link encap:IPv6-in-IPv4 > NOARP MTU:1480 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) > > tun0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 > inet6 addr: fe80::fcae:66ff:fe79:1813/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:31 errors:0 dropped:0 overruns:0 frame:0 > TX packets:843 errors:0 dropped:0 overruns:2 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:4101 (4.0 Kb) TX bytes:52246 (51.0 Kb) > > 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) > > veth4 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) > > veth5 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) > > veth6 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) > > veth7 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 > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:1904 errors:0 dropped:0 overruns:0 frame:0 > TX packets:172324 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:371462 (362.7 Kb) TX bytes:12503150 (11.9 Mb) > > 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) > > vif0.4 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.5 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.6 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.7 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) > > vif2.0 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:6 errors:0 dropped:0 overruns:0 frame:0 > TX packets:148584 errors:0 dropped:1800 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:468 (468.0 b) TX bytes:9013081 (8.5 Mb) > > vif2.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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:150390 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > vif3.0 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:0 errors:0 dropped:861 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:170009 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:7939155 (7.5 Mb) TX bytes:0 (0.0 b) > > > I''ll be happy to provide any other information to help identify the issue. >Couple of things: I myself find it helpful to hardcode the vifnames so that my SNMP reporting of bandwidth stays consistent. Second, iptables is not your friend for Xen: can you turn off the firewall on this machine for a few moments and see if you get your networking to your guest domains? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-29 13:20 UTC
Re: [Xen-users] Need help setting up guest''s networking
Nico, I did have my firewall turned off. What would be an example of hard-coding a vif name? Also, I''ve discovered that I could manually assign an IP address to a vif interface in Dom0. This way I could network between the Dom0 and DomU, but could not establish an Internet connection from the DomU. My attempt to set the network interface of DomU to dhcp did not work either. Best regards, -Eugene On Apr 29, 2007, at 2:27 AM, Nico Kadel-Garcia wrote:> YEVGENIY GOLDBERG wrote: >> Greetings! >> >> I finally got the install done for a couple of gust OSs (Win 2003 >> server & Suse Enterprise 10) >> Bothe gusts are up and running, but - no networking. >> >> My setup: >> >> Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 >> onboard GB NICs >> Host OS- Suse Linux Enterprise server 10 >> Xen - 3.0.2_09749-0.4 >> >> Config file for Win 2003 server guest: >> >> # -*- mode: python; -*- >> #==================================================================== >> =======>> # Python configuration setup for ''xm create''. >> # This script sets the parameters used when a domain is created >> using ''xm create''. >> # You use a separate script for each domain you want to create, or >> # you can set the parameters for the domain on the xm command line. >> #==================================================================== >> =======>> >> import os, re >> arch = os.uname()[4] >> if re.search(''64'', arch): >> arch_libdir = ''lib64'' >> else: >> arch_libdir = ''lib'' >> >> #-------------------------------------------------------------------- >> -------- >> # Kernel image file. >> kernel = "/usr/lib/xen/boot/hvmloader" >> >> # The domain build function. HVM domain uses ''hvm''. >> builder=''hvm'' >> >> # Initial memory allocation (in megabytes) for the new domain. >> # >> # WARNING: Creating a domain with insufficient memory may cause >> out of >> # memory errors. The domain needs enough memory to boot >> kernel >> # and modules. Allocating less than 32MBs is not >> recommended. >> memory = 512 >> >> # Shadow pagetable memory for the domain, in MB. >> # Should be at least 2KB per MB of domain memory, plus a few MB >> per vcpu. >> shadow_memory = 8 >> >> # A name for your domain. All domains must have different names. >> name = "win2003server" >> >> # 128-bit UUID for the domain. The default behavior is to >> generate a new UUID >> # on each call to ''xm create''. >> #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" >> >> #-------------------------------------------------------------------- >> --------- >> # the number of cpus guest platform has, default=1 >> #vcpus=1 >> >> # enable/disable HVM guest PAE, default=0 (disabled) >> #pae=0 >> >> # enable/disable HVM guest ACPI, default=0 (disabled) >> #acpi=0 >> >> # enable/disable HVM guest APIC, default=0 (disabled) >> #apic=0 >> >> # List of which CPUS this domain is allowed to use, default Xen picks >> #cpus = "" # leave to Xen to pick >> #cpus = "0" # all vcpus run on CPU0 >> #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 >> >> # Optionally define mac and/or bridge for the network interfaces. >> # Random MACs are assigned if not given. >> vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0'' ] >> # type=ioemu specify the NIC is an ioemu device not netfront >> #vif = [ ''type=ioemu, bridge=xenbr0'' ] >> >> #-------------------------------------------------------------------- >> -------- >> # Define the disk devices you want the domain to have access to, and >> # what you want them accessible as. >> # Each disk entry is of the form phy:UNAME,DEV,MODE >> # where UNAME is the device, DEV is the device name the domain >> will see, >> # and MODE is r for read-only, w for read-write. >> >> #disk = [ ''phy:hda1,hda1,r'' ] >> disk = [ ''file:/var/lib/xen/images/windisk.img,ioemu:hda,w'', ''phy:/ >> dev/hda,hdb,r'' ] >> cdrom="/media/disk/iso/win2003server.iso" >> >> #-------------------------------------------------------------------- >> -------- >> # Configure the behaviour when a domain exits. There are three >> ''reasons'' >> # for a domain to stop: poweroff, reboot, and crash. For each of >> these you >> # may specify: >> # >> # "destroy", meaning that the domain is cleaned up as >> normal; >> # "restart", meaning that a new domain is started in >> place of the old >> # one; >> # "preserve", meaning that no clean-up is done until the >> domain is >> # manually destroyed (using xm destroy, for >> example); or >> # "rename-restart", meaning that the old domain is not cleaned >> up, but is >> # renamed and a new domain started in its place. >> # >> # The default is >> # >> on_poweroff = ''destroy'' >> on_reboot = ''destroy'' >> on_crash = ''destroy'' >> # >> # For backwards compatibility we also support the deprecated >> option restart >> # >> # restart = ''onreboot'' means on_poweroff = ''destroy'' >> # on_reboot = ''restart'' >> # on_crash = ''destroy'' >> # >> # restart = ''always'' means on_poweroff = ''restart'' >> # on_reboot = ''restart'' >> # on_crash = ''restart'' >> # >> # restart = ''never'' means on_poweroff = ''destroy'' >> # on_reboot = ''destroy'' >> # on_crash = ''destroy'' >> >> #on_poweroff = ''destroy'' >> #on_reboot = ''restart'' >> #on_crash = ''restart'' >> >> #==================================================================== >> =======>> >> # New stuff >> device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' >> >> #-------------------------------------------------------------------- >> --------- >> # boot on floppy (a), hard disk (c) or CD-ROM (d) >> # default: hard disk, cd-rom, floppy >> boot="c" >> >> #-------------------------------------------------------------------- >> --------- >> # write to temporary files instead of disk image files >> #snapshot=1 >> >> #-------------------------------------------------------------------- >> -------- >> # enable SDL library for graphics, default = 0 >> sdl=1 >> >> #-------------------------------------------------------------------- >> -------- >> # enable VNC library for graphics, default = 1 >> vnc=0 >> >> #-------------------------------------------------------------------- >> -------- >> # address that should be listened on for the VNC server if vnc is >> set. >> # default is to use ''vnc-listen'' setting from /etc/xen/xend- >> config.sxp >> #vnclisten="127.0.0.1" >> >> #-------------------------------------------------------------------- >> -------- >> # set VNC display number, default = domid >> #vncdisplay=1 >> >> #-------------------------------------------------------------------- >> -------- >> # try to find an unused port for the VNC server, default = 1 >> #vncunused=1 >> >> #-------------------------------------------------------------------- >> -------- >> # enable spawning vncviewer for domain''s console >> # (only valid when vnc=1), default = 0 >> #vncconsole=0 >> vncviewer=0 >> >> #-------------------------------------------------------------------- >> -------- >> # no graphics, use serial port >> #nographic=0 >> >> #-------------------------------------------------------------------- >> -------- >> # enable stdvga, default = 0 (use cirrus logic device model) >> stdvga=0 >> >> #-------------------------------------------------------------------- >> --------- >> # serial port re-direct to pty deivce, /dev/pts/n >> # then xm console or minicom can connect >> serial=''pty'' >> >> >> #-------------------------------------------------------------------- >> --------- >> # enable sound card support, [sb16|es1370|all|..,..], default none >> #soundhw=''sb16'' >> >> >> #-------------------------------------------------------------------- >> --------- >> # set the real time clock to local time [default=0 i.e. set to >> utc] >> #localtime=1 >> >> >> #-------------------------------------------------------------------- >> --------- >> # start in full screen >> #full-screen=1 >> >> >> #-------------------------------------------------------------------- >> --------- >> # Enable USB support (specific devices specified at runtime >> through the >> # monitor window) >> #usb=1 >> >> # Enable USB mouse support (only enable one of the following, >> `mouse'' for >> # PS/2 protocol relative mouse, >> `tablet'' for >> # absolute mouse) >> #usbdevice=''mouse'' >> #usbdevice=''tablet'' >> >> >> >> Config file for Suse Linux Enterprise 10 guest: >> >> disk = [ ''file:/var/lib/xen/images/OraDb1/hda,hda,w'', ''phy:/dev/ >> hda,hdb,r'' ] >> memory = 1024 >> vcpus = 2 >> builder = ''linux'' >> name = ''OraDb1'' >> vif = [ ''mac=00:16:3e:f3:64:e9'',''bridge=xenbr0''] >> localtime = 0 >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> extra = '' TERM=xterm'' >> bootloader = ''/usr/lib/xen/boot/domUloader.py'' >> bootentry = ''hda2:/boot/vmlinuz-xen,/boot/initrd-xen'' >> boot="c" >> >> >> >> out put of brctl show: >> >> bridge name bridge id STP enabled interfaces >> xenbr0 8000.feae66791813 no vif0.0 >> peth0 >> vif2.1 >> vif2.0 >> tun0 >> vif3.0 >> >> >> Output of ifconfig on the host: >> >> >> eth0 Link encap:Ethernet HWaddr 00:50:8D:94:71:4A >> inet addr:67.184.153.5 Bcast:255.255.255.255 Mask: >> 255.255.248.0 >> inet6 addr: fe80::250:8dff:fe94:714a/64 Scope:Link >> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 >> Metric:1 >> RX packets:172324 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:1904 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:12503150 (11.9 Mb) TX bytes:371462 (362.7 Kb) >> >> eth1 Link encap:Ethernet HWaddr 00:50:8D:94:71:4B >> 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:5 Base address:0xa000 >> >> 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:502 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:49132 (47.9 Kb) TX bytes:49132 (47.9 Kb) >> >> 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 MTU:1500 Metric:1 >> RX packets:172405 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:1953 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:12507544 (11.9 Mb) TX bytes:377357 (368.5 Kb) >> Interrupt:11 Base address:0x4000 >> >> sit0 Link encap:IPv6-in-IPv4 >> NOARP MTU:1480 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) >> >> tun0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 >> inet6 addr: fe80::fcae:66ff:fe79:1813/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:31 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:843 errors:0 dropped:0 overruns:2 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:4101 (4.0 Kb) TX bytes:52246 (51.0 Kb) >> >> 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) >> >> veth4 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) >> >> veth5 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) >> >> veth6 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) >> >> veth7 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 >> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:1904 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:172324 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:371462 (362.7 Kb) TX bytes:12503150 (11.9 Mb) >> >> 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) >> >> vif0.4 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.5 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.6 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.7 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) >> >> vif2.0 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:6 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:148584 errors:0 dropped:1800 overruns:0 >> carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:468 (468.0 b) TX bytes:9013081 (8.5 Mb) >> >> vif2.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:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:150390 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif3.0 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:0 errors:0 dropped:861 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> xenbr0 Link encap:Ethernet HWaddr FE:AE:66:79:18:13 >> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:170009 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:7939155 (7.5 Mb) TX bytes:0 (0.0 b) >> >> >> I''ll be happy to provide any other information to help identify >> the issue. >> > Couple of things: I myself find it helpful to hardcode the vifnames > so that my SNMP reporting of bandwidth stays consistent. Second, > iptables is not your friend for Xen: can you turn off the firewall > on this machine for a few moments and see if you get your > networking to your guest domains? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2007-Apr-29 13:34 UTC
Re: [Xen-users] Need help setting up guest''s networking
Yevgeniy Goldberg wrote:> Nico, > I did have my firewall turned off. > What would be an example of hard-coding a vif name? > Also, I''ve discovered that I could manually assign an IP address to a > vif interface in Dom0. > This way I could network between the Dom0 and DomU, but could not > establish an Internet connection from the DomU. > My attempt to set the network interface of DomU to dhcp did not work > either.The vifnames are set in the "vif=" configuration statement. So vif = [ ''mac=MACADDRESS, bridge=xenbr0'' ] would become vif = [ ''vifname=xen0.01,mac=MACADDRESS, bridge=xenbr0'' ] Setting the IP address of a network port is not the right job for Xen itself: it''s the right job for the guest domain, which has all the network configuration tools built in normally, and itself needs to know the netmask and gateway address. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-29 14:03 UTC
Re: [Xen-users] Need help setting up guest''s networking
Nico, Wouldn''t vif name assigned by xeb based on the Domain id? (ie if the DomU is 5 then it will become vif5.0) Alos, I''ve misspoke when I said that I was setting the static IP for the guest''s vif from the Dom0 - I was doing that inside the actual DomU. Also, I have a win 2003 server guest on the same xen host and networking works just fine on that one. Both configs are found in my initial post. Let me know what you think and THANK YOU FOR TRYING TO HELP ME! -Eugene On Apr 29, 2007, at 8:34 AM, Nico Kadel-Garcia wrote:> Yevgeniy Goldberg wrote: >> Nico, >> I did have my firewall turned off. >> What would be an example of hard-coding a vif name? >> Also, I''ve discovered that I could manually assign an IP address >> to a vif interface in Dom0. >> This way I could network between the Dom0 and DomU, but could not >> establish an Internet connection from the DomU. >> My attempt to set the network interface of DomU to dhcp did not >> work either. > The vifnames are set in the "vif=" configuration statement. So > > vif = [ ''mac=MACADDRESS, bridge=xenbr0'' ] > > would become > > vif = [ ''vifname=xen0.01,mac=MACADDRESS, bridge=xenbr0'' ] > > Setting the IP address of a network port is not the right job for > Xen itself: it''s the right job for the guest domain, which has all > the network configuration tools built in normally, and itself needs > to know the netmask and gateway address. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2007-Apr-29 14:27 UTC
Re: [Xen-users] Need help setting up guest''s networking
Yevgeniy Goldberg wrote:> Nico, > Wouldn''t vif name assigned by xeb based on the Domain id? (ie if the > DomU is 5 then it will become vif5.0) > Alos, > I''ve misspoke when I said that I was setting the static IP for the > guest''s vif from the Dom0 - I was doing that inside the actual DomU. > Also, I have a win 2003 server guest on the same xen host and > networking works just fine on that one. > Both configs are found in my initial post. > Let me know what you think and THANK YOU FOR TRYING TO HELP ME!From experience, if you do "xm shutdown DOMAIN" and "xm create DOMAIN", it winds up with a new vifname unless it''s hard-coded, much the same way you wind up with a new MAC address unless you hard-code it. The vifname renaming makes SNMP tracking of traffic for specific domains a serious pain. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, 2007-04-29 at 09:03 -0500, Yevgeniy Goldberg wrote:> Nico, > Wouldn''t vif name assigned by xeb based on the Domain id? (ie if the > DomU is 5 then it will become vif5.0)Its logical to assign vifnames that correspond to the domname + device as seen within the dom-u. If my dom-u was named foo, and the device was to become eth0 in foo, I would name the vif foo.0 , eth1 in foo would be foo.1 , eth2 would be foo.2 (for a max of three vif''s per guest). This lets me do all of my bandwidth accounting just reading /proc/net/dev directly with grawk ( http://echoreply.us/2007/04/25/grawk-100-released/ ) rather easily. I try to avoid snmp or anything else that malloc()s way more than it needs on dom-0 for obvious reasons :)> Alos, > I''ve misspoke when I said that I was setting the static IP for the > guest''s vif from the Dom0 - I was doing that inside the actual DomU. > Also, I have a win 2003 server guest on the same xen host and > networking works just fine on that one. > Both configs are found in my initial post. > Let me know what you think and THANK YOU FOR TRYING TO HELP ME!Are the guests using the same subnet (netmask) as the the bridge serving them? In other words, the IP address of your guest not working ends in a number equal or lesser than the broadcast address of the bridge? Best, --Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-29 15:32 UTC
Re: [Xen-users] Need help setting up guest''s networking
Hi Tim,
The guest that has network issues is suppose to use dhcp and that is
the part that is not working.
When I run ifconfig -a on the xen host OS (Dom0) I get the following:
From: thegoldberg@mac.com
Subject: ifconfig
Date: April 29, 2007 10:31:22 AM CDT
To: thegoldberg@mac.com
eth0 Link encap:Ethernet HWaddr 00:50:8D:94:71:4A
inet addr:67.184.153.5 Bcast:255.255.255.255 Mask:
255.255.248.0
inet6 addr: fe80::250:8dff:fe94:714a/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:628903 errors:0 dropped:0 overruns:0 frame:0
TX packets:828 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38759832 (36.9 Mb) TX bytes:114555 (111.8 Kb)
eth1 Link encap:Ethernet HWaddr 00:50:8D:94:71:4B
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:5 Base address:0xa000
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:223698 errors:0 dropped:0 overruns:0 frame:0
TX packets:223698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28526525 (27.2 Mb) TX bytes:28526525 (27.2 Mb)
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 MTU:1500 Metric:1
RX packets:629335 errors:0 dropped:0 overruns:0 frame:0
TX packets:972 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:38813257 (37.0 Mb) TX bytes:156020 (152.3 Kb)
Interrupt:11 Base address:0x4000
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
veth4 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)
veth5 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)
veth6 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)
veth7 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
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:828 errors:0 dropped:0 overruns:0 frame:0
TX packets:628903 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:114555 (111.8 Kb) TX bytes:38759832 (36.9 Mb)
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)
vif0.4 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.5 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.6 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.7 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)
vif6.0 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:0 errors:0 dropped:72073 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:627484 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:29099604 (27.7 Mb) TX bytes:0 (0.0 b)
Let me know what you think.
Best regards,
-Eugene
On Apr 29, 2007, at 9:30 AM, Tim Post wrote:
> On Sun, 2007-04-29 at 09:03 -0500, Yevgeniy Goldberg wrote:
>> Nico,
>> Wouldn''t vif name assigned by xeb based on the Domain id? (ie
if the
>> DomU is 5 then it will become vif5.0)
>
> Its logical to assign vifnames that correspond to the domname + device
> as seen within the dom-u.
>
> If my dom-u was named foo, and the device was to become eth0 in foo, I
> would name the vif foo.0 , eth1 in foo would be foo.1 , eth2 would be
> foo.2 (for a max of three vif''s per guest).
>
> This lets me do all of my bandwidth accounting just
> reading /proc/net/dev directly with grawk
> ( http://echoreply.us/2007/04/25/grawk-100-released/ ) rather easily.
>
> I try to avoid snmp or anything else that malloc()s way more than it
> needs on dom-0 for obvious reasons :)
>
>> Alos,
>> I''ve misspoke when I said that I was setting the static IP for
the
>> guest''s vif from the Dom0 - I was doing that inside the actual
DomU.
>> Also, I have a win 2003 server guest on the same xen host and
>> networking works just fine on that one.
>> Both configs are found in my initial post.
>> Let me know what you think and THANK YOU FOR TRYING TO HELP ME!
>
> Are the guests using the same subnet (netmask) as the the bridge
> serving
> them? In other words, the IP address of your guest not working ends
> in a
> number equal or lesser than the broadcast address of the bridge?
>
> Best,
> --Tim
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-29 15:53 UTC
Re: [Xen-users] Need help setting up guest''s networking
My physical eth1 is currently unused. It may be a good idea for me to use that in association with xen bridge. How do I make xen bridge to use eth1 instead of eth0? Once I do that, I should be able to assign a local IP to it without loosing Internet connectivity for Dom0. Then I will follow the rest of your plan. Best regards, -Eugene On Apr 29, 2007, at 10:45 AM, Tim Post wrote:> On Sun, 2007-04-29 at 10:32 -0500, Yevgeniy Goldberg wrote: >> Hi Tim, >> The guest that has network issues is suppose to use dhcp and that is >> the part that is not working. >> When I run ifconfig -a on the xen host OS (Dom0) I get the following: > > Your bridge (xenbr0) does not appear to have an IPV4 address. > >> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:627484 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:29099604 (27.7 Mb) TX bytes:0 (0.0 b) > > ... nor does your non-enslaved secondary ethernet device (eth1). > Something is telling me you have something wrong with your DHCP > configuration. > > Can you paste anything related to dhcp from syslog on the dhcp server > itself? > > Better yet, for purposes of eliminating Xen as part of this > problem, can > you assign a static address and subnet to eth0 (which appears to > become > enslaved to xenbr0 via network-bridge), as well as specifying a static > IP and subnet from within the dom-u? From your ifconfig dump, it looks > like network-bridge is doing its job correctly. > > Please note, if macs change, you may have to ping outward from within > dom-0 (and the dom-u) prior to either being able to see incoming > traffic. 4.2.2.2 or 4.2.2.3 are good hosts to ping for this purpose. > > Best, > --Tim > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, 2007-04-29 at 10:53 -0500, Yevgeniy Goldberg wrote:> My physical eth1 is currently unused. > It may be a good idea for me to use that in association with xen bridge. > How do I make xen bridge to use eth1 instead of eth0? > Once I do that, I should be able to assign a local IP to it without > loosing Internet connectivity for Dom0. > Then I will follow the rest of your plan.you would do that with ifconfig and brctl, see the functions in /etc/xen/scripts/* for a better blow by blow of how to accomplish (manually) the stuff that Xen does. This should get you going for a test : brctl addbr brtest brctl stp brtest off brctl setfd brtest off ip link set brtest arp off ip link set brtest multicast off Now, use ifconfig to assign the static IP / netmask to testbr like you would any other network interface. Finally, brctl addif testbr eth1 At this point, you have enslaved eth1 to brtest. You would then need to specify brtest to your dom-u in the bridge= part of the vif[] array in its configuration file. Bridged networking is a big vitamin to swallow if your not used to it, so don''t get discouraged over it. Many seasoned GNU/Linux administrators draw a blank on it simply because they have never had to bother with it before. Let the list know how it goes. If you eliminate the DHCP server as the cause (i.e. test bridge is no go too), I''m sure someone else can help you pick up on nailing this down. I''m off to 24 hours of R&R where there is no electricity, much less computers :) Best, --Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry for the double post, I meant to include this reference link as a footnote : http://linux-net.osdl.org/index.php/Bridge#Kernel_Configuration A great (rest of) the weekend to all :) Best, --Tim On Sun, 2007-04-29 at 10:53 -0500, Yevgeniy Goldberg wrote:> My physical eth1 is currently unused. > It may be a good idea for me to use that in association with xen bridge. > How do I make xen bridge to use eth1 instead of eth0? > Once I do that, I should be able to assign a local IP to it without > loosing Internet connectivity for Dom0. > Then I will follow the rest of your plan. > > Best regards, > > -Eugene > On Apr 29, 2007, at 10:45 AM, Tim Post wrote: > > > On Sun, 2007-04-29 at 10:32 -0500, Yevgeniy Goldberg wrote: > >> Hi Tim, > >> The guest that has network issues is suppose to use dhcp and that is > >> the part that is not working. > >> When I run ifconfig -a on the xen host OS (Dom0) I get the following: > > > > Your bridge (xenbr0) does not appear to have an IPV4 address. > > > >> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > >> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > >> RX packets:627484 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:29099604 (27.7 Mb) TX bytes:0 (0.0 b) > > > > ... nor does your non-enslaved secondary ethernet device (eth1). > > Something is telling me you have something wrong with your DHCP > > configuration. > > > > Can you paste anything related to dhcp from syslog on the dhcp server > > itself? > > > > Better yet, for purposes of eliminating Xen as part of this > > problem, can > > you assign a static address and subnet to eth0 (which appears to > > become > > enslaved to xenbr0 via network-bridge), as well as specifying a static > > IP and subnet from within the dom-u? From your ifconfig dump, it looks > > like network-bridge is doing its job correctly. > > > > Please note, if macs change, you may have to ping outward from within > > dom-0 (and the dom-u) prior to either being able to see incoming > > traffic. 4.2.2.2 or 4.2.2.3 are good hosts to ping for this purpose. > > > > Best, > > --Tim > > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-Apr-30 13:49 UTC
Re: [Xen-users] Need help setting up guest''s networking
After reading some entries from the syslog I''ve discovered: "ifup: xenbr0 configuration not found: Could this be the underlying cause of not having networking in my SLES 10 guest? -Eugene On Apr 29, 2007, at 11:47 AM, Tim Post wrote:> > On Sun, 2007-04-29 at 10:53 -0500, Yevgeniy Goldberg wrote: >> My physical eth1 is currently unused. >> It may be a good idea for me to use that in association with xen >> bridge. >> How do I make xen bridge to use eth1 instead of eth0? >> Once I do that, I should be able to assign a local IP to it without >> loosing Internet connectivity for Dom0. >> Then I will follow the rest of your plan. > > you would do that with ifconfig and brctl, see the functions > in /etc/xen/scripts/* for a better blow by blow of how to accomplish > (manually) the stuff that Xen does. > > This should get you going for a test : > > brctl addbr brtest > brctl stp brtest off > brctl setfd brtest off > > ip link set brtest arp off > ip link set brtest multicast off > > Now, use ifconfig to assign the static IP / netmask to testbr like you > would any other network interface. > > Finally, > > brctl addif testbr eth1 > > At this point, you have enslaved eth1 to brtest. You would then > need to > specify brtest to your dom-u in the bridge= part of the vif[] array in > its configuration file. > > Bridged networking is a big vitamin to swallow if your not used to it, > so don''t get discouraged over it. Many seasoned GNU/Linux > administrators > draw a blank on it simply because they have never had to bother > with it > before. > > Let the list know how it goes. If you eliminate the DHCP server as the > cause (i.e. test bridge is no go too), I''m sure someone else can help > you pick up on nailing this down. I''m off to 24 hours of R&R where > there > is no electricity, much less computers :) > > Best, > --Tim > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yevgeniy Goldberg
2007-May-03 01:01 UTC
Re: [Xen-users] Need help setting up guest''s networking
Hi Tim, I''ve made some progress with VM networking. My initial issue was that the forcedeth driver was not loading as it should. Now that is fixed. My next problem is - how to make my guest VMs recognize the second physical NIC (eth1) Ideally, I would like to have 2 network interfaces available to each guest - one for Internet and one for internal network. The Internet part seem to work now. I''ve tried your suggestion and created a second bridge. So far I could not make it to work. Please, let me know what information I could provide to make this work. Best regards, -Eugene On Apr 29, 2007, at 11:47 AM, Tim Post wrote:> > On Sun, 2007-04-29 at 10:53 -0500, Yevgeniy Goldberg wrote: >> My physical eth1 is currently unused. >> It may be a good idea for me to use that in association with xen >> bridge. >> How do I make xen bridge to use eth1 instead of eth0? >> Once I do that, I should be able to assign a local IP to it without >> loosing Internet connectivity for Dom0. >> Then I will follow the rest of your plan. > > you would do that with ifconfig and brctl, see the functions > in /etc/xen/scripts/* for a better blow by blow of how to accomplish > (manually) the stuff that Xen does. > > This should get you going for a test : > > brctl addbr brtest > brctl stp brtest off > brctl setfd brtest off > > ip link set brtest arp off > ip link set brtest multicast off > > Now, use ifconfig to assign the static IP / netmask to testbr like you > would any other network interface. > > Finally, > > brctl addif testbr eth1 > > At this point, you have enslaved eth1 to brtest. You would then > need to > specify brtest to your dom-u in the bridge= part of the vif[] array in > its configuration file. > > Bridged networking is a big vitamin to swallow if your not used to it, > so don''t get discouraged over it. Many seasoned GNU/Linux > administrators > draw a blank on it simply because they have never had to bother > with it > before. > > Let the list know how it goes. If you eliminate the DHCP server as the > cause (i.e. test bridge is no go too), I''m sure someone else can help > you pick up on nailing this down. I''m off to 24 hours of R&R where > there > is no electricity, much less computers :) > > Best, > --Tim >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users