similar to: Help/problems with blktap on xen-unstable

hi, i''m trying move from file: based disk to tap:aio but things don''t work i have centos4 dom0 with centos4 domU xen 3.0.4-testing changeset: 13138:d401cb96d8a0 self compiled [root@xen linux-2.6.16.38-xen]# grep XEN_BLKDEV_TAP .config CONFIG_XEN_BLKDEV_TAP=m config disk = [ ''file:/var/lib/xen/test.img,hda1,w'',

Hello, i am experiencing something weird on my Xen Dom0 Since a few days, i can no more install or reboot any vm using tap:aio driver My vms complains about no mounted disks OS: On openSUSE 11.2 (x86_64) with xen-tools-3.4.1_19718_04-2.1.x86_64 kernel-xen-base-2.6.31.8-0.1.1.x86_64 xen-libs-3.4.1_19718_04-2.1.x86_64 kernel-xen-2.6.31.8-0.1.1.x86_64

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, while trying to get blktap based domus running with current Debian Xen 3.1.2 I came across a missing link: The tapdisk binary should be added to GLOBAL_SCRIPTS in xen-common/scripts/Makefile. Otherwise blktap based domus don't find their disks. blktapctrl forks tapdisk processes. Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG

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, Attached patch moves OS dependent code from blktapctrl into an OS dependent file. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden:

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

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

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 =

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

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

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:

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

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

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

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

Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in

Another problem is that the blktapctrl daemon itself does not even start if the "xenblktap" kernel module is not loaded. (blktapctrl is started automatically by xend.) So to use tap:aio with Xen from Debian lenny you need to - create a symlink named "tapdisk" pointing to /usr/lib/xen-3.2-1/bin/tapdisk somewhere in root's $PATH and - load the "xenblktap"

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for