Xend.log :
[2005-11-24 09:47:53 xend] DEBUG (DevController:302) DevController: writing
{'backend-id': '0', 'mac': '00:16:3e:79:41:f0', 'handle': '0', 'state': '1',
'backend': '/local/domain/0/backend/vif/8/0'} to
/local/domain/8/device/vif/0.
[2005-11-24 09:47:53 xend] DEBUG (DevController:304) DevController: writing
{'mac': '00:16:3e:79:41:f0', 'state': '1', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'frontend-id': '8', 'domain': 'RHEL4',
'frontend': '/local/domain/8/device/vif/0'} to
/local/domain/0/backend/vif/8/0.
[2005-11-24 09:47:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:602) Storing
VM details: {'ssidref': '0', 'uuid': '6197183c-768a-ea36-e57d-0be2f17ef434',
'on_reboot': 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6.12-xenU)
(ip 148.191.190.53:148.191.190.7::255.255.254.0::eth0:off) (root /dev/nfs)
(args 'nfsroot=148.191.190.7:/xen 3') (vcpus 1) (vcpus 1) (boot c) (display
localhost:10.0))", 'on_poweroff': 'destroy', 'name': 'RHEL4', 'vcpus': '1',
'vcpu_avail': '1', 'memory': '392', 'on_crash': 'restart', 'start_time':
'1132822073.44', 'maxmem': '392'}
[2005-11-24 09:47:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:627) Storing
domain details: {'console/ring-ref': '61391', 'console/port': '2', 'name':
'RHEL4', 'console/limit': '1048576', 'vm':
'/vm/6197183c-768a-ea36-e57d-0be2f17ef434', 'domid': '8',
'cpu/0/availability': 'online', 'memory/target': '401408', 'store/ring-ref':
'62836', 'store/port': '1'}
[2005-11-24 09:47:53 xend] DEBUG (DevController:88) Waiting for devices vif.
[2005-11-24 09:47:53 xend] DEBUG (DevController:94) Waiting for 0.
[2005-11-24 09:47:53 xend] DEBUG (DevController:361) hotplugStatusCallback
/local/domain/0/backend/vif/8/0/hotplug-status.
[2005-11-24 09:47:53 xend] DEBUG (DevController:361) hotplugStatusCallback
/local/domain/0/backend/vif/8/0/hotplug-status.
[2005-11-24 09:47:53 xend] DEBUG (DevController:376) hotplugStatusCallback
3.
[2005-11-24 09:47:53 xend] ERROR (SrvBase:87) Request wait_for_devices
failed.
Traceback (most recent call last):
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/xend/server/SrvDomain.py", line 68, in
op_wait_for_devices
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 1264, in
waitForDevices
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 912, in
waitForDevices_
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/xend/server/DevController.py", line 90,
in waitForDevices
File
"/local/scratch/xenod/cron-build/xen-unstable-x86_32p.g29771.dir/xen-unstabl
e.hg/dist/install/usr/lib/python/xen/xend/server/DevController.py", line
106, in waitForDevice
VmError: Device 0 (vif) could not be connected. Backend device not found
[2005-11-24 09:47:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:1186)
XendDomainInfo.destroy: domid=8
[2005-11-24 09:47:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:1194)
XendDomainInfo.destroyDomain(8)
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: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx]
Gesendet: Donnerstag, 24. November 2005 09:44
An: mfbernardes@xxxxxxxxx; DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Betreff: AW: [Xen-devel] Problem with vif - help!!!!
I can't exacly figure out what you mean.
Here is my vif-bridge:
# Enslaves the vif interface to the bridge and adds iptables rules
# for its ip addresses (if any).
#
# down:
# Removes the vif interface from the bridge and removes the iptables
# rules for its ip addresses (if any).
#===========================================================================
=
set -x
dir=$(dirname "$0")
. "$dir/vif-common.sh"
bridge=${bridge:-}
bridge=$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")
if [ -z "$bridge" ]
then
bridge=$(brctl show | cut -d "
" -f 2 | cut -f 1)
if [ -z "$bridge" ]
then
fatal "Could not find bridge, and none was specified"
fi
fi
case "$command" in
online)
if brctl show | grep "$vif" >&/dev/null
then
log debug "$vif already attached to a bridge"
exit 0
fi
brctl addif "$bridge" "$vif" ||
fatal "brctl addif $bridge $vif failed"
ifconfig "$vif" up || fatal "ifconfig $vif up failed"
;;
offline)
# vifs are auto-removed from bridge.
ifconfig "$vif" down || fatal "ifconfig $vif down failed"
;;
esac
handle_iptable
log debug "Successful vif-bridge operation for $vif, bridge $bridge."
success
74,1
Bot
*****
Is set -x in correct position?
And my udev.conf looks now like this.
[root@ingpcxen002 log]# vi /etc/udev/udev.conf
# udev.conf
# The main config file for udev
#
# This file can be used to override some of udev's default values
# for where it looks for files, and where it places device nodes.
#
# WARNING: changing any value, can cause serious system breakage!
#
# udev_root - where in the filesystem to place the device nodes
udev_root="/dev/"
# udev_db - The name and location of the udev database.
udev_db="/dev/.udev.tdb"
# udev_rules - The name and location of the udev rules file
udev_rules="/etc/udev/rules.d/"
# udev_permissions - The name and location of the udev permission file
udev_permissions="/etc/udev/permissions.d/"
#udev log
#udevcontrol
log_priority="debug"
# default_mode - set the default mode for all nodes that have no
# explicit match in the permissions file
default_mode="0600"
# default_owner - set the default owner for all nodes that have no
# explicit match in the permissions file
default_owner="root"
# default_group - set the default group for all nodes that have no
# explicit match in the permissions file
default_group="root"
# udev_log - set to "yes" if you want logging, else "no"
udev_log="yes"
Is this also correct?????
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: Murillo Bernardes [mailto:mfbernardes@xxxxxxxxx]
Gesendet: Dienstag, 22. November 2005 16:23
An: DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [Xen-devel] Problem with vif - help!!!!
On 11/22/05, DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx > This is my config file.
> When I replace nics=0 with nics=1 i get the following error:
>
> Error: Device 0 (vif) could not be connected. Backend device not found
>
> I need nics=1 because i need to connect to my nfs server where my domU is
> located.
>
> With nics=0 it won't also work beacuase "no eth0 could be found"
>
> Thomas Diederich
>
> **************************************************
> * Boehringer Ingelheim Pharma GmbH & Co.KG
> * A Informationsverarbeitung / Diplomant Systemtechnik
> *
> * Mail: diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> * Phone: +49 (0)6132/77-98151
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>
>
Are you using bridged network?
Could you add "set -x" to begining of
/etc/xen/scripts/vif-{bridge,route,nat} and set log_priority on udev
to debug? ("udevcontrol log_priority=debug" does that in runtime, or
you can set that on udev.conf and restart udevd)
After that you will have on /var/log/debug a very usefull log of
hotplug script responsible for setting up vif.
--
Murillo Fernandes Bernardes
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home