similar to: Bug#582363: xen-utils-3.4: blktapctrl not started by default

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)]

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

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

Processing commands for control at bugs.debian.org: > forcemerge 582363 582364 421825 442380 517007 Bug #582363 [src:xen] xen-utils-3.4: blktapctrl not started by default Bug #582363 [src:xen] xen-utils-3.4: blktapctrl not started by default The source xen and version 3.0.3-0-2 do not appear to match any binary packages The source xen and version 3.1.0-2 do not appear to match any binary

Andrew, I think bug 709 is caused by blktapctrl not daemonizing itself correctly and holding open a file descriptor that the xm-test python code is reading from. I''m not really very familiar with blktapctrl. If you''d like to pick up the bug or outline how you''d like it fixed---for example by copying the daemonize implementation from xenconsoled---that would be

[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

Processing commands for control at bugs.debian.org: > close 421825 4.4.0-1 Bug #421825 [src:xen] xen-utils-3.0.3-1: blktap is missing Bug #442380 [src:xen] xen-utils-3.1-1: reenabled blktap support unusable Bug #517007 [src:xen] xen-utils-3.2-1: tap:aio on disk image files is not usable Bug #582363 [src:xen] xen-utils-3.4: blktapctrl not started by default Bug #582364 [src:xen] xen-utils-3.4:

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

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

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Please can you add python-xml as a dependancy for xen-utils-3.2-1 on lenny and above. Without python-xml a dependancy for "xm new" isn't satified. Thanks, Matthew Millar -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux

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 =

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important /usr/lib/xen-3.2-1/bin/blktapctrl searches for tapdisk executable in /usr/bin while is in /usr/lib/xen-3.2-1/bin this makes tap:aio unusable I've linked to /usr/bin and everything went fine perhaps the idea is to patch sources to pick executable from the right directory Regards -- System Information: Debian Release: 5.0

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

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

Hi I''ve been trying to play with the new blktap support in xen-unstable. First, an observation - blktapctrl is pinned at 100% CPU: ----------------------------------------------------------------------------------------------------------------- top - 17:29:48 up 4 days, 2:02, 3 users, load average: 0.90, 1.01, 1.00 Tasks: 83 total, 3 running, 80 sleeping, 0 stopped, 0 zombie