summaryrefslogtreecommitdiffstats
path: root/block-migration.c
diff options
context:
space:
mode:
authorRyan Harper <ryanh@us.ibm.com>2010-11-12 11:07:13 -0600
committerKevin Wolf <kwolf@redhat.com>2010-11-24 17:30:19 +0100
commit9063f81415f3518ef8206e74085c2a92c96890a0 (patch)
treeac5eb775dea385bff21fce6f063eb0348e413217 /block-migration.c
parent6fa2c95f279dda62aa7e3292cc424ff3fab6a602 (diff)
downloadhqemu-9063f81415f3518ef8206e74085c2a92c96890a0.zip
hqemu-9063f81415f3518ef8206e74085c2a92c96890a0.tar.gz
Implement drive_del to decouple block removal from device removal
Currently device hotplug removal code is tied to device removal via ACPI. All pci devices that are removable via device_del() require the guest to respond to the request. In some cases the guest may not respond leaving the device still accessible to the guest. The management layer doesn't currently have a reliable way to revoke access to host resource in the presence of an uncooperative guest. This patch implements a new monitor command, drive_del, which provides an explicit command to revoke access to a host block device. drive_del first quiesces the block device (qemu_aio_flush; bdrv_flush() and bdrv_close()). This prevents further IO from being submitted against the host device. Finally, drive_del cleans up pointers between the drive object (host resource) and the device object (guest resource). Signed-off-by: Ryan Harper <ryanh@us.ibm.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block-migration.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud