DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 08:43 UTC
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@ing.boehringer-Ingelheim.com
* Phone: +49 (0)6132/77-98151
-----Ursprüngliche Nachricht-----
Von: Murillo Bernardes [mailto:mfbernardes@gmail.com]
Gesendet: Dienstag, 22. November 2005 16:23
An: DIEDERIT@ing.boehringer-ingelheim.com
Cc: xen-devel@lists.xensource.com
Betreff: Re: [Xen-devel] Problem with vif - help!!!!
On 11/22/05, DIEDERIT@ing.boehringer-ingelheim.com > 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@ing.boehringer-Ingelheim.com
> * Phone: +49 (0)6132/77-98151
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> 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@lists.xensource.com
http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 08:49 UTC
AW: [Xen-devel] Problem with vif - help!!!!
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@ing.boehringer-Ingelheim.com
* Phone: +49 (0)6132/77-98151
-----Ursprüngliche Nachricht-----
Von: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com]
Gesendet: Donnerstag, 24. November 2005 09:44
An: mfbernardes@gmail.com; DIEDERIT@ing.boehringer-ingelheim.com
Cc: xen-devel@lists.xensource.com
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@ing.boehringer-Ingelheim.com
* Phone: +49 (0)6132/77-98151
-----Ursprüngliche Nachricht-----
Von: Murillo Bernardes [mailto:mfbernardes@gmail.com]
Gesendet: Dienstag, 22. November 2005 16:23
An: DIEDERIT@ing.boehringer-ingelheim.com
Cc: xen-devel@lists.xensource.com
Betreff: Re: [Xen-devel] Problem with vif - help!!!!
On 11/22/05, DIEDERIT@ing.boehringer-ingelheim.com > 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@ing.boehringer-Ingelheim.com
> * Phone: +49 (0)6132/77-98151
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> 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@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 12:09 UTC
AW: [Xen-devel] Problem with vif - help!!!!
On Thu, Nov 24, 2005 at 01:09:52PM +0100, DIEDERIT@ing.boehringer-ingelheim.com wrote:> > brctl show offers me this result: > [root@ingpcxen002 ~]# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0Well there''s nothing wrong with that at all. vif-bridge does this: brctl show | cut -d " " -f 2 | cut -f 1 to get the bridge name, which should succeed, but it is complaining that this is returning nothing. Perhaps you could figure out why this command is not working. Otherwise, I''m stuck I''m afraid. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 12:40 UTC
AW: [Xen-devel] Problem with vif - help!!!!
I get this: [root@ingpcxen002 mercurial-0.7]# brctl show | cut -f 2 bridge id [root@ingpcxen002 mercurial-0.7]# brctl show | cut -f 1 bridge name xenbr0 [root@ingpcxen002 mercurial-0.7]# Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: Ewan Mellor [mailto:ewan@xensource.com] Gesendet: Donnerstag, 24. November 2005 13:21 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On Thu, Nov 24, 2005 at 01:09:52PM +0100, DIEDERIT@ing.boehringer-ingelheim.com wrote:> > brctl show offers me this result: > [root@ingpcxen002 ~]# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0Well there''s nothing wrong with that at all. vif-bridge does this: brctl show | cut -d " " -f 2 | cut -f 1 to get the bridge name, which should succeed, but it is complaining that this is returning nothing. Perhaps you could figure out why this command is not working. Otherwise, I''m stuck I''m afraid. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com> Is set -x in correct position? >Yes> log_priority="debug" > udev_log="yes"> Is this also correct?????Yes Now send what matters in /var/log/daemon.log (last logs, from udev) -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 13:29 UTC
AW: [Xen-devel] Problem with vif - help!!!!
I do not have a daemon.log Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: Murillo Bernardes [mailto:mfbernardes@gmail.com] Gesendet: Donnerstag, 24. November 2005 13:56 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com> Is set -x in correct position? >Yes> log_priority="debug" > udev_log="yes"> Is this also correct?????Yes Now send what matters in /var/log/daemon.log (last logs, from udev) -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote:> I do not have a daemon.loggrep -ri udev /var/log You probably will find udev logs. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-24 13:43 UTC
AW: [Xen-devel] Problem with vif - help!!!!
/var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttys7'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttys8'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttys9'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttysa'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttysb'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttysc'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttysd'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyse'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttysf'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt0'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt1'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt2'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt3'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt4'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt5'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt6'' /var/log/messages:Nov 24 15:36:50 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyt9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyta'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttytb'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttytc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttytd'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyte'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttytf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyu9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyua'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyub'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyuc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyud'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyue'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyuf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyv9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyva'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyvb'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyvc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyvd'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyve'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyvf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyw9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywa'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywb'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywd'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywe'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttywf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyx9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxa'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxb'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxd'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxe'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyxf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyy9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyya'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyyb'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyyc'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyyd'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyye'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyyf'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz0'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz1'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz2'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz3'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz4'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz5'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz6'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz7'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz8'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyz9'' /var/log/messages:Nov 24 15:36:51 ingpcxen002 udev[1335]: creating device node ''/dev/ttyza'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ttyzb'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ttyzc'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ttyzd'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ttyze'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ttyzf'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/vcs'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/vcs1'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/vcsa'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/vcsa1'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: configured rule in ''/etc/udev/rules.d/50-udev.rules'' at line 63 applied, added symlink ''floppy%e'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/fd0'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda1'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda2'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda3'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda5'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda6'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda7'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda8'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hda9'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: configured rule in ''/etc/udev/rules.d/50-udev.rules'' at line 68 applied, added symlink ''cdrom%e'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/hdc'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop0'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop1'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop2'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop3'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop4'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop5'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop6'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/loop7'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: configured rule in ''/etc/udev/rules.d/50-udev.rules'' at line 48 applied, added symlink ''ramdisk'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram0'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: configured rule in ''/etc/udev/rules.d/50-udev.rules'' at line 39 applied, added symlink ''ram'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram1'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram10'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram11'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram12'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram13'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram14'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram15'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram2'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram3'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram4'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram5'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram6'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram7'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram8'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 udev[1335]: creating device node ''/dev/ram9'' /var/log/messages:Nov 24 15:36:52 ingpcxen002 start_udev: Starting udev: succeeded /var/log/messages:Nov 24 15:36:53 ingpcxen002 udevsend[2667]: starting udevd daemon /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3049]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3050]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3051]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3052]: /etc/udev/udev.conf:23:32: unknown key '''' <30>Nov 24 14:37:03 udev[3052]: creating device node ''/dev/agpgart'' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3055]: /etc/udev/udev.conf:23:32: unknown key '''' <30>Nov 24 14:37:03 udev[3055]: creating device node ''/dev/md0'' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3058]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3059]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3060]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3061]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:03 ingpcxen002 udev[3062]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3063]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3064]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3065]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3066]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3067]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3068]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3068]: creating device node ''/dev/dm-0'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3071]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3071]: creating device node ''/dev/dm-1'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3074]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3074]: creating device node ''/dev/dm-2'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3077]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3077]: creating device node ''/dev/dm-3'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3079]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3081]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3081]: removing device node ''/dev/vcsa1'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3084]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3085]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3086]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3087]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3087]: creating device node ''/dev/vcsa1'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3079]: removing device node ''/dev/vcs1'' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3092]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:04 ingpcxen002 udev[3092]: creating device node ''/dev/vcs1'' /var/log/messages:Nov 24 14:37:07 ingpcxen002 udev[3202]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:07 ingpcxen002 udev[3208]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:07 ingpcxen002 udev[3219]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:37:07 ingpcxen002 udev[3226]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:38 ingpcxen002 udev[4801]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:38 ingpcxen002 udev[4802]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:38 ingpcxen002 udev[4811]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:38 ingpcxen002 udev[4803]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:38 ingpcxen002 udev[4812]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:49 ingpcxen002 udev[4858]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:49 ingpcxen002 udev[4859]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:55 ingpcxen002 udev[4931]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:38:55 ingpcxen002 udev[4932]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:42:00 ingpcxen002 udev[4965]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:42:00 ingpcxen002 udev[4973]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:42:00 ingpcxen002 udev[4968]: /etc/udev/udev.conf:23:32: unknown key '''' /var/log/messages:Nov 24 14:42:06 ingpcxen002 udev[5034]: /etc/udev/udev.conf:23:32: unknown key '''' Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: Murillo Bernardes [mailto:mfbernardes@gmail.com] Gesendet: Donnerstag, 24. November 2005 14:41 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote:> I do not have a daemon.loggrep -ri udev /var/log You probably will find udev logs. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote: Oh... Please, try to start a domain, and send only what is related to vif-bridge. Better, try this (exactly as is!) #!/bin/sh echo $(brctl show | cut -d " " -f 2 | cut -f 1) I should return the bridge name. As Ewan said, try to figure out why it is failing. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-25 07:06 UTC
AW: [Xen-devel] Problem with vif - help!!!!
I find out that this Part in the vif-bridge script is never reached. This is my output when I start ./vif-bridged: + echo ''vif-bridge edited Thomas Diedeirch November, 25, 2005'' vif-bridge edited Thomas Diedeirch November, 25, 2005 ++ brctl show ++ cut -d '' '' -f 2 ++ cut -f 1 + echo xenbr0 xenbr0 ++ dirname ./vif-bridge + dir=. + . ./vif-common.sh +++ dirname ./vif-bridge ++ dir=. ++ . ./xen-hotplug-common.sh ++++ dirname ./vif-bridge +++ dir=. +++ . ./xen-script-common.sh ++++ set -e +++ export PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr /local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/roo t/bin +++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr /local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/roo t/bin +++ export LANG=POSIX +++ LANG=POSIX ++++ set ++++ grep ''^LC_'' ++++ cut -d= -f1 +++ unset +++ log debug XENBUS_PATH+++ local level=debug +++ shift +++ logger -p daemon.debug -- ./vif-bridge: XENBUS_PATH++ . ./xen-network-common.sh +++ ''['' -e /etc/SuSE-release '']'' +++ which ifup ++ findCommand ++ ''['' '''' ''!='' online '']'' ++ ''['' '''' ''!='' offline '']'' ++ ''['' '''' ''!='' add '']'' ++ ''['' '''' ''!='' remove '']'' ++ log err ''Invalid command: '' ++ local level=err ++ shift ++ logger -p daemon.err -- ./vif-bridge: ''Invalid command: '' ++ exit 1 Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: Murillo Bernardes [mailto:mfbernardes@gmail.com] Gesendet: Donnerstag, 24. November 2005 17:08 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote: Oh... Please, try to start a domain, and send only what is related to vif-bridge. Better, try this (exactly as is!) #!/bin/sh echo $(brctl show | cut -d " " -f 2 | cut -f 1) I should return the bridge name. As Ewan said, try to figure out why it is failing. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-25 08:04 UTC
AW: [Xen-devel] Problem with vif - help!!!!
Ok, in vif-common.sh the variable $command is always empty. It gets it from findCommand §@ and this is running zero! Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] Gesendet: Freitag, 25. November 2005 08:06 An: mfbernardes@gmail.com; DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: AW: [Xen-devel] Problem with vif - help!!!! I find out that this Part in the vif-bridge script is never reached. This is my output when I start ./vif-bridged: + echo ''vif-bridge edited Thomas Diedeirch November, 25, 2005'' vif-bridge edited Thomas Diedeirch November, 25, 2005 ++ brctl show ++ cut -d '' '' -f 2 ++ cut -f 1 + echo xenbr0 xenbr0 ++ dirname ./vif-bridge + dir=. + . ./vif-common.sh +++ dirname ./vif-bridge ++ dir=. ++ . ./xen-hotplug-common.sh ++++ dirname ./vif-bridge +++ dir=. +++ . ./xen-script-common.sh ++++ set -e +++ export PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr /local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/roo t/bin +++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr /local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/roo t/bin +++ export LANG=POSIX +++ LANG=POSIX ++++ set ++++ grep ''^LC_'' ++++ cut -d= -f1 +++ unset +++ log debug XENBUS_PATH+++ local level=debug +++ shift +++ logger -p daemon.debug -- ./vif-bridge: XENBUS_PATH++ . ./xen-network-common.sh +++ ''['' -e /etc/SuSE-release '']'' +++ which ifup ++ findCommand ++ ''['' '''' ''!='' online '']'' ++ ''['' '''' ''!='' offline '']'' ++ ''['' '''' ''!='' add '']'' ++ ''['' '''' ''!='' remove '']'' ++ log err ''Invalid command: '' ++ local level=err ++ shift ++ logger -p daemon.err -- ./vif-bridge: ''Invalid command: '' ++ exit 1 Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: Murillo Bernardes [mailto:mfbernardes@gmail.com] Gesendet: Donnerstag, 24. November 2005 17:08 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On 11/24/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote: Oh... Please, try to start a domain, and send only what is related to vif-bridge. Better, try this (exactly as is!) #!/bin/sh echo $(brctl show | cut -d " " -f 2 | cut -f 1) I should return the bridge name. As Ewan said, try to figure out why it is failing. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/25/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote:> > > I find out that this Part in the vif-bridge script is never reached. > > This is my output when I start ./vif-bridged:You must see what happens when udev/hotplug start it. Because it depends on some environment variables and a command, like: XENBUS_PATH=backend/123/vif/0 /etc/xen/scripts/vif-bridge online Are you using RHEL4, right? Probably you don''t have udev logs because you are using hotplug, but I''m not sure. Xen can use udev only with udev version > 059. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-25 12:09 UTC
AW: [Xen-devel] Problem with vif - help!!!!
Yeah, this output seems clearer now: vif-bridge edited Thomas Diederich November, 25, 2005 ++ brctl show ++ cut -d '' '' -f 2 ++ cut -f 1 + echo xenbr0 xenbr0 ++ dirname /etc/xen/scripts/vif-bridge + dir=/etc/xen/scripts + . /etc/xen/scripts/vif-common.sh +++ dirname /etc/xen/scripts/vif-bridge ++ dir=/etc/xen/scripts ++ . /etc/xen/scripts/xen-hotplug-common.sh ++++ dirname /etc/xen/scripts/vif-bridge +++ dir=/etc/xen/scripts +++ . /etc/xen/scripts/xen-script-common.sh ++++ set -e +++ export PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/ke rberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin: /usr/X11R6/bin:/root/bin +++ PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/ bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X1 1R6/bin:/root/bin +++ export LANG=POSIX +++ LANG=POSIX ++++ set ++++ grep ''^LC_'' ++++ cut -d= -f1 +++ unset +++ log debug online XENBUS_PATH=backend/123/vif/0 +++ local level=debug +++ shift +++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: online XENBUS _PATH=backend/123/vif/0 ++ . /etc/xen/scripts/xen-network-common.sh +++ ''['' -e /etc/SuSE-release '']'' +++ which ifup ++ findCommand online ++ for arg in ''"$@"'' ++ expr index online ++ command=online ++ return ++ ''['' online ''!='' online '']'' ++ case "$command" in ++ evalVariables online ++ for arg in ''"$@"'' ++ expr index online = ''>'' 1 ++ ip+++ xenstore_read_default backend/123/vif/0/ip '''' +++ xenstore-read backend/123/vif/0/ip xenstore-read: couldn''t read path backend/123/vif/0/ip +++ echo '''' ++ ip++ XENBUS_PATH=backend/123/vif/0 /etc/xen/scripts/vif-common.sh: line 53: vif: parameter null or not set [root@ingpcxen002 ~]# But there are still errors and my problem is still alive. Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] Gesendet: Freitag, 25. November 2005 12:38 An: DIEDERIT@ing.boehringer-ingelheim.com Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] Problem with vif - help!!!! On 11/25/05, DIEDERIT@ing.boehringer-ingelheim.com <DIEDERIT@ing.boehringer-ingelheim.com> wrote:> > > I find out that this Part in the vif-bridge script is never reached. > > This is my output when I start ./vif-bridged:You must see what happens when udev/hotplug start it. Because it depends on some environment variables and a command, like: XENBUS_PATH=backend/123/vif/0 /etc/xen/scripts/vif-bridge online Are you using RHEL4, right? Probably you don''t have udev logs because you are using hotplug, but I''m not sure. Xen can use udev only with udev version > 059. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel