similar to: Bug#517007: "xenblktap" module

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

Hi everyone, as what I''ve learned form this link<http://wiki.xensource.com/xenwiki/blktap>, i know that when i specify tap:aio I’m actually using the blktap driver and finally using "tapdisk" to wirite to raw image file. but the truth is even when i delete /usr/sbin/tapdisk the domU can still boot on my machine with tap:aio protocol after a deeper look into the scene,

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

Hi all I was reading through Xen 3 user manual and saw this tap:aio should be used instead of loopback... Then I came to do that, but I can get it working with replacing `file'' URI''s with `tap:aio''. My OS: Debian Lenny 2.6.26-2-xen-amd64 DomU Xen configuration file: kernel = ''/boot/vmlinuz-2.6.26-2-xen-amd64'' ramdisk =

I have never been able to get tap:aio devices running. When I try it in a Linux PV domain, it says: XENBUS: Waiting for devices to initialise: 295s... And they don''t work in my GPLPV drivers, which is the problem I am trying to solve, but I''d like to see them work under Linux first. Is there anything extra I need to do? I have loaded the xenblktap module (forgot to do this

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

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

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

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

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 514918 src:xen 3.3-unstable+hg17961-1 Bug #514918 [xen-utils-unstable] xen-utils-unstable: xend starts with errors Warning: Unknown package 'xen-utils-unstable' Bug reassigned from package

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 all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

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

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

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

Hi, I''ve been testing Xen 4.0.1 with kernel 2.6.34.5 + http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2, and one of the things that I noticed immediately is there are two problems with tapdisk and this combination. First, the syntax "disk = [''tap:tapdisk:aio: ..." no longer works. When tested with HVM domU, it boots, but there was no disk