similar to: A little confusion between "tapdisk" and "tapdisk-ioemu"

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

stubdom: do not build tapdisk as it it not supposed to build and we don''t need it Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 4024164e7572 stubdom/Makefile --- a/stubdom/Makefile Tue Jul 08 16:11:49 2008 +0100 +++ b/stubdom/Makefile Tue Jul 08 17:12:38 2008 +0100 @@ -190,7 +190,7 @@ [ -f ioemu/config-host.mak ] || \ ( cd ioemu ; \

Although tapdisk has been instead of tapdisk-ioemu, but it still used on some old xen-3.2. So fix a performance problem here. -- Kernel aio will retry when encounter a block doesn''t allocated, then do async io, but O_DIRECT flag was there, so io_wait on sync data. And clean a little code style. Signed-off-by: Wei Kong <weikong.cn@gmail.com>

Hi all, Has anyone used gdb to debug tapdisk problems? I''ve implemented a custom tapdisk interface and I''m trying to debug a few kernel paging crashes. -Jack

When a domain wants to use a tap:ioemu disk but has no device model, start a tapdisk-ioemu instance as provider. Also, move the creation and removal of communication pipes to xend so that qemu-dm doesn''t need the unwanted SIGHUP handler anymore. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list

On Thu, Mar 12, 2015 at 6:11 PM, Nathan March <nathan at gt.net> wrote: > 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. Interesting -- actually you get the same effect just starting and shutting down a guest. It

Hi, For this issue I had initial discussion thread before, more detail, please see : http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01140.html. I write a new patch for this issue, which modified qemu code. So Ian, could you take a look this patch,too. thanks, James (Song Wei) Signed-off-by: James ( Song Wei ) <jsong@novell.com> diff -r efa1b905d893

# 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

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 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' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder =

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

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

I would write in tab-text file a table like this one: TAB colname1 TAB colname2 TAB TAB... colnameN rowname1 # # # rowname2 # # # rownameM # # # then I wrote something like: mymatrix <- matrix(nrow=M,ncol=N,byrow=T) rownames(mymatrix) <- chvector1 colnames(mymatrix) <- chvector2

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

Hello, I have a small problem with the blktap, that when I use "tap:aio" protocol to access my disk, the domU stop booting with following message: [ 0.185031] PCI: Fatal: No config space access function found [ 0.189998] Unable to read sysrq code in control/sysrq [ 0.350220] i8042: No controller found [ 0.452153]

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>