Acquire the AioContext during _realize()
v2 cover Acquire the AioContext during _realize()
This series acquires the AioContext in the _realize() functions of several devices before making use of their block backends. This fixes at least a couple of crashes (in virtio-blk and scsi). The other devices don't currently support iothreads so there's no crashes.
Berto
v2:
- Patch 1: include a test case [Kevin]
- Patch 2: include a test case and extend the locking to protect more function calls [Kevin]
v1: https://lists.gnu.org/archive/html/qemu-block/2019-01/msg00259.html
- Initial version
Output of backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch [down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/6:[0095] [FC] 'block: Acquire the AioContext in virtio_blk_device_realize()' 002/6:[0094] [FC] 'block: Acquire the AioContext in scsi_*_realize()' 003/6:[----] [--] 'block: Acquire the AioContext in floppy_drive_realize()' 004/6:[----] [--] 'block: Acquire the AioContext in nvme_realize()' 005/6:[----] [--] 'block: Acquire the AioContext in ide_dev_initfn()' 006/6:[----] [--] 'block: Acquire the AioContext in usb_msd_storage_realize()'
Alberto Garcia (6):
block: Acquire the AioContext in virtio_blk_device_realize()
block: Acquire the AioContext in scsi_*_realize()
block: Acquire the AioContext in floppy_drive_realize()
block: Acquire the AioContext in nvme_realize()
block: Acquire the AioContext in ide_dev_initfn()
block: Acquire the AioContext in usb_msd_storage_realize()
hw/block/fdc.c | 15 ++++-- hw/block/nvme.c | 13 +++-- hw/block/virtio-blk.c | 22 ++++++--- hw/ide/qdev.c | 17 +++++-- hw/scsi/scsi-disk.c | 23 +++++++-- hw/usb/dev-storage.c | 5 ++ tests/qemu-iotests/236 | 121 +++++++++++++++++++++++++++++++++++++++++++++ tests/qemu-iotests/236.out | 46 +++++++++++++++++ tests/qemu-iotests/group | 1 + 9 files changed, 241 insertions(+), 22 deletions(-) create mode 100755 tests/qemu-iotests/236 create mode 100644 tests/qemu-iotests/236.out
Signature · 1 line
2.11.0
PATCH v2 4/6 block: Acquire the AioContext in nvme_realize()
--- hw/block/nvme.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
hw/block/nvme.c +10 -3
@@ -1203,6 +1203,7 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp) {NvmeCtrl *n =NVME (pci_dev);NvmeIdCtrl *id = &n->id_ctrl; +AioContext *ctx;int i;int64_t bs_size;
@@ -1213,20 +1214,23 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp)return ; } + ctx =blk_get_aio_context (n->conf.blk); +aio_context_acquire (ctx); + bs_size =blk_getlength (n->conf.blk);if (bs_size <0 ) {error_setg (errp,"could not get backing file size" ); -return ; + goto out; }if (!n->serial) {error_setg (errp,"serial property not set" ); -return ; + goto out; }blkconf_blocksizes (&n->conf);if (!blkconf_apply_backend_options (&n->conf,blk_is_read_only (n->conf.blk), false, errp)) { -return ; + goto out; } pci_conf = pci_dev->config;
@@ -1323,6 +1327,9 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp)cpu_to_le64 (n->ns_size >> id_ns->lbaf[NVME_ID_NS_FLBAS_INDEX (ns->id_ns.flbas)].ds); } + +out: +aio_context_release (ctx); }static void nvme_exit (PCIDevice *pci_dev)
Signature · 1 line
2.11.0
PATCH v2 5/6 block: Acquire the AioContext in ide_dev_initfn()
In reply to Alberto Garcia--- hw/ide/qdev.c | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-)
hw/ide/qdev.c +12 -5
@@ -160,6 +160,7 @@ static void ide_dev_initfn(IDEDevice *dev, IDEDriveKind kind, Error **errp) {IDEBus *bus =DO_UPCAST (IDEBus, qbus, dev->qdev.parent_bus);IDEState *s = bus->ifs + dev->unit; +AioContext *ctx;int ret;if (!dev->conf.blk) {
@@ -174,36 +175,39 @@ static void ide_dev_initfn(IDEDevice *dev, IDEDriveKind kind, Error **errp) } } + ctx =blk_get_aio_context (dev->conf.blk); +aio_context_acquire (ctx); +if (dev->conf.discard_granularity ==-1 ) { dev->conf.discard_granularity =512 ; }else if (dev->conf.discard_granularity && dev->conf.discard_granularity !=512 ) {error_setg (errp,"discard_granularity must be 512 for ide" ); -return ; + goto out; }blkconf_blocksizes (&dev->conf);if (dev->conf.logical_block_size !=512 ) {error_setg (errp,"logical_block_size must be 512 for IDE" ); -return ; + goto out; }if (kind !=IDE_CD ) {if (!blkconf_geometry (&dev->conf, &dev->chs_trans,65535 ,16 ,255 , errp)) { -return ; + goto out; } }if (!blkconf_apply_backend_options (&dev->conf, kind ==IDE_CD , kind !=IDE_CD , errp)) { -return ; + goto out; }if (ide_init_drive (s, dev->conf.blk, kind, dev->version, dev->serial, dev->model, dev->wwn, dev->conf.cyls, dev->conf.heads, dev->conf.secs, dev->chs_trans, errp) <0 ) { -return ; + goto out; }if (!dev->version) {
@@ -215,6 +219,9 @@ static void ide_dev_initfn(IDEDevice *dev, IDEDriveKind kind, Error **errp)add_boot_device_path (dev->conf.bootindex, &dev->qdev, dev->unit ?"/disk@1" :"/disk@0" ); + +out: +aio_context_release (ctx); } static void ide_dev_get_bootindex(Object *obj, Visitor *v, const char *name,
Signature · 1 line
2.11.0
PATCH v2 6/6 block: Acquire the AioContext in usb_msd_storage_realize()
In reply to Alberto Garcia--- hw/usb/dev-storage.c | 5 +++++ 1 file changed, 5 insertions(+)
hw/usb/dev-storage.c +5 -0
@@ -593,13 +593,18 @@ static void usb_msd_storage_realize(USBDevice *dev, Error **errp)MSDState *s =USB_STORAGE_DEV (dev);BlockBackend *blk = s->conf.blk;SCSIDevice *scsi_dev; +AioContext *ctx;if (!blk) {error_setg (errp,"drive property not set" );return ; } + ctx =blk_get_aio_context (blk); +aio_context_acquire (ctx);blkconf_blocksizes (&s->conf); +aio_context_release (ctx); +if (!blkconf_apply_backend_options (&s->conf,blk_is_read_only (blk), true, errp)) {return ;
Signature · 1 line
2.11.0
PATCH v2 3/6 block: Acquire the AioContext in floppy_drive_realize()
In reply to Alberto Garcia--- hw/block/fdc.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
hw/block/fdc.c +11 -4
@@ -512,6 +512,7 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp) {FloppyDrive *dev =FLOPPY_DRIVE (qdev);FloppyBus *bus =FLOPPY_BUS (qdev->parent_bus); +AioContext *ctx;FDrive *drive;int ret;
@@ -543,13 +544,16 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)assert (ret ==0 ); } + ctx =blk_get_aio_context (dev->conf.blk); +aio_context_acquire (ctx); +blkconf_blocksizes (&dev->conf);if (dev->conf.logical_block_size !=512 || dev->conf.physical_block_size !=512 ) {error_setg (errp,"Physical and logical block size must " "be 512 for floppy" ); -return ; + goto out; }/* rerror/werror aren't supported by fdc and therefore not even registered
@@ -561,7 +565,7 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)if (!blkconf_apply_backend_options (&dev->conf,blk_is_read_only (dev->conf.blk), false, errp)) { -return ; + goto out; }/* 'enospc' is the default for -drive, 'report' is what blk_new() gives us
@@ -569,11 +573,11 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)if (blk_get_on_error (dev->conf.blk,0 ) !=BLOCKDEV_ON_ERROR_ENOSPC &&blk_get_on_error (dev->conf.blk,0 ) !=BLOCKDEV_ON_ERROR_REPORT ) {error_setg (errp,"fdc doesn't support drive option werror" ); -return ; + goto out; }if (blk_get_on_error (dev->conf.blk,1 ) !=BLOCKDEV_ON_ERROR_REPORT ) {error_setg (errp,"fdc doesn't support drive option rerror" ); -return ; + goto out; } drive->conf = &dev->conf;
@@ -589,6 +593,9 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp) dev->type = drive->drive;fd_revalidate (drive); + +out: +aio_context_release (ctx); }static void floppy_drive_class_init (ObjectClass *klass,void *data)
Signature · 1 line
2.11.0
PATCH v2 2/6 block: Acquire the AioContext in scsi_*_realize()
In reply to Alberto GarciaThis fixes a crash when adding a virtio-scsi device with a drive that is using an iothread. Test case included.
--- hw/scsi/scsi-disk.c | 23 ++++++++++++++++++++--- tests/qemu-iotests/236 | 43 +++++++++++++++++++++++++++++++++++++++++++ tests/qemu-iotests/236.out | 30 ++++++++++++++++++++++++++++++ 3 files changed, 93 insertions(+), 3 deletions(-)
hw/scsi/scsi-disk.c +20 -3
@@ -2381,10 +2381,13 @@ static void scsi_realize(SCSIDevice *dev, Error **errp)static void scsi_hd_realize (SCSIDevice *dev,Error **errp) {SCSIDiskState *s =DO_UPCAST (SCSIDiskState, qdev, dev); +AioContext *ctx =NULL ;/* can happen for devices without drive. The error message for missing * backend will be issued in scsi_realize */ if (s->qdev.conf.blk) { + ctx =blk_get_aio_context (s->qdev.conf.blk); +aio_context_acquire (ctx);blkconf_blocksizes (&s->qdev.conf); } s->qdev.blocksize = s->qdev.conf.logical_block_size;
@@ -2393,11 +2396,15 @@ static void scsi_hd_realize(SCSIDevice *dev, Error **errp) s->product =g_strdup ("QEMU HARDDISK" ); }scsi_realize (&s->qdev, errp); +if (ctx) { +aio_context_release (ctx); + } }static void scsi_cd_realize (SCSIDevice *dev,Error **errp) {SCSIDiskState *s =DO_UPCAST (SCSIDiskState, qdev, dev); +AioContext *ctx;int ret;if (!dev->conf.blk) {
@@ -2408,6 +2415,8 @@ static void scsi_cd_realize(SCSIDevice *dev, Error **errp)assert (ret ==0 ); } + ctx =blk_get_aio_context (dev->conf.blk); +aio_context_acquire (ctx); s->qdev.blocksize =2048 ; s->qdev.type =TYPE_ROM ; s->features |=1 <<SCSI_DISK_F_REMOVABLE ;
@@ -2415,6 +2424,7 @@ static void scsi_cd_realize(SCSIDevice *dev, Error **errp) s->product =g_strdup ("QEMU CD-ROM" ); }scsi_realize (&s->qdev, errp); +aio_context_release (ctx); }static void scsi_disk_realize (SCSIDevice *dev,Error **errp)
@@ -2553,6 +2563,7 @@ static int get_device_type(SCSIDiskState *s)static void scsi_block_realize (SCSIDevice *dev,Error **errp) {SCSIDiskState *s =DO_UPCAST (SCSIDiskState, qdev, dev); +AioContext *ctx;int sg_version;int rc;
@@ -2567,6 +2578,9 @@ static void scsi_block_realize(SCSIDevice *dev, Error **errp) "be removed in a future version"); } + ctx =blk_get_aio_context (s->qdev.conf.blk); +aio_context_acquire (ctx); +/* check we are using a driver managing SG_IO (version 3 and after) */ rc =blk_ioctl (s->qdev.conf.blk,SG_GET_VERSION_NUM , &sg_version);if (rc <0 ) {
@@ -2574,18 +2588,18 @@ static void scsi_block_realize(SCSIDevice *dev, Error **errp)if (rc != -EPERM ) {error_append_hint (errp,"Is this a SCSI device?\n" ); } -return ; + goto out; }if (sg_version <30000 ) {error_setg (errp,"scsi generic interface too old" ); -return ; + goto out; }/* get device type from INQUIRY data */ rc =get_device_type (s);if (rc <0 ) {error_setg (errp,"INQUIRY failed" ); -return ; + goto out; }/* Make a guess for the block size, we'll fix it when the guest sends.
@@ -2605,6 +2619,9 @@ static void scsi_block_realize(SCSIDevice *dev, Error **errp)scsi_realize (&s->qdev, errp);scsi_generic_read_device_inquiry (&s->qdev); + +out: +aio_context_release (ctx); } typedef struct SCSIBlockReq {
tests/qemu-iotests/236 +43 -0
49 lines not on this page · raw message
tests/qemu-iotests/236.out +30 -0
@@ -13,4 +13,34 @@ QMP_VERSION {"return": {}} {"return": {}} {"return": {}} + +=== Try adding and removing a virtio-scsi device with a hard drive === + +Testing: +QMP_VERSION +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} + +=== Try adding and removing a virtio-scsi device with a CD === + +Testing: +QMP_VERSION +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} *** done
Signature · 1 line
2.11.0
PATCH v2 1/6 block: Acquire the AioContext in virtio_blk_device_realize()
In reply to Alberto GarciaThis fixes a crash when adding a virtio-blk device with a drive that is using an iothread. Test case included.
--- hw/block/virtio-blk.c | 22 ++++++++----- tests/qemu-iotests/236 | 78 ++++++++++++++++++++++++++++++++++++++++++++++ tests/qemu-iotests/236.out | 16 ++++++++++ tests/qemu-iotests/group | 1 + 4 files changed, 110 insertions(+), 7 deletions(-) create mode 100755 tests/qemu-iotests/236 create mode 100644 tests/qemu-iotests/236.out
hw/block/virtio-blk.c +15 -7
@@ -912,6 +912,7 @@ static void virtio_blk_device_realize(DeviceState *dev, Error **errp)VirtIODevice *vdev =VIRTIO_DEVICE (dev);VirtIOBlock *s =VIRTIO_BLK (dev);VirtIOBlkConf *conf = &s->conf; +AioContext *ctx;Error *err =NULL ;unsigned i;
@@ -919,30 +920,34 @@ static void virtio_blk_device_realize(DeviceState *dev, Error **errp)error_setg (errp,"drive property not set" );return ; } + + ctx =blk_get_aio_context (conf->conf.blk); +aio_context_acquire (ctx); +if (!blk_is_inserted (conf->conf.blk)) {error_setg (errp,"Device needs media, but drive is empty" ); -return ; + goto out; }if (!conf->num_queues) {error_setg (errp,"num-queues property must be larger than 0" ); -return ; + goto out; }if (!is_power_of_2 (conf->queue_size) || conf->queue_size >VIRTQUEUE_MAX_SIZE ) {error_setg (errp,"invalid queue-size property (%" PRIu16"), " "must be a power of 2 (max %d)" , conf->queue_size,VIRTQUEUE_MAX_SIZE ); -return ; + goto out; }if (!blkconf_apply_backend_options (&conf->conf,blk_is_read_only (conf->conf.blk), true, errp)) { -return ; + goto out; } s->original_wce =blk_enable_write_cache (conf->conf.blk);if (!blkconf_geometry (&conf->conf,NULL ,65535 ,255 ,255 , errp)) { -return ; + goto out; }blkconf_blocksizes (&conf->conf);
@@ -951,7 +956,7 @@ static void virtio_blk_device_realize(DeviceState *dev, Error **errp) conf->conf.physical_block_size) {error_setg (errp,"logical_block_size > physical_block_size not supported" ); -return ; + goto out; } virtio_init(vdev, "virtio-blk", VIRTIO_ID_BLOCK,
@@ -968,7 +973,7 @@ static void virtio_blk_device_realize(DeviceState *dev, Error **errp)if (err !=NULL ) {error_propagate (errp, err);virtio_cleanup (vdev); -return ; + goto out; } s->change =qemu_add_vm_change_state_handler (virtio_blk_dma_restart_cb, s);
@@ -976,6 +981,9 @@ static void virtio_blk_device_realize(DeviceState *dev, Error **errp)blk_set_guest_block_size (s->blk, s->conf.conf.logical_block_size);blk_iostatus_enable (s->blk); + +out: +aio_context_release (ctx); }static void virtio_blk_device_unrealize (DeviceState *dev,Error **errp)
tests/qemu-iotests/236 new file +78 -0
78 lines not on this page · raw message
tests/qemu-iotests/236.out new file +16 -0
@@ -0,0 +1,16 @@ +QA output created by 236 + +=== Try adding and removing a virtio-blk device === + +Testing: +QMP_VERSION +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +{"return": {}} +*** done
tests/qemu-iotests/group +1 -0
@@ -233,3 +233,4 @@ 233 auto quick 234 auto quick migration 235 auto quick +236 auto quick
Signature · 1 line
2.11.0
Quoted 6 lines · Alberto Garcia
This series acquires the AioContext in the
_realize()functions of several devices before making use of their block backends. This fixes at least a couple of crashes (in virtio-blk and scsi). The other devices don't currently support iothreads so there's no crashes.Berto
My assumption has been that drives are in the main loop AioContext until the device model (e.g. virtio-blk) decides to move them into the IOThread configured by the user.
(And when the VM is stopped or the device is removed, the drive is moved back into the main loop AioContext by the device.)
The x-blockdev-set-iothread command is for low-level tests so I don't expect users to invoke it. So I'm not sure which real-world scenario is being tested here?
This patch series makes virtio-blk and virtio-scsi more robust, although I haven't checked what happens if the drive is attached to a different IOThread than the device - will the switchover work?
What I'm unclear about is why fdc, ide, usb-msd, and nvme should worry about IOThreads/AioContext in .realize() since they don't support it in their data path. What happens when you submit I/O requests to devices configured like this? I guess they would crash or hit assertion failures since they invoke blk_aio_*() APIs from outside the appropriate AioContext.
Maybe fdc and friends should forbid this scenario:
/* Fail if @blk is attached to an IOThread */
static bool blk_check_main_aio_context(BlockBackend *blk, Error **errp) {
if (blk_get_aio_context(blk) != qemu_get_aio_context()) {
error_setg(errp, "Device does not support iothreads");
return false;
}
return true;
}
...in a realize() function...
if (!blk_check_main_aio_context(blk, errp)) {
return;
}Quoted 2 lines · Stefan Hajnoczi
The x-blockdev-set-iothread command is for low-level tests so I don't expect users to invoke it.
As I said in a different e-mail maybe this is not necessary then.
Quoted 3 lines
This patch series makes virtio-blk and virtio-scsi more robust, although I haven't checked what happens if the drive is attached to a different IOThread than the device - will the switchover work?
You mean if you use x-blockdev-set-iothread with a drive and then attach it to a device using a different thread? That seems to work (with my patch).
Quoted 8 lines
What I'm unclear about is why fdc, ide, usb-msd, and nvme should worry about IOThreads/AioContext in .realize() since they don't support it in their data path. What happens when you submit I/O requests to devices configured like this? I guess they would crash or hit assertion failures since they invoke blk_aio_*() APIs from outside the appropriate AioContext.
Maybe fdc and friends should forbid this scenario:
Yeah, that seems like a simple solution.
Berto
Quoted 8 lines · Alberto Garcia
Quoted 3 lines · Stefan Hajnoczi
This patch series makes virtio-blk and virtio-scsi more robust, although I haven't checked what happens if the drive is attached to a different IOThread than the device - will the switchover work?
You mean if you use x-blockdev-set-iothread with a drive and then attach it to a device using a different thread? That seems to work (with my patch).
Does it work with a running VM that will do I/O? If yes, then that's great and we should merge the virtio-blk/scsi patches to make them robust for this case. I'm a little surprised it works though :-) because the code wasn't designed or tested for this.
Stefan
Am 18.01.2019 um 10:56 hat Stefan Hajnoczi geschrieben:
Quoted 6 lines · Alberto Garcia
Quoted 5 lines · Stefan Hajnoczi
Quoted 3 lines
This patch series makes virtio-blk and virtio-scsi more robust, although I haven't checked what happens if the drive is attached to a different IOThread than the device - will the switchover work?
Quoted 8 lines
Quoted 3 lines
You mean if you use x-blockdev-set-iothread with a drive and then attach it to a device using a different thread? That seems to work (with my patch).
Does it work with a running VM that will do I/O? If yes, then that's great and we should merge the virtio-blk/scsi patches to make them robust for this case. I'm a little surprised it works though :-) because the code wasn't designed or tested for this.
There are two ways to trigger the crash even without x-blockdev-set-iothread:
* device_del, then device_add for a device with iothread (virtio-scsi; may or may not exist with virtio-blk)
https://bugzilla.redhat.com/show_bug.cgi?id=1656276
* Simply attach two devices with iothread to the the same node
https://bugzilla.redhat.com/show_bug.cgi?id=1662508
Maybe this series is actually papering over the real problems, though. Unplug should move the BDS back to the main AioContext, and attaching two users with different AioContexts must fail. If we don't take care there, the locking will be wrong.
Note that even though there are more problems, we still need this series so we can allow attaching two devices to the same node while using the same iothread.
Kevin
Am 14.01.2019 um 15:23 hat Alberto Garcia geschrieben:
Quoted 7 lines
This series acquires the AioContext in the
_realize()functions of several devices before making use of their block backends. This fixes at least a couple of crashes (in virtio-blk and scsi). The other devices don't currently support iothreads so there's no crashes.tests/qemu-iotests/236 | 121 +++++++++++++++++++++++++++++++++++++++++++++ tests/qemu-iotests/236.out | 46 +++++++++++++++++
236 is already taken by two other series. :-)
I'll use 239 and 239.out for the conflict resolution, so I think the next free one for you is 240.
Kevin
Quoted 9 lines · Kevin Wolf
There are two ways to trigger the crash even without x-blockdev-set-iothread:
*
device_del, thendevice_addfor a device with iothread (virtio-scsi; may or may not exist with virtio-blk)
https://bugzilla.redhat.com/show_bug.cgi?id=1656276* Simply attach two devices with iothread to the the same node
https://bugzilla.redhat.com/show_bug.cgi?id=1662508
While having a look at this I found another crash. Here's how to reproduce it (wait for the events after each system_reset):
{ "execute": "qmp_capabilities" }
{ "execute": "blockdev-add", "arguments": {"driver": "null-co", "node-name": "hd0"}} { "execute": "device_add", "arguments": {"id": "vb0", "driver": "virtio-blk", "drive": "hd0"}} { "execute": "system_reset"}
{ "execute": "device_del", "arguments": {"id": "vb0"}} { "execute": "system_reset"}
{ "execute": "device_add", "arguments": {"id": "vb0", "driver": "virtio-blk", "drive": "hd0"}} { "execute": "system_reset"}
{ "execute": "device_del", "arguments": {"id": "vb0"}} { "execute": "system_reset"}
{ "execute": "device_add", "arguments": {"id": "vb0", "driver": "virtio-blk", "drive": "hd0"}} { "execute": "system_reset"}
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Aborted
git-bisect points to this commit:
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <[email protected]>
Date: Wed Nov 28 17:28:45 2018 +0100
memory: update coalesced_range on transaction_commit
The e1000 driver calls memory_region_add_coalescing but kvm_coalesce_mmio_region is never called for those regions. The bug dates back to the introduction of the memory region API; to fix it, delete and re-add coalesced MMIO ranges when building the FlatViews.
Because coalesced MMIO regions apply to all address spaces, the has_coalesced_range flag has to be changed into an int.
Berto