similar to: [PATCH] qemu-xen: Fix open_disk for blktap disks

With my qcow2 patch to blktap I contributed a bit to the mess, so here an attempt to clean up and remove at least some of the code duplication in the functions dealing with aio operations. This patch is mostly just moving code. Apart from renaming to get common names and such things, only very few changes are needed as big parts of the code were completely identical and obviously created by

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

Hello, I wonder what the "open error -1" / "release open_disk error" messages in sanlock.log actually mean. I saw these messages in the log on a KVM host that rebooted, and after running "/usr/sbin/virt-sanlock-cleanup" on that host. The resources where disks from 2 guests running on another KVM host. So in fact the disks are still in use, bot got cleaned up by

On Tue, Apr 10, 2018 at 4:48 PM Kevin Wolf <kwolf@redhat.com> wrote: > Am 10.04.2018 um 15:03 hat Nir Soffer geschrieben: > > On Tue, Apr 10, 2018 at 1:44 PM Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > We now have true zeroing support in oVirt imageio, thanks for that. > > > > > > However a problem is that ‘qemu-img

Hi, Currently, we mount all blktap disks for pygrub so that it can boot from e.g. QCOW images. However, since pygrub will handle a raw image just fine without mounting through blktap, we shouldn''t bother in that case. Also, it looks like XendDomainInfo.create_vbd() takes the full disk uname rather than the image path. Signed-off-by: Mark McLoughlin <markmc@redhat.com> Cheers,

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

Am 14.05.2012 12:30, schrieb Jan Beulich: > While for the "normal" case (called from blk_send_response_all()) > decrementing requests_finished is correct, doing so in the parse error > case is wrong; requests_inflight needs to be decremented instead. > > Change in v2: Adjust coding style. > > Signed-off-by: Jan Beulich <jbeulich@suse.com> I think it would be

пн, 10 лют. 2020 о 15:48 Kevin Wolf <kwolf@redhat.com> пише: > > Am 10.02.2020 um 12:43 hat Richard W.M. Jones geschrieben: > > On Sat, Feb 08, 2020 at 01:25:28AM +0200, Mykola Ivanets wrote: > > > From: Nikolay Ivanets <stenavin@gmail.com> > > > > > > I faced with situation where libguestfs cannot recognize partitions on a > > > disk

The following two fixes by Jürgen Keil have been in qemu for a year now. They are still missing in ioemu. [Qemu-devel] PATCH: qcow2 image corruption http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00773.html [Qemu-devel] [PATCH] qcow2: release refcount table clusters of the old table, after growing the refcount table http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00043.html

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- hw/xen_disk.c | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git

Package: blktap-dkms Severity: grave Justification: renders package unusable Hi, blktap-dkms FTBFS against linux 3.10-1 from unstable: Cheers, Moritz CC [M] /var/lib/dkms/blktap/2.0.91/build/control.o In file included from /var/lib/dkms/blktap/2.0.91/build/control.c:30:0: /var/lib/dkms/blktap/2.0.91/build/blktap.h:75:41: warning: variably modified ?pending? at file scope [enabled by

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 17 Dec 2015 10:38:51 +0200 Source: blktap-dkms Binary: blktap-dkms Architecture: source Version: 2.0.93-0.5 Distribution: unstable Urgency: high Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Chrysostomos Nanakos <cnanakos at debian.org> Description: blktap-dkms - Xen

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Fri, 22 Mar 2013 19:02:45 +0800 Source: blktap-dkms Binary: blktap-dkms Architecture: source amd64 Version: 2.0.91-3 Distribution: experimental Urgency: low Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Thomas Goirand <zigo at debian.org> Description: blktap-dkms - Xen API

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 27 Apr 2014 12:10:36 +0200 Source: blktap-dkms Binary: blktap-dkms Architecture: source amd64 Version: 2.0.93-0.2 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Evgeni Golov <evgeni at debian.org> Description: blktap-dkms - Xen

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 23 May 2014 11:46:01 +0100 Source: blktap-dkms Binary: blktap-dkms Architecture: source amd64 Version: 2.0.93-0.3 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Bob Ball <bob.ball at citrix.com> Description: blktap-dkms - Xen

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 25 Oct 2015 14:54:28 +0200 Source: blktap-dkms Binary: blktap-dkms Architecture: source Version: 2.0.93-0.4 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Chrysostomos Nanakos <cnanakos at debian.org> Description: blktap-dkms -

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 05 Mar 2016 21:44:41 +0200 Source: blktap-dkms Binary: blktap-dkms Architecture: source Version: 2.0.93-0.6 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Chrysostomos Nanakos <cnanakos at debian.org> Description: blktap-dkms -

On 11/14/2011 07:43 AM, Jon Ludlam wrote: > On 12 Nov 2011, at 09:17, Thomas Goirand wrote: >> On 11/12/2011 12:16 AM, Jonathan Ludlam wrote: >>> Secondly, there are a few more things that need to be done to your >>> blktap >>> packaging prior to uploading: >>> >>> * The xen-org/blktap.git repository builds and works for amd64 >> >>

Hi. These patches add the output function for blktap statistics into xentop. Currently, xentop outputs only blkback statistics, and not blktap statistics. By these patches, xentop is made cover both blkback and blktap. In xen, back-end driver has two types; blkback and blktap. Blkback driver is old back-end driver. Blktap driver is new back-end driver and is recommended currently. Usage of both

This commit delays the point at which bdrv_new (and hence blk_open on the underlying device) is called from blk_init to blk_connect. This ensures that in an inbound live migrate, the block device is not opened until it has been closed at the other end. This is in preparation for supporting devices with open/close consistency without using O_DIRECT. This commit does NOT itself change O_DIRECT