similar to: Bug#588406: xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set

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 in the

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

On Wed, 22 Oct 2008, Russell Coker wrote: > It seems reasonable to create a file /etc/modprobe.d/xen that contains > the following line to alleviate this: > options loop max_loop=32 Since kernel 2.6.22, loop devices are allocated dynamically, so that you can `mknod /dev/loopN b 7 N` for any N and start using it immediately. The max_loop option causes more loop devices to be

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

I can confirm this bug still is in squeeze... a full year 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,

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 +++

Based on Waldi''s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the

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;

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341941699 -3600 # Node ID efb7fee3573b68e895de0341dd67df83cb68acc6 # Parent ca5c306052791edf6d96da3f80aecd750b86a5e4 hotplug: vif: fail if a duplicate vifname is used. This is based on a patch from Hans van Kranenburg in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658305. Quoting that bug report: When

Hi All I am using xen 3.3.0 version and I want to start network virtual interface on Dom U by using the following command # xend start *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is

Hello everyone, Recently I have been testing my customized Xen 4.2 networking setup. It works pretty good and I would like to share it with anyone who is interested. The relevant files can be found here: https://github.com/slacks42/xenscripts Benefit: configure the Xen related networking devices with one understandable bash script. Please note that this is all still work in progress. For

Dear all, I followed the steps described in the wiki in order to get an Arnadle board running Xen, but I''m having trouble in starting a domU. Let me describe you the steps I followed. Sorry for such a long mail, but I think that a verbose description is necessary so you can point me what I''m doing wrong. I couldn''t boot properly over the network. This is why I

Confirmed in squeeze. Almost two years old. Thanks for the fix, works well. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4371 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120321/ea6d5566/attachment.bin>

--- docs/nbdkit-captive.pod | 4 ++-- docs/nbdkit-plugin.pod | 2 +- docs/nbdkit-service.pod | 2 +- docs/nbdkit-tls.pod | 2 +- filters/cow/nbdkit-cow-filter.pod | 4 ++-- filters/delay/nbdkit-delay-filter.pod | 2 +- filters/error/nbdkit-error-filter.pod | 6 +++---

--- docs/nbdkit-captive.pod | 4 ++-- docs/nbdkit-plugin.pod | 2 +- docs/nbdkit-service.pod | 2 +- docs/nbdkit-tls.pod | 2 +- filters/cow/nbdkit-cow-filter.pod | 4 ++-- filters/delay/nbdkit-delay-filter.pod | 2 +- filters/error/nbdkit-error-filter.pod | 6 +++---

In libguestfs we have a few tests that require root privileges and they are skipped by default (normally you should not build or test as root), but you can do this to run them: sudo make check-root In nbdkit I wanted to check that the file plugin works with block devices (this is not tested), and the only way I can sensibly think to do this is using a loopback device and root. This commit

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

Device model path cleanup. Remove bochsrc which is no longer needed. Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- a/tools/examples/xmexample.vmx Thu Jun 30 18:41:11 2005 +++ b/tools/examples/xmexample.vmx Thu Jun 30 18:59:08 2005 @@ -89,10 +89,10 @@ # New stuff -device_model = ''/usr/bin/qemu-dm'' +device_model = ''/usr/lib/xen/bin/qemu-dm''