Date: Sat, 29 Apr 2023 14:41:07 +0200 From: Guido Falsi <mad@madpilot.net> To: Mario Marietto <marietto2008@gmail.com>, Tomek CEDRO <tomek@cedro.info> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: BHYVE_SNAPSHOT Message-ID: <9ec8d674-0e1e-5701-7879-3e61e68b5976@madpilot.net> In-Reply-To: <CA%2B1FSig0VTxRcBRcUUWZy%2BkDyTyPmuhAD9yMb8Q7wiZ=F5Mztg@mail.gmail.com> References: <ZEz8tU_83QfqbbMu@int21h> <CAFYkXj=vuFTdu9uWj8rWfmOc6ZHJY9nARH9YC2wwTOe1sRAM3A@mail.gmail.com> <78195461-2297-ca49-22a5-291cd805d59a@madpilot.net> <CAFYkXj=-QjOgsJduqVQEd5DcqtJn9UZpfg4z2orfCP7Rf7XFGA@mail.gmail.com> <CA%2B1FSig0VTxRcBRcUUWZy%2BkDyTyPmuhAD9yMb8Q7wiZ=F5Mztg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/04/23 14:06, Mario Marietto wrote: > Hello. > > I do the smapshots of the bhyve vms simply by copying the img file with > the cp command. What the "internal" function added by the developers add > to what I already do ? As explained in my message this "snapshot" functionality allows snapshotting live machines, keeping their state and RAM, allowing for a "live and running" VM to be suspended and restarted at a later time, maybe even on another physical machine. I don't know the details, it is quite possible that to move to another physical machine some extra requirements apply, like, for example, having the very same CPU model, or a very similar one. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ec8d674-0e1e-5701-7879-3e61e68b5976>