|
Yes, I modified the Config.
Here it
is:
[root@ingpcxen002 ~]# vi /etc/xen/xend-config.sxp
#
-*- sh -*-
#
# Xend configuration file.
#
# This example
configuration is appropriate for an installation that trusts
# only localhost
connections, and is otherwise fully functional, with a
# bridged network
configuration.
# Commented out entries show the default for that entry,
unless otherwise
# specified.
#(logfile
/var/log/xend.log)
#(loglevel DEBUG)
#(xend-http-server
no)
(xend-http-server yes)
#(xend-unix-server
yes)
#(xend-relocation-server no)
(xend-relocation-server
yes)
#(xend-unix-path /var/lib/xend/xend-socket)
# Port xend
should use for the HTTP interface, if xend-http-server is
set.
#(xend-port
8000)
# Port xend should use for the relocation interface, if
xend-relocation-server
# is set.
(xend-relocation-port 8002)
#
Address xend should listen on for HTTP connections, if xend-http-server is
#
set.
# Specifying 'localhost' prevents remote connections.
# Specifying
the empty string '' (the default) allows all connections.
(xend-address
'')
#(xend-address localhost)
# Address xend should listen on for
relocation-socket connections, if
# xend-relocation-server is set.
#
Meaning and default as for xend-address above.
#(xend-relocation-address
'')
(xend-relocation-address localhost)
# The limit (in kilobytes) on
the size of the console buffer
#(console-limit 1024)
##
# To bridge
network traffic, like this:
#
# dom0: fake eth0 -> vif0.0
-+
#
|
#
bridge -> real eth0 -> the
network
#
|
# domU: fake eth0 -> vifN.0 -+
#
# use
#
# (network-script
network-bridge)
#
# Your eth0 is used as the outgoing interface, by
default. To use a different
# one (e.g. eth1) use
#
#
(network-script 'network-bridge netdev=eth1')
#
# The bridge is named
xenbr0, by default. To rename the bridge, use
#
# (network-script
'network-bridge bridge=<name>')
#
# It is possible to use the
network-bridge script in more complicated
# scenarios, such as having two
outgoing interfaces, with two bridges, and
# two fake interfaces per guest
domain. To do things like this, write
# yourself a wrapper script, and
call network-bridge from it, as appropriate.
#
(network-script
network-bridge)
# The script used to control virtual interfaces.
This can be overridden on a
# per-vif basis when creating a domain or a
configuring a new vif. The
# vif-bridge script is designed for use with
the network-bridge script, or
# similar configurations.
#
# If you have
overridden the bridge name using
# (network-script 'network-bridge
bridge=<name>') then you may wish to do the
# same here. The
bridge name can also be set when creating a domain or
# configuring a new
vif, but a value specified here would act as a default.
#
# If you are
using only one bridge, the vif-bridge script will discover that,
# so there
is no need to specify it explicitly.
#
(vif-script
vif-bridge)
## Use the following if network traffic is routed, as an
alternative to the
# settings for bridged networking given
above.
#(network-script
network-route)
#(vif-script vif-route)
##
Use the following if network traffic is routed with NAT, as an alternative
#
to the settings for bridged networking given above.
#(network-script
network-nat)
#(vif-script vif-nat)
# Dom0
will balloon out when needed to free memory for domU.
# dom0-min-mem is the
lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0
will never balloon out.
(dom0-min-mem 0)
# In SMP system, dom0 will
use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus
available
(dom0-cpus 0)
# Whether to enable core-dumps when domains
crash.
#(enable-dump no)
BRCTL is installed, and after strating
network-bridge manually nothing is written in /var/log/messages.
brctl show offers me this result:
[root@ingpcxen002 ~]# brctl
show
bridge name bridge
id
STP enabled
interfaces
xenbr0
8000.feffffffffff
no
vif0.0
peth0
[root@ingpcxen002 ~]#
58,1 85%
Thomas
Diederich
**************************************************
*
Boehringer Ingelheim Pharma GmbH & Co.KG
* A
Informationsverarbeitung / Diplomant Systemtechnik
*
* Mail:
diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* Phone: +49
(0)6132/77-98151
-----Ursprüngliche Nachricht-----
Von: Ewan
Mellor [mailto:ewan@xxxxxxxxxxxxx]
Gesendet:
Donnerstag, 24. November 2005 12:03
An:
DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cc:
xen-devel@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [Xen-devel] Problem with vif -
help!!!!
On Thu, Nov 24, 2005 at 09:30:54AM +0100,
DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
> These are parts of my
messages
>
>
> Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget:
iget failed
> Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server -
nlink == 0!
> Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget
failed
> Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink ==
0!
> Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed
>
Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink == 0!
> Nov
22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed
> Nov 22 15:54:55
ingpcxen002 kernel: NFS: Buggy server - nlink == 0!
> Nov 22 15:54:55
ingpcxen002 kernel: nfs_fhget: iget failed
> Nov 22 15:55:56 ingpcxen002
logger: /etc/xen/scripts/vif-bridge: Could not
> find bridge, and none was
specified
It's this message that is the smoking gun. The vif-bridge
script cannot find
a bridge to attach to. Have you altered the basic
configuration
(/etc/xen/xend-config.sxp)? Do you have brctl installed
(though I thought
we'd fixed that test recently)? What version of Xen
are you using? What
happens when you run
/etc/xen/scripts/network-bridge start manually? Do you
get anything in
/var/log/messages then? What do you get when you type "brctl
show"
afterwards?
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home