[pve-devel] savevm tests

[Dietmar Maurer]

> here how I see things:
> 
> 
> for nexenta:
>      no vmstate(no possible)

Why not possible? We can simply allocate a normal volume, and store state there?

>      ----------
>    - send freeze-fs via qemu-ga if available
>    - use nexenta api to snapshot all disks
>    - unfreeze freeze-fs via qemu-ga if available
> 
> for rbd:
>     no vmstate (not available)
>     ----------
>    - send freeze-fs via qemu-ga if available
>    - savevm.  (or rbd command, it's works too)
>    - unfreeze freeze-fs via qemu-ga if available
> 
> for sheepdog:
>     vmstate
>     -------
>     savevm
> 
>     novmstate
>     ---------
>    - send freeze-fs via qemu-ga if available and if we don't don't
>    - savevm.  (or rbd command, it's works too)
>    - unfreeze freeze-fs via qemu-ga if available
> 
> 
> for qcow2:
>     vmstate
>     -------
>     savevm
> 
>     novmstate
>     ---------
>    - send freeze-fs via qemu-ga if available and if we don't don't
>    - savevm.  (or rbd command, it's works too)
>    - unfreeze freeze-fs via qemu-ga if available


We have VM which use qcow2, sheepdog, rdb and nexenta at the same time. How should that work?