search for: xen_script_dir

I had another look at this and found the source of the problem - the reason why XEN_SCRIPT_DIR is not set: The hotplugpath.sh file is missing in the package. In the "rules" file the "install" target includes this line: $(MAKE) -C $(BUILD_DIR)/tools/hotplug/Linux install-udev install-scripts UDEV_RULES_DIR=/lib/udev/rules.d The problem is that make is never run...

...xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was not being driven. My work around was to modify /etc/xen/scripts/block; I replaced [ -x ${XEN_SCRIPT_DIR}/block-"$t" ] && \ ${XEN_SCRIPT_DIR}/block-"$t$" "$command" $node with [ -x /etc/xen/scripts/block-"$t" ] && \ /etc/xen/scripts/block-"$t" "$command" $node It appears as though XEN_SCRIPT_DIR has not been properly set....

Processing commands for control at bugs.debian.org: > severity 588406 important Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set Severity set to 'important' from 'normal' > tags 588406 patch Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set Added tag(s) patch. > retitle 588406 Xen unusable with DRBD, missi...

.../examples/Makefile Thu Jun 30 18:41:11 2005 +++ b/tools/examples/Makefile Thu Jun 30 18:59:08 2005 @@ -13,8 +13,6 @@ XEN_CONFIGS += xmexample1 XEN_CONFIGS += xmexample2 XEN_CONFIGS += xmexample.vmx -XEN_CONFIGS += mem-map.sxp -XEN_CONFIGS += bochsrc # Xen script dir and scripts to go there. XEN_SCRIPT_DIR = /etc/xen/scripts @@ -23,10 +21,13 @@ XEN_SCRIPTS += block-file XEN_SCRIPTS += block-enbd +XEN_BOOT_DIR = /usr/lib/xen/boot +XEN_BOOT = mem-map.sxp + all: build: -install: all install-initd install-configs install-scripts +install: all install-initd install-configs install-scripts install...

...d the latest openSuSE development branch. http://lists.opensuse.org/opensuse-packaging/2011-11/msg00055.html Signed-off-by: Olaf Hering <olaf@aepfle.de> diff -r 0b1ac7b3ee4d config/StdGNU.mk --- a/config/StdGNU.mk +++ b/config/StdGNU.mk @@ -67,7 +67,7 @@ XEN_CONFIG_DIR = $(CONFIG_DIR)/xen XEN_SCRIPT_DIR = $(XEN_CONFIG_DIR)/scripts SOCKET_LIBS = -CURSES_LIBS = -lncurses +CURSES_LIBS = $(shell if ! ncurses5-config --libs 2>/dev/null ; then ncurses-config --libs ; fi) PTHREAD_LIBS = -lpthread UTIL_LIBS = -lutil DLOPEN_LIBS = -ldl

...after being first reported, despite the fact that it includes the fix?. I can also confirm that the workaround proposed here works, although I am not sure that it's the best possible solution, maybe it can be set in some confoguration file, bit if so, I have benn unable to find it. AFAICT, XEN_SCRIPT_DIR is a compile-time option, and can't be configured. A more robust solution, which survives relocation of /etc/xen/scripts, would be to change the same lines to this instead, since `dir' gets set to the `block' script's directory as the first order of business in it. [ -x $dir/blo...

Hi I wrote a vif script to support openvswitch. I use it on some of my machines, so it works for non-qemu domains. Ian asked me to send it here, maybe someone wants to take a look. Bastian #!/bin/bash #============================================================================ # ${XEN_SCRIPT_DIR}/vif-openvswitch # # Script for configuring a vif in openvswitch mode. # The hotplugging system will call this script if it is specified either in # the device configuration given to Xend, or the default Xend configuration # in ${XEN_CONFIG_DIR}/xend-config.sxp. If the script is specified in # nei...

.../xen-/bin" LIBDIR="/usr/lib" SHAREDIR="/usr/share" -PRIVATE_BINDIR="/usr/lib/xen/bin" -XENFIRMWAREDIR="/usr/lib/xen/boot" +PRIVATE_BINDIR="/usr/lib/xen-/bin" +XENFIRMWAREDIR="/usr/lib/xen-/boot" XEN_CONFIG_DIR="/etc/xen" XEN_SCRIPT_DIR="/etc/xen/scripts" XEN_LOCK_DIR="/var/lock" -XEN_RUN_DIR="/var/run/xen" -XEN_PAGING_DIR="/var/lib/xen/xenpaging" The dpkg-new version is missing the version number in the xen path. -- System Information: Debian Release: 7.0 APT prefers testing APT poli...

...*) echo "Unknown command: $command" >&2 echo ''Valid commands are: start, stop, status'' >&2 exit 1 esac /etc/xen/scripts/vif-openvswitch: #!/bin/bash #============================================================================ # ${XEN_SCRIPT_DIR}/vif-openvswitch # # Script for configuring a vif using Open vSwitch. # # 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:...

Hans van Kranenburg writes ("Re: [PATCH 08/13] xen init script: rewrite xenstored start logic"): > So the question we should answer first is: What do we allow the user to > set as value? /bin/bash? And how should the init script deal with that? If they specify an absolute path, it should be used. Eg, /home/alice/Xen/xen/tools/xenstore/xenstore If the user specifies /bin/bash

...iff --git a/tools/hotplug/Linux/vif-openvswitch b/tools/hotplug/Linux/vif-openvswitch new file mode 100644 index 0000000..53c2f50 --- /dev/null +++ b/tools/hotplug/Linux/vif-openvswitch @@ -0,0 +1,99 @@ +#!/bin/bash +#============================================================================ +# ${XEN_SCRIPT_DIR}/vif-openvswitch +# +# Script for configuring a vif in openvswitch mode. +# The hotplugging system will call this script if it is specified either in +# the device configuration given to Xend, or the default Xend configuration +# in ${XEN_CONFIG_DIR}/xend-config.sxp. If the script is specified in...

...quot;$dev" "$type_if" add_to_openvswitch $dev ;; -- Aleksi Suhonen () ascii ribbon campaign /\ support plain text e-mail -------------- next part -------------- #!/bin/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: # b...

Hi List, many People seem to be interested in the Graphic-Card Passthrough Feature (for more or less obvious reasons). Official Support is still under development, and i hope not to interfere with it in any (bad) way ... But i remember my own painfull and timeconsuming research when i wanted this feature to work, so i thought perhaps this spares some time for the unpatient users like me :)

...="/usr/local/bin" LIBEXEC="/usr/local/lib/xen-/bin" LIBDIR="/usr/local/lib/x86_64-linux-gnu" SHAREDIR="/usr/local/share" PRIVATE_BINDIR="/usr/local/lib/xen-/bin" XENFIRMWAREDIR="/usr/local/lib/xen-/boot" XEN_CONFIG_DIR="/etc/xen" XEN_SCRIPT_DIR="/etc/xen/scripts" XEN_LOCK_DIR="/var/lock" XEN_RUN_DIR="/var/run/xen" XEN_PAGING_DIR="/var/lib/xen/xenpaging" /etc/xen/scripts/qemu-ifup changed: echo 'config qemu network with xen bridge for ' $* bridge=$2 if [ ! -e "/sys/class/net/$bridge&quo...

...\ > mv ioemu-remote.tmp ioemu-remote; \ > fi; \ > rm -f ioemu-dir; \ > ln -sf ioemu-remote ioemu-dir; \ > fi > + test -d /?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/../qemu > + mkdir -p ioemu-dir > set -e; \ > export PREFIX="/usr"; export XEN_SCRIPT_DIR="/etc/xen/scripts"; export XEN_ROOT="/?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/.."; \ > cd ioemu-dir; \ > /?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/../qemu/xen-setup > Install prefix /usr > BIOS directory /usr/share/qemu > binary dir...

....tmp; echo "PRIVATE_BINDIR=\"/usr/lib64/xen/bin\"" >> _libxl_paths.h.tmp.tmp; echo "XENFIRMWAREDIR=\"/usr/lib/xen/boot\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_CONFIG_DIR=\"/etc/xen\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_SCRIPT_DIR=\"/etc/xen/scripts\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_LOCK_DIR=\"/var/lock\"" >> _libxl_paths.h.tmp.tmp; if ! cmp _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; then mv -f _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; fi cmp: _libxl_paths.h.tmp: No such...

....tmp; echo "PRIVATE_BINDIR=\"/usr/lib64/xen/bin\"" >> _libxl_paths.h.tmp.tmp; echo "XENFIRMWAREDIR=\"/usr/lib/xen/boot\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_CONFIG_DIR=\"/etc/xen\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_SCRIPT_DIR=\"/etc/xen/scripts\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_LOCK_DIR=\"/var/lock\"" >> _libxl_paths.h.tmp.tmp; if ! cmp _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; then mv -f _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; fi sed -e "s/\([^=]*\)=\(.*\)/#...

...]; do xen_root_rhs="${xen_root_rhs#../}"; xen_root_rhs="${xen_root_rhs#/}"; xen_root_rhs="${xen_root_rhs#/}"; xen_root_lhs="${xen_root_lhs%/*}"; done; XEN_ROOT="$xen_root_lhs/$xen_root_rhs" ;; esac; export XEN_ROOT; \ PREFIX="/usr"; XEN_SCRIPT_DIR="/etc/xen/scripts"; export PREFIX; export XEN_SCRIPT_DIR; \ cd ioemu-dir; \ ./xen-setup Install prefix /usr BIOS directory /usr/share/qemu binary directory /usr/bin Manual directory /usr/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path /usr/src/xen-4.0.1/tools...

There are basically three issues we''re waiting to sort out (see below for more info): * XSA-55 * cpu hotplug in qemu-upsream * The MMIO hole issue Unfortuantely, there is considerable uncertainty about how long it will take for each of those to complete. We''re hoping to be able to release maybe on the 19th, This information will be mirrored on the Xen 4.3 Roadmap wiki page:

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now