summaryrefslogtreecommitdiffstats
path: root/hw/block/nvme.c
diff options
context:
space:
mode:
authorVladimir Sementsov-Ogievskiy2019-01-24 13:25:24 +0100
committerKevin Wolf2019-05-20 17:08:56 +0200
commit9183dd15334f1eee46051bbdafc6ab9fbfc2efd5 (patch)
tree815f2c7ee07a574688f13144f2cb23241e090349 /hw/block/nvme.c
parentblock: Use BDRV_REQUEST_MAX_BYTES instead of BDRV_REQUEST_MAX_SECTORS (diff)
downloadqemu-9183dd15334f1eee46051bbdafc6ab9fbfc2efd5.tar.gz
qemu-9183dd15334f1eee46051bbdafc6ab9fbfc2efd5.tar.xz
qemu-9183dd15334f1eee46051bbdafc6ab9fbfc2efd5.zip
qmp: forbid qmp_cont in RUN_STATE_FINISH_MIGRATE
qmp_cont in RUN_STATE_FINISH_MIGRATE may lead to moving vm to RUN_STATE_RUNNING, before actual migration finish. So, when migration thread will try to go to RUN_STATE_POSTMIGRATE, assuming transition RUN_STATE_FINISH_MIGRATE->RUN_STATE_POSTMIGRATE, it will crash, as current state is RUN_STATE_RUNNING, and transition RUN_STATE_RUNNING->RUN_STATE_POSTMIGRATE is forbidden. Reported-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/block/nvme.c')
0 files changed, 0 insertions, 0 deletions