summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2014-08-18 16:07:13 +0100
committerStefan Hajnoczi <stefanha@redhat.com>2014-08-29 16:01:48 +0100
commit3255d1c21f364774390061fbc3b8e25c027cc862 (patch)
treea03b99470af3b48cd5c249b7326211f86ce9eed9
parent8ad4202bf61bc1d124ff26016cfe17cb261cc392 (diff)
downloadhqemu-3255d1c21f364774390061fbc3b8e25c027cc862.zip
hqemu-3255d1c21f364774390061fbc3b8e25c027cc862.tar.gz
virtio-blk: allow drive_del with dataplane
Now that drive_del acquires the AioContext we can safely allow deleting the drive. As with non-dataplane mode, all I/Os submitted by the guest after drive_del will return EIO. This patch makes hot unplug work with virtio-blk dataplane. Previously drive_del reported an error because the device was busy. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
-rw-r--r--hw/block/dataplane/virtio-blk.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/hw/block/dataplane/virtio-blk.c b/hw/block/dataplane/virtio-blk.c
index c07adc6..b55188c 100644
--- a/hw/block/dataplane/virtio-blk.c
+++ b/hw/block/dataplane/virtio-blk.c
@@ -194,6 +194,7 @@ void virtio_blk_data_plane_create(VirtIODevice *vdev, VirtIOBlkConf *blk,
error_setg(&s->blocker, "block device is in use by data plane");
bdrv_op_block_all(blk->conf.bs, s->blocker);
bdrv_op_unblock(blk->conf.bs, BLOCK_OP_TYPE_RESIZE, s->blocker);
+ bdrv_op_unblock(blk->conf.bs, BLOCK_OP_TYPE_DRIVE_DEL, s->blocker);
*dataplane = s;
}
OpenPOWER on IntegriCloud