summaryrefslogtreecommitdiff
path: root/block/qcow.c
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2017-07-17 17:37:42 +0100
committerPeter Maydell <peter.maydell@linaro.org>2017-07-25 13:04:28 +0100
commit4c4414a4388f902b7ae2814f9a64898dd0e426a5 (patch)
tree231aff794b6c6c312e572bd04ec615404d2f1b4b /block/qcow.c
parent5fb203a1991d2a93e47f76f063a7ce3563b91942 (diff)
downloadqemu-4c4414a4388f902b7ae2814f9a64898dd0e426a5.tar.gz
hw/display/sm501: Don't use vmstate_register_ram_global()
The sm501 device uses vmstate_register_ram_global() to register its memory region for migration. This means it gets a name that is assumed to be global to the whole system, which in turn means that if you create two of the device we assert because of the duplication: qemu-system-ppc -device sm501 -device sm501 RAMBlock "sm501.local" already registered, abort! Aborted (core dumped) Changing this to just use memory_region_init_ram()'s automatic registration of the memory region with a device-local name fixes this. The downside is that it breaks migration compatibility, but luckily we only added migration support to this device in the 2.10 release cycle so we haven't released a QEMU version with the broken implementation. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Message-id: 1500309462-12792-1-git-send-email-peter.maydell@linaro.org
Diffstat (limited to 'block/qcow.c')
0 files changed, 0 insertions, 0 deletions