actually=2C live snapshot today is only supported for disks=2C without=
--_3064f56a-7a6a-4abf-8891-68ba87d085f3_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable the
RAM. I can not find the button to create a snapshot for disk only in engine 3.1 beta release. Are you talking about a undergoing project? =20 live snapshot is for disks only=2C not for RAM. so the live snapshot button only snapshots the disks already. =20 How does this compare to other virtualization solutions?To me it seems like= "live snapshot" is the wrong term to use if it doesn't include the RAM sta= te. Specifically thinking of VirtualBox or VMWare Workstation... if I take = a "snapshot" of a running system the disk and RAM states are preserved in t= hat snapshot. If the VM is shut down=2C then only a snapshot of the disks i= s taken. Being that 3.1 is really close and this likely can't change (if su= ch a change were to be made)=2C can we at least have this noted somewhere i= n the documentation and/or interface that that is how "live snapshots" work= s at the current time? disk state only=2C no RAM state. If it's already the= re then I shall go to the quiet corner and RTFM. - Nick =
--_3064f56a-7a6a-4abf-8891-68ba87d085f3_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 10pt=3B font-family:Tahoma } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'> >=3B >=3B>=3B actually=2C live snapshot today is only supported for d= isks=2C without the<br>>=3B >=3B>=3B RAM.<br>>=3B >=3B I can not = find the button to create a snapshot for disk only in engine<br>>=3B >= =3B 3.1 beta release. Are you talking about a undergoing project?<br>>=3B= <br>>=3B live snapshot is for disks only=2C not for RAM.<br>>=3B so th= e live snapshot button only snapshots the disks already.<br>>=3B <br><BR>= How does this compare to other virtualization solutions?<BR>To me it seems = like =3B"live snapshot" is the wrong term to use if it doesn't include = the =3BRAM state. Specifically thinking of VirtualBox or VMWare Worksta= tion... if I take a "snapshot" of a running system the disk <strong>and </s= trong>RAM states are preserved in that snapshot. If the VM is shut down=2C = then only a snapshot of the disks is taken.<BR> =3B<BR>Being that 3.1 i= s really close and this likely can't change (if such a change were to be ma= de)=2C can we at least have this noted somewhere in the documentation = =3Band/or interface =3Bthat that is how "live snapshots" works at the c= urrent time? disk state only=2C no RAM state. If it's already there then I = shall go to the quiet corner and RTFM.<BR> =3B<BR>- Nick<BR> = </div></body> </html>= --_3064f56a-7a6a-4abf-8891-68ba87d085f3_--