similar to: Bug#442380: xen-utils-3.1-1: reenabled blktap support unusable

Displaying 20 results from an estimated 6000 matches similar to: "Bug#442380: xen-utils-3.1-1: reenabled blktap support unusable"

2009 Aug 01
0
Bug#442380: xen-utils-3.1-1: reenabled blktap support unusable
Any movement on this? It's a pain to have to remember to re-add the symlink when setting up a new system or upgrading xen-utils.
2013 Feb 23
2
Bug#701248: blktap: ftbfs with GCC-4.8
Package: src:blktap Version: 2.0.90-1 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'
2015 Feb 12
1
Bug#777801: blktap: ftbfs with GCC-5
Package: src:blktap Version: 2.0.90-3 Severity: normal Tags: sid stretch User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built
2015 Mar 12
2
Tapdisk processes being left behind when hvm domu's migrate/shutdown
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 =
2007 Nov 28
1
RFC: add tapdisk link in xen-common for blktap
-----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
2014 Sep 04
1
Bug#760504: blktap-utils: Failing to call io_setup with EINVAL
Package: blktap-utils Version: 2.0.90-2 Severity: important Tapdisk fails to start and exit's silently after failing to detect current kernel version. This happens only on newer kernel versions missing sublevel field. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP
2012 Aug 10
1
want to write a difference copy program to sync two VHDs in blktap
Hello List, I''m using blktap on XCP 1.1 and developing a difference copy program for easy backup and remote archival. The idea is to read the BAT of VHD1 and sync it to BAT of VHD2 with BITMAP and the data blocks. Other way would be by adding a sha1 signature in each data block and comparing it with remote VHD. I tried to get some info from below programs but could not get required
2012 May 23
0
A little confusion between "tapdisk" and "tapdisk-ioemu"
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,
2013 Mar 02
7
libxl device_disk_add orphans blktap devices on transaction error
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 = [
2013 May 15
0
blktap stops every 10 seconds and the performance suffers
Hi all, I am not sure if this is the right list. I implemented a network store based on blktap, a IO consumes100 ms, however tapdisk stops every 10 seconds, as a result previous io''s completion will be sent to kernel until 10 seconds later. This makes the performance suffer. Am I using blktap wrong ? Thanks, Yongqiang -- Best Wishes Yongqiang Yang
2015 Aug 21
0
Processed: forcibly merging 582363 582364 421825 442380 517007
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
2008 Mar 10
12
[RFC][PATCH] Use ioemu block drivers through blktap
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
2006 Dec 01
1
[PATCH] Ensure blktap reports I/O errors back to guest
There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O
2008 Apr 22
0
[PATCH] blktap: Automatically start tapdisk-ioemu on demand
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
2010 Jun 22
2
domU can not start in Xen 4.0.1-rc3-pre using 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:
2010 Jun 22
2
domU can not start in Xen 4.0.1-rc3-pre using 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:
2011 Aug 04
3
[Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd
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
2010 Sep 15
3
How to setup the page sharing environment
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
2012 Nov 07
4
[PATCH 2/2] 4.1.2 blktap2 cleanup fixes.
--------------------------------------------------------------------------- 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
2012 Apr 02
23
[PATCH 00 of 18] [v2] tools: fix bugs and build errors triggered by -O2 -Wall -Werror
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