aboutsummaryrefslogtreecommitdiff
path: root/target-sh4
diff options
context:
space:
mode:
authorJason J. Herne <jjherne@linux.vnet.ibm.com>2015-06-03 11:04:03 -0400
committerChristian Borntraeger <borntraeger@de.ibm.com>2015-06-03 18:07:05 +0200
commit2a72ea5f66b3b87a975475bdc1cabacbbb402937 (patch)
treeb884e677c1bb428a2d544577d868e00f3f4dc07f /target-sh4
parentde6a92185e3ac25ba7d37f03e579b1fc72e70162 (diff)
downloadqemu-2a72ea5f66b3b87a975475bdc1cabacbbb402937.zip
qemu-2a72ea5f66b3b87a975475bdc1cabacbbb402937.tar.gz
qemu-2a72ea5f66b3b87a975475bdc1cabacbbb402937.tar.bz2
virtio-ccw/migration: Migrate config vector for virtio devices
virtio_ccw_{save|load}_config are missing code to save and restore a vdev's config_vector value. This causes some virtio devices to become disabled following a migration. This patch fixes a bug whereby the qmp/hmp balloon command (virsh setmem) silently fails to update the guest's available memory because the device was not properly migrated. This will break compatibility, but vmstate_s390_cpu was bumped from version 2 to version 4 between v2.3.0 and v2.4.0 without a compat handler. Furthermore, there is no production environment yet so migration is fenced anyway between any relevant version of 2.3 and 2.4. Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com> Message-Id: <1433343843-803-1-git-send-email-jjherne@linux.vnet.ibm.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'target-sh4')
0 files changed, 0 insertions, 0 deletions