search for: xenstore_read_default

...t; = "$devmm" ] then echo 'local' return fi fi done local base_path="$XENBUS_BASE_PATH/$XENBUS_TYPE" for dom in $(xenstore-list "$base_path") do for dev in $(xenstore-list "$base_path/$dom") do d=$(xenstore_read_default "$base_path/$dom/$dev/physical-device" "") if [ "$d" = "$devmm" ] then if [ "$mode" = 'w' ] then if ! same_vm $dom then echo 'guest' return fi...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Is there a way to prevent hwaddr/mac address spoofing between DomU''s? So in a way ''binding'' a mac-address on boot time with a virtual interface? (with something like ebtables/arptables/etc?) Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla -

...get the following output: / //root@arndale:~# xl create -c vmDescriptor.cfg // //Parsing config from vmDescriptor.cfg// ///etc/xen/scripts/block: line 3: dirname: command not found// ///etc/xen/scripts/block: line 4: /block-common.sh: No such file or directory// ///etc/xen/scripts/block: line 208: xenstore_read_default: command not found// //libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block add [15289] exited with error status 1// //libxl: error: libxl_create.c:935:domcreate_launch_dm: unable to add disk devices// ///etc/xen/scripts/block: line 3: dirname: command not found//...

...vm_path}/uuid") openvswitch_external_id $dev "xen-vm-uuid" "$uuid" local mac=$(xenstore_read "$XENBUS_PATH/mac") openvswitch_external_id $dev "attached-mac" "$mac" } add_to_openvswitch () { local dev=$1 local bridge="$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")" local tag trunk if [[ $bridge =~ ^([^.:]+)(\.([[:digit:]]+))?(:([[:digit:]]+(:[[:digit:]]+)*))?$ ]]; then bridge="${BASH_REMATCH[1]}" tag="${BASH_REMATCH[3]}" trunk="${BASH_REMATCH[5...

I''m using vif-route as my network script. I''ve added set -x to the xen hotplug script change. I''ve also added a command to do a listing of the xenstore directory. Here''s the snippet: == ++ ip= +++ xenstore_read_default backend/vif/4/0/ip '''' +++ xenstore-read backend/vif/4/0/ip xenstore-read: couldn''t read path backend/vif/4/0/ip +++ echo '''' ++ ip= ++ xenstore-list backend/vif/4/0 mac state handle script frontend-id domain frontend ++ XENBUS_PATH=backend/vif/4/0 ++ vif=...

...s what. Then a couple of functions are initialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functions are modified versions of the same functions in Xen''s xen-script-common.sh file. I added line 191-198 for debugging, rather than calling the actual commands they fake their execution and only add a log entry. That''s why they are comme...

...$dev. An interface with name $vifname already exists." + fi + do_or_die ip link set "$dev" name "$vifname" +} if [ "$type_if" = vif ]; then # Check presence of compulsory args. @@ -74,9 +88,9 @@ if [ "$type_if" = vif ]; then vifname=$(xenstore_read_default "$XENBUS_PATH/vifname" "") if [ "$vifname" ] then - if [ "$command" == "online" ] && ! ip link show "$vifname" >&/dev/null + if [ "$command" == "online" ] then -...

...-35 /var/log/xen/xen-hotplug.log /etc/xen/scripts/vif-bridge: /etc/xen/scripts/vif-common.sh: line 66: syntax error: Bad fd number /etc/xen/scripts/vif-bridge: line 94: syntax error: Bad fd number i have checked the /etc/xen/scripts/vif-common.sh file i think there is no syntax error 57vifname=$(xenstore_read_default "$XENBUS_PATH/vifname" "") 58if [ "$vifname" ] 59then 60 if [ "$command" == "online" ] && ! ip link show "$vifname" >&/dev/null 61 then 62 do_or_die ip link set "$vif" name "$vifname" 63fi 64vif=&quot...

...bridge itself. # # up: # Enslaves the vif interface to the bridge. # # down: # Removes the vif interface from the bridge. #============================================================================ dir=$(dirname "$0") . "$dir/vif-common.sh" bridge=${bridge:-} bridge=$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge") if [ -z "${bridge}" ] then bridge=$(ovs-vsctl listbr | cut -d " " -f 1) if [ -z "${bridge}" ] then fatal "Could not find bridge and none was specified" fi fi tag=${tag:-} # Domain on VLAN ta...

...s what. Then a couple of functions are initialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functions are modified versions of the same functions in Xen''s xen-script-common.sh file. I added line 191-198 for debugging, rather than calling the actual commands they fake their execution and only add a log entry. That''s why they are comme...

.../uuid") + openvswitch_external_id $dev "xen-vm-uuid" "$uuid" + local mac=$(xenstore_read "$XENBUS_PATH/mac") + openvswitch_external_id $dev "attached-mac" "$mac" +} + +add_to_openvswitch () { + local dev=$1 + local bridge="$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")" + local tag trunk + + if [[ $bridge =~ ^([^.:]+)(\.([[:digit:]]+))?(:([[:digit:]]+(:[[:digit:]]+)*))?$ ]]; then + bridge="${BASH_REMATCH[1]}" + tag="${BASH_REMATCH[3]}" + trunk="${BASH_REM...

...vm_path}/uuid") openvswitch_external_id $dev "xen-vm-uuid" "$uuid" local mac=$(xenstore_read "$XENBUS_PATH/mac") openvswitch_external_id $dev "attached-mac" "$mac" } add_to_openvswitch () { local dev=$1 local bridge="$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")" local tag trunk if [[ $bridge =~ ^([^.:]+)(\.([[:digit:]]+))?(:([[:digit:]]+(:[[:digit:]]+)*))?$ ]]; then bridge="${BASH_REMATCH[1]}" tag="${BASH_REMATCH[3]}" trunk="${BASH_REMATCH[5...