similar to: Xen blktap driver for Ceph RBD : Anybody wants to test ? :p

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

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>

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

Hi, A bit of explanation of what I''m trying to achieve : We have a bunch of homogeneous nodes that have CPU + RAM + Storage and we want to use that as some generic cluster. The idea is to have Xen on all of these and run Ceph OSD in a domU on each to "export" the local storage space to the entire cluster. And then use RBD to store / access VM images from any of the machines.

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

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

On Tue, May 5, 2015 at 2:07 PM, Johnny Hughes <johnny at centos.org> wrote: > WRT a new kernel .. the 3.18.x kernel has been selected to be maintained > as an LTS until Jan 2017. I think we should start work on rebuilding > this kernel and using it in the x4c projects. > > https://lwn.net/Articles/636289/ > > Thoughts? > > I will grab this kernel and try to roll

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

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

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

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

I''m using the CentOS 6 bundle of xen from http://dev.centos.org/centos/6/xen-c6/ and ran into an issue when creating domains with multiple VHD tap disks. Comparing unstable to the 4.2.1 code I''m using, it seems this issue still applies. I''m using a configuration line that looks something like disk = [

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

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

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:

Hi, milos/list, now I''m working on some code related to page sharing. Are there any document/wiki that show how to setup the page sharing environment, so that I can test my code? Checking the code, I noticed the only tapdisk/blktap will use this page sharing mechanism. I''m not sure HVM guest without PV driver can use blktap, so does page sharing support HVM guest? Sorry that

When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In

--------------------------------------------------------------------------- The following patch when applied on top of: libxl: attempt to cleanup tapdisk processes on disk backend destroy. Establishes correct cleanup behavior for blktap devices. This patch implements the release of the backend device before calling for the destruction of the userspace component of the blktap device. Without