[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCHv3 12/13] qemu: virtio save/load bindings
From: |
Glauber Costa |
Subject: |
Re: [Qemu-devel] [PATCHv3 12/13] qemu: virtio save/load bindings |
Date: |
Tue, 9 Jun 2009 14:45:54 -0300 |
User-agent: |
Jack Bauer |
duplicated save config.
> diff --git a/hw/virtio.h b/hw/virtio.h
> index 04a3c3d..ce05517 100644
> --- a/hw/virtio.h
> +++ b/hw/virtio.h
> @@ -72,6 +72,10 @@ typedef struct VirtQueueElement
>
> typedef struct {
> void (*notify)(void * opaque, uint16_t vector);
> + void (*save_config)(void * opaque, QEMUFile *f);
> + void (*save_queue)(void * opaque, int n, QEMUFile *f);
> + int (*load_config)(void * opaque, QEMUFile *f);
> + int (*load_queue)(void * opaque, int n, QEMUFile *f);
> } VirtIOBindings;
>
So, what's the overall effect on a virtual machine that gets migrated,
of a certain device not implementing one of those functions? Will it work?
Will it break?