search for: blktap3

Hi, I''d like to use the blktap utils from https://github.com/xen-org/blktap because of the mirror feature, as the blktap utils comming with xen does not support this. Could anybody explain why there are two different blktap utils (one in git and one comming with xen source) and how to compile the one from git so that it works with libxl ? Any pointers greatly appreciated ;-) Thanks

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

...bit of work on building the 3.18 kernel a couple of weeks ago, but it looks like the blktap2.5 kernel code we were using before has totally bitrotted. I see three ways forward: 1. Try to do a "deep port" of the functionality, continuing to maintain it going forward. 2. Start using the blktap3 code, which requires no kernel driver. 3. Drop blktap support, and ask people to use qdisk for vhd. Re #1, I'm not really excited about the idea of trying to keep porting those patches forward (and finding and fixing bugs in the forward-port each time). Re #2, this would require getting the...

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

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>

...d upon boot.. I did have to change some of the code based on this Debain bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748953 I have no idea how well this works .. we could use some testing of that kernel here: http://people.centos.org/hughesjr/xen-kernel/ > > 2. Start using the blktap3 code, which requires no kernel driver. > > 3. Drop blktap support, and ask people to use qdisk for vhd. > > Re #1, I'm not really excited about the idea of trying to keep porting > those patches forward (and finding and fixing bugs in the forward-port > each time). This has...

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

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

...vDaemon:332) Xend Daemon started [2010-06-25 03:13:36 4401] INFO (SrvDaemon:336) Xend changeset: unavailable. ... ... /var/log/messages: ... ... Jun 25 03:10:41 r21b02004 tapdisk2[16340]: /guest/VM-420A07DA/disk10369/image.vhd: 4 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opening device blktap3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opened device 3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_mmap: blktap: mapping pid is 16340 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:...

...vDaemon:332) Xend Daemon started [2010-06-25 03:13:36 4401] INFO (SrvDaemon:336) Xend changeset: unavailable. ... ... /var/log/messages: ... ... Jun 25 03:10:41 r21b02004 tapdisk2[16340]: /guest/VM-420A07DA/disk10369/image.vhd: 4 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opening device blktap3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opened device 3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_mmap: blktap: mapping pid is 16340 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:...

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

...(currently 1024 for 32-bit guests, 4096 for 64-bit guests) * NUMA scheduler affinity owner: dario@citrix * NUMA Memory migration owner: dario@citrix * PVH mode, domU (w/ Linux) owner: mukesh@oracle * PVH mode, dom0 (w/ Linux) owner: mukesh@oracle * ARM server port owner: @citrix * blktap3 owner: @citrix * Default to QEMU upstream - qemu-based stubdom (Linux or BSD libc) owner: anthony@citrix qemu-upstream needs a more fully-featured libc than exists in minios. Either work on a minimalist linux-based stubdom with glibc, or port one of the BSD libcs to minios. -...