search for: xenbus_path

...PU E6550 @ 2.33GHz If I boot a non xen-kernel, I get the "vmx" cpu flag. Google didn''t help me either. syslog: ---8<--- Jun 15 09:30:28 debian init: Id "x0" respawning too fast: disabled for 5 minutes Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2050 Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2049 Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2080 Jun 15 09:30:29 debian logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/4/0 Jun 1...

This is on a snapshot from 11/12/2005 of unstable. I wrote some quick debug code into vif-route to see what is going on during runtime, ex: echo "xenbus_path = $XENBUS_PATH" >>/root/route.log echo "command = $command" >>/root/route.log After starting/stopping a domain a few times it contains: xenbus_path = backend/vif/20/0 command = online xenbus_path = backend/vif/21/0 command = online Is this a bug or is there some new wa...

line 52: XENBUS_PATH: parameter null or not set what the XENBUS_PATH is? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi There, I''ve installed xen 3 and xen-tools on my Debian etch server and all seems well, until I try to start a guest domain. debian:/home/xen# xm create /etc/xen/D4G3.cfg Using config file "/etc/xen/D4G3.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device

...$mode" = 'w' ] then m1='' m2='' else m1='read-write ' m2='read-only ' fi release_lock "block" ebusy \ "${prefix}${m1}in ${dom}domain, and so cannot be mounted ${m2}${when}." } t=$(xenstore_read_default "$XENBUS_PATH/type" 'MISSING') case "$command" in add) phys=$(xenstore_read_default "$XENBUS_PATH/physical-device" 'MISSING') if [ "$phys" != 'MISSING' ] then # Depending upon the hotplug configuration, it is possible for this #...

...and searching it > > seems to me like a problem in /etc/xen/scripts/vif-bridge > > But I miss the knowhow to tell what exactly goes wrong. > > > > Here is the from daemon.log when I run "xm create gerd.cfg -c" : > > > > /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2049 & gt; > /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2050 > > /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/4/0 > > /etc/xen/scripts/vif-bridge: Writing backend/vif/4/0/hotplug-status error > > to xenstore. /etc/xen/scripts/vif-...

...tenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6900 comm="/usr/sbin/hald)) May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/40/0 May 19 18:46:29 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=8950 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="Quer...

...Dec 6 08:41:51 davetho-intel udevsend[5696]: main: unable to connect to event daemon, try to call udev directly Dec 6 08:41:51 davetho-intel udevsend[5699]: main: unable to connect to event daemon, try to call udev directly Dec 6 08:41:51 davetho-intel logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/5/0 Dec 6 08:41:51 davetho-intel kernel: device vif5.0 entered promiscuous mode Dec 6 08:41:51 davetho-intel kernel: xenbr0: port 4(vif5.0) entering learning state Dec 6 08:41:51 davetho-intel kernel: xenbr0: topology change detected, propagating Dec 6 08:41:51 davetho-intel kernel:...

...cted to xenstore. Jun 7 16:11:44 alca2 kernel: [12533839.409637] blktap: ring-ref 8, event-channel 12, protocol 1 (x86_64-abi) Jun 7 16:11:44 alca2 kernel: [12533839.412361] blktap: ring-ref 9, event-channel 13, protocol 1 (x86_64-abi) Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51712 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51728 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51728 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap...

...to Xend, or the default Xend configuration # in ${XEN_CONFIG_DIR}/xend-config.sxp. If the script is specified in # neither of those places, then this script is the default. # # Usage: # vif-openvswitch (add|remove|online|offline) # # Environment vars: # vif vif interface name (required). # XENBUS_PATH path to this device''s details in the XenStore (required). # # Read from the store: # bridge openvswitch to add the vif to (required). # ip list of IP networks for the vif, space-separated (optional). # # up: # Enslaves the vif interface to the bridge and adds iptables rules # for its...

...re called by inserting a line ''logger "xen-backend xenbus_type:$XENBUS_TYPE script:$script action:$ACTION"'' to the beginning of /etc/hotplug/xen-backend.agent. Here are the relevant logfile excerpts: 1. syslog: Nov 25 00:51:39 nereus logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/8/2049 Nov 25 00:51:39 nereus logger: /etc/xen/scripts/block: Writing backend/vbd/8/2049/physical-device 0xfd00 backend/vbd/8/2049/node /dev/vg/fast.fqdn.org.root to xenstore. Nov 25 00:51:39 nereus logger: /etc/xen/scripts/block: Writing backend/vbd/8/2049/hotplug-status connected to x...

...l - here''s the output when I try with tap:aio: Apr 29 16:55:02 xen02 kernel: blkback: ring-ref 8, event-channel 38, protocol 1 (x86_64-abi) Apr 29 16:55:02 xen02 kernel: blkback: ring-ref 8, event-channel 38, protocol 1 (x86_64-abi) Apr 29 16:55:02 xen02 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/0/51952 Apr 29 16:56:42 xen02 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/0/51952 Apr 29 16:56:43 xen02 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/0/51952 Anyone have any hints as to what might be going on here? Any possible solutions?...

...gic driver on SLES 11, I was able to attached a NPIV disk to a virtual machine without problem. The bootable disk of this VM is on a file device. The problem is when I try to start a VM from a bootable NPIV disk. I receive the error "Error: Device 51952 not connected". I found that the XENBUS_PATH is set to /local/domain/0/backend/vbd/0. This is not the same when I start a VM (ex.: domain id = 1) that the bootable disk is on a file and I do "xm block-attach npiv:...". In this case, the XENBUS_PATH used is /local/domain/0/backend/vbd/1. I think that the disk is not suppose to be...

...connected. " VmError: Device 769 (vbd) could not be connected. Hotplug scripts not working However, based on the following passage from /var/log/messages, the relevant vbd backend *really did* start up and try to provide notification of its new state: logger: /etc/xen/scripts/block: bind XENBUS_PATH=backend/vbd/1/769 logger: /etc/xen/scripts/block: bind XENBUS_PATH=backend/vbd/1/770 logger: /etc/xen/scripts/block: Writing backend/vbd/1/770/physical-device 0xfd04 backend/vbd/1/770/node /dev/data/demo-1-swap to xenstore. changing physical-device not supported changing physical-device not suppo...

...connected. " VmError: Device 769 (vbd) could not be connected. Hotplug scripts not working However, based on the following passage from /var/log/messages, the relevant vbd backend *really did* start up and try to provide notification of its new state: logger: /etc/xen/scripts/block: bind XENBUS_PATH=backend/vbd/1/769 logger: /etc/xen/scripts/block: bind XENBUS_PATH=backend/vbd/1/770 logger: /etc/xen/scripts/block: Writing backend/vbd/1/770/physical-device 0xfd04 backend/vbd/1/770/node /dev/data/demo-1-swap to xenstore. changing physical-device not supported changing physical-device not suppo...

...changed:0 act_log: used:0/127 hits:6821 misses:25 starving:0 dirty:0 changed:25 Destroying/creating the old/new domain generates the udev remove/add events in correct order and cause a parallel execution of xen block scripts: Sep 24 16:59:32 srv logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/39/2049 Sep 24 16:59:32 srv logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/40/2049 Sep 24 16:59:32 srv logger: /etc/xen/scripts/block-drbd: add XENBUS_PATH=backend/vbd/40/2049 Sep 24 16:59:33 srv logger: /etc/xen/scripts/block-drbd: remove XENBUS_PATH=backend/vbd/39/2...

Hello, My name is Fermín Galán. I have started recently to use Xen (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected.

...or the default Xend configuration +# in ${XEN_CONFIG_DIR}/xend-config.sxp. If the script is specified in +# neither of those places, then this script is the default. +# +# Usage: +# vif-openvswitch (add|remove|online|offline) +# +# Environment vars: +# vif vif interface name (required). +# XENBUS_PATH path to this device''s details in the XenStore (required). +# +# Read from the store: +# bridge openvswitch to add the vif to (required). +# ip list of IP networks for the vif, space-separated (optional). +# +# up: +# Enslaves the vif interface to the bridge and adds iptables rules +#...

.../bash #============================================================================ # ${XEN_SCRIPT_DIR}/vif-openvswitch # # Script for configuring a vif in openvswitch mode. # # Usage: # vif-openvswitch (add|remove|online|offline) # # Environment vars: # vif vif interface name (required). # XENBUS_PATH path to this device's details in the XenStore (required). # # Read from the store: # bridge openvswitch to add the vif to (required). # ip list of IP networks for the vif, space-separated (optional). # # up: # Enslaves the vif interface to the bridge and adds iptables rules # for its ip a...

...piled fine and installs fine. When I run xl create it starts vm. I have vif devices created but they don''t attach to bridget that are created on startup . I have xenbr0 and xenbr1 created. If I run this I get vifi attached ro bridge. Is this xl issue or python. # export vif=vif1.0 # export XENBUS_PATH=/local/domain/0/backend/vif/1/0 (found with `xl network-list`) # export bridge=br0 # /etc/xen/scripts/vif-bridge add # /etc/xen/scripts/vif-bridge online It seems that xen has to be compileg with python 2.7 . I wonder if this well known bug are there any patches. _________________________________...