| commit | aede5d5dfc5f3e4ea7467b28c51fda2f8945d117 | |
| author | Cornelia Huck <cohuck@redhat.com> | |
| Fri, 1 Feb 2019 12:29:08 +0000 (1 13:29 +0100) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Mon, 4 Feb 2019 12:47:50 +0000 (4 13:47 +0100) | ||
| tree | 5fbf714d7e82898e7922dcfee3dd0610e8f76027 | treesnapshot (tar.gz zip) |
| parent | 9f2a46b11139cd21c41f4d97c0416af6f9e76f7b | commitdiff |
s390x/pci: mark zpci devices as unmigratable
We currently don't migrate any state for zpci devices, which are
coupled with standard pci devices. This means funny things happen
when we e.g. try to migrate with a virtio-pci device but the s390x-
specific zpci state is not migrated (vfio-pci is not affected, as
it is not migratable anyway.)
Until this is fixed, mark zpci devices as unmigratable.
Reported-by: David Hildenbrand <david@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
We currently don't migrate any state for zpci devices, which are
coupled with standard pci devices. This means funny things happen
when we e.g. try to migrate with a virtio-pci device but the s390x-
specific zpci state is not migrated (vfio-pci is not affected, as
it is not migratable anyway.)
Until this is fixed, mark zpci devices as unmigratable.
Reported-by: David Hildenbrand <david@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| hw/s390x/s390-pci-bus.c | diffblobblamehistory |