From d3674c5754775eb65ec2f2fd5f8cfe9b032ca0b1 Mon Sep 17 00:00:00 2001 From: Jason Wang Date: Wed, 18 May 2011 13:57:37 +0800 Subject: virtio: correctly initialize vm_running Current vm_running was not explicitly initialized and its value was changed by vm state notifier, this may confuse the virtio device being hotplugged such as virtio-net with vhost backend as it may think the vm was not running. Solve this by initialize this value explicitly in virtio_common_init(). Signed-off-by: Jason Wang Signed-off-by: Michael S. Tsirkin --- hw/virtio.c | 1 + 1 file changed, 1 insertion(+) (limited to 'hw/virtio.c') diff --git a/hw/virtio.c b/hw/virtio.c index a651860..36b8f35 100644 --- a/hw/virtio.c +++ b/hw/virtio.c @@ -787,6 +787,7 @@ VirtIODevice *virtio_common_init(const char *name, uint16_t device_id, vdev->queue_sel = 0; vdev->config_vector = VIRTIO_NO_VECTOR; vdev->vq = qemu_mallocz(sizeof(VirtQueue) * VIRTIO_PCI_QUEUE_MAX); + vdev->vm_running = vm_running; for(i = 0; i < VIRTIO_PCI_QUEUE_MAX; i++) { vdev->vq[i].vector = VIRTIO_NO_VECTOR; vdev->vq[i].vdev = vdev; -- cgit v1.1