virtio-crypto: tag as not hotpluggable and migration
Currently the virtio-crypto device hasn't supported hotpluggable and live migration well. Let's tag it as not hotpluggable and migration actively and reopen them once we support them well. Suggested-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Gonglei <arei.gonglei@huawei.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
This commit is contained in:
parent
bf91bd2792
commit
6e724d9d99
@ -48,7 +48,7 @@ static void virtio_crypto_pci_class_init(ObjectClass *klass, void *data)
|
||||
k->realize = virtio_crypto_pci_realize;
|
||||
set_bit(DEVICE_CATEGORY_MISC, dc->categories);
|
||||
dc->props = virtio_crypto_pci_properties;
|
||||
|
||||
dc->hotpluggable = false;
|
||||
pcidev_k->class_id = PCI_CLASS_OTHERS;
|
||||
}
|
||||
|
||||
|
@ -813,6 +813,7 @@ static void virtio_crypto_device_unrealize(DeviceState *dev, Error **errp)
|
||||
|
||||
static const VMStateDescription vmstate_virtio_crypto = {
|
||||
.name = "virtio-crypto",
|
||||
.unmigratable = 1,
|
||||
.minimum_version_id = VIRTIO_CRYPTO_VM_VERSION,
|
||||
.version_id = VIRTIO_CRYPTO_VM_VERSION,
|
||||
.fields = (VMStateField[]) {
|
||||
|
Loading…
Reference in New Issue
Block a user