search for: tapdisk

...Severity: important Tags: sid jessie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. tapdisk-logfile.c:166:23: error: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to dereference it? [-Werror=sizeof-pointer-memaccess] The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/blktap_2.0.90-1_unstab...

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 find that when i specify tap:aio the executable functioning is actually /usr/sbin/tapdisk-ioemu i don'...

...are some errors about "warn_unused_result". Is it the error in code or the error in the compiling environment? Thank you so much. gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .tapdisk-queue.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror -g -Wno-unused -fno-strict-aliasing -I../include -I../drivers -I/root/Xen/xen-4.2-unstable/tools/blktap2/drivers/../../../tools/libxc -I/root/Xen/xen-4.2-unstable/tools/blktap2/drivers/../../../tools/include -D...

Hello, I have a problem with storage over NFS (NFS server is running on Open Solaris 10 with NFS version client/server/min/max=3) cat /var/log/messages from cnode1 (XCP 1.0 beta) during instalation new VM: an 18 22:57:37 cnode1 tapdisk[9661]: ERROR: errno -88 at vhd_complete: /var/run/sr-mount/2d5ed3ca-7e4d-bceb-f959-542d3bade15e/3d69f4a6-743d-486e-8a65-1734e6ef0b67.vhd: op: 2, lsec: 80003048, secs: 24, nbytes: 12288, blk: 19531, blk_offset: 4294967295 Jan 18 22:57:37 cnode1 tapdisk[9661]: ERROR: errno -88 at vhd_complete: /v...

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 attched (and /sys/class/blktap2/devices stays empty). Changing it to tap2:tapdisk:aio works (sort of). I recall some discussion ab...

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] v...

...e27-4830-9bf0-5b66ba290547.vhd,xvdb,w" ] What I noticed happening in the code is that in device_disk_add the call to libxl__xs_transaction_commit returns rc=1 so the "for (;;)" loop just tries again. The problem though is that the blktap device was already created and assigned to a tapdisk process. So it will just leave that process hanging out there and allocated a new device on the second pass through the for loop. The second run through succeeds. What I typically see is that if I have more than 1 disk on the domain, the first disk gets created fine and then each subsequent disk...

...: gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -I../include -D_FORTIFY_SOURCE=2 -Wall -Werror -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -MT block-lcache.lo -MD -MP -MF .deps/block-lcache.Tpo -c block-lcache.c -fPIC -DPIC -o block-lcache.o >/dev/null 2>&1 mv -f .deps/tapdisk-image.Tpo .deps/tapdisk-image.Plo mv -f .deps/block-aio.Tpo .deps/block-aio.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -I../include -D_FORTIFY_SOURCE=2 -Wall -Werror -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -MT tapdisk-vbd.lo -MD -MP -MF .deps/tapdisk-...

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: Waiting for devices to initialise: 295s...290s... Then after reboot, the domU can not mount the filesystem /dev/root and kernel...

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: Waiting for devices to initialise: 295s...290s... Then after reboot, the domU can not mount the filesystem /dev/root and kernel...

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

...ols/blktap/drivers/block-ram.c | 7 ------ tools/blktap/drivers/block-sync.c | 5 ---- tools/blktap/drivers/img2qcow.c | 7 +----- tools/blktap/drivers/qcow2raw.c | 6 ++--- tools/blktap/drivers/tapaio.c | 1 tools/blktap/drivers/tapdisk.c | 18 ++++++++-------- tools/blktap/lib/xenbus.c | 11 ++++----- tools/blktap/lib/xs_api.c | 32 ++++++++++++++--------------- tools/blktap2/control/tap-ctl-check.c | 1 tools/blktap2/control/tap-ctl-list.c | 3 -- tools/blktap...

Get blktap2 running on pvops. This mainly adds eventfd support to the userland code. Based on some prior cleanup to tapdisk-queue and the server object. We had most of that in XenServer for a while, so I kept it stacked. 1. Clean up IPC and AIO init in tapdisk-server. [I think tapdisk-ipc in blktap2 is basically obsolete. Pending a later patch to remove it?] 2. Split tapdisk-queue into variable raw I/O backen...

Hi, I''ve been working on getting a working blktap driver allowing to access ceph RBD block devices without relying on the RBD kernel driver and it finally got to a point where, it works and is testable. Some of the advantages are: - Easier to update to newer RBD version - Allows functionality only available in the userspace RBD library (write cache, layering, ...) - Less issue when

-----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 v1.4.7 (Darwin) iD8DBQFHTa6qoSFr3dtMR4IRAgeoAJ0WurcbMuE+VBxU3TLOBOk3jqk3cw...

This patch series introduces the shared ring used by the front-end to pass request descriptors to tapdisk, as well as responses from tapdisk to the front-end. Requests from this ring end up in tapdisk''s standard request queue. When the tapback daemon detects that the front-end tries to connect to the back-end, it spawns a tapdisk and tells it to connect to the shared ring. The shared ring is...

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1316609964 -3600 # Node ID b43fd821d1aebc8671e684bfc285cda7a6002ff1 # Parent 206afa070919e3fe0b13a03f870ca2da44ab604a libxl: attempt to cleanup tapdisk processes on disk backend destroy. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 206afa070919 -r b43fd821d1ae tools/blktap2/control/tap-ctl-list.c --- a/tools/blktap2/control/tap-ctl-list.c Wed Sep 21 13:59:24 2011 +0100 +++ b/tools/blktap2/control/tap-ctl-list.c Wed Sep 21...

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the front-end and the tapdisk is provided by a piece of code that lives inside the tapdisk and will be introduced by the next patch se...

...Windows domU from VHD. The VNC console for the Windows HVM has this message: Booting from Hard Disk ... Boot from Hard Disk failed; could not read the boot disk No bootable device. Powering off in 30 seconds. Here''s the disk setting in my Windows domU config file: disk = [''tap:tapdisk:vhd:/mnt/win2008sp2.vhd,xvda:sda1,w''] Here''s the other BLKTAPCTRL messages in daemon.log: BLKTAPCTRL[2444]: blktapctrl.c:790: blktapctrl: v1.0.0 BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [raw image (aio)] BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [raw image (sync...

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''] #device-model = ''/usr/lib/xen-4.0/bin/qemu-dm'' #vnc = 1 #boot = ''d'' #PV name = "webserver" memory = 2048 bootloader = "/usr/lib/xen-4.0/bin/pygrub"...