similar to: Bug 709 blktapctrl doesn''t daemonize

What follows below is an outline of what we''re changing in Xen startup for Fedora 8. I know historically when getting into initscripts you tend to hit distro specific issues. So I''m posting this to see if there''s any interest from others in having these changes integrated upstream. I''d like to thing that with a few minor tweaks this is general enough to be

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

Hi! When I try to compile xen-unstable on Sarge, I get this error and I don''t know how to solve it: make[3]: Entering directory `/root/xen-unstable/tools/blktap/drivers'' gcc -O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall -Wstrict-prototypes -D__XEN_TOOLS__ -fPIC -Wall -Werror -Wno-unused -g3 -fno-strict-aliasing -I ../../../tools/libxc -I ../../libaio/src -I..

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl isn't started by default. If blktapctrl isn't started then none of the tap: disks (eg tap:aio) work. This functionality has been removed in tools-misc-xend-startup.diff @@ -120,24 +86,14 @@ if not sys.argv[1:]: print 'usage: %s {start|stop|reload|restart}' % sys.argv[0] elif

[PATCH 3/4] (Refactored) Add error checking in blktapctrl blktap-fixes.patch Add some additional error checking to blktapctrl during mkfifo Signed-off-by: Boris Ostrovsky <bostrovsky@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I am running XEN 4.1 on Debian 6 and I cannot find blktapctrl process running. xend is started. I installed XEN from 4.1 source following instructions here: http://wiki.xensource.com/xenwiki/XenParavirtOps http://wiki.xensource.com/xenwiki/Xen4.0 Should there be a blktapctrl process running in this version? The problem I have encountered is that I can create a domain on a raw disk image but

I''m getting this message (subject line) in daemon.log every time I start or restart xend. I''m not sure if this is related to the fact that I cannot boot up my Windows domU from a VHD file. The Windows domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel). When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can no long boot the Windows domU from VHD. The

In dispatch_rw_block_io after a call to HYPERVISOR_grant_table_op, there is the following code which calls fast_flush_area and breaks out of the loop early if one of the handles returned from HYPERVISOR_grant_table_op is negative: for (i = 0; i < nseg; i++) { if (unlikely(map[i].handle < 0)) { DPRINTK("invalid buffer -- could not remap it\n"); fast_flush_area(pending_idx,

Here''s the latest USB code against the xen 3.0.0 release. Since the last posting this version updates the code to use the new 32 bit grant references and the latest GNTTABOP_map_grant_ref definition. I''ve also changed the definition of the virtual USB HCD to have a single port rather than seven ports with six unused. Domains importing multiple USB devices will get a HCD for

*After running intensively (i.e. running >10 guests and migrating them all into other machines etc.) , I wasn''t able to * *run xen tools as the following messages show. * ** ># xm list Error: (9, ''Bad file descriptor'') Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP

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 list! I''ve noticed this problem a couple of times now.. so I''m wondering if it''s a known bug? Symptoms: After "long" dom0 uptime (174 days when it happened now, was something similar on previous times too) cannot start new pv domUs anymore.. pygrub runs and boots the kernel, but kernel newer gets to actually running initrd and the console output

Package: xen-utils-common Version: 4.4.0-1 Severity: important Tags: patch Under some circumstances the xl toolstack needs to create a loopback mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending on the nature of the guest disk (e.g. qcow2 or raw file image based) this can require a qemu instance in dom0. The upstream xencommons starts such a qemu on boot. The following patch

Hi all, I have some serious problems making Xen run. I have spent a couple of days looking in Google and trying a lot of different things, but none of them has worked. I hope you can help me... First of all: xen was running smoothly on my machine, but suddenly (I think I haven''t changed any configuration) it doesn''t work anymore. I am using a Debian 4.0 with Xen 3. When

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

Came across this issue in 3.0.2; looks to also be present in the latest unstable sources: # ls -l /var/run/xenconsoled.pid -rwS--x--T 1 root root 5 Aug 31 00:29 /var/run/xenconsoled.pid setuid, group-execute, and sticky...? This happens because daemonize() in tools/console/daemon/utils.c isn''t specifying a "mode" parameter when creating the file: fd = open(pidfile, O_RDWR

/usr/lib/xen/bin/qemu-system-i386 doesn''t exist on ARM. We need to check if the file exists/is executable and starts it. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/hotplug/Linux/init.d/xencommons | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tools/hotplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons index

Package: xen-utils-3.0 Version: 3.0.2+hg9697-2 Severity: wishlist Hi, it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). Thanks Andras -- Andras Korn <korn at chardonnay.math.bme.hu> <http://chardonnay.math.bme.hu/~korn/> QOTD: Paranoid: someone

Package: xen-utils-common Version: 3.4.2-3 Severity: normal If one daemon is running but the others are not then the stop script will fail. It should use the pid file for each daemon and try to stop them independently. Note that the fact that Xen shouldn't get into this state is not relevant, daemons do periodically fail, relevant system control scripts should be able to stop them even

a clean new FC6 system downloading xen src tar ball I get make[3]: Entering directory `/opt/xen-3.0.4_1-src/tools/blktap/drivers'' gcc -O2 -fomit-frame-pointer -m64 -DNDEBUG -std=gnu99 -Wall -Wstrict- prototypes -Wno-unused-value -Wdeclaration-after-statement - D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror - Wno-unused -fno-strict-aliasing -I