* [Qemu-devel] register_savevm()
@ 2015-04-17 13:03 Catalin Vasile
2015-04-17 13:40 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: Catalin Vasile @ 2015-04-17 13:03 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 99 bytes --]
When are save() and load() handlers actually used?
When are they trying to save and restore state?
[-- Attachment #2: Type: text/html, Size: 138 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] register_savevm()
2015-04-17 13:03 [Qemu-devel] register_savevm() Catalin Vasile
@ 2015-04-17 13:40 ` Peter Maydell
2015-04-17 13:54 ` Catalin Vasile
0 siblings, 1 reply; 4+ messages in thread
From: Peter Maydell @ 2015-04-17 13:40 UTC (permalink / raw)
To: Catalin Vasile; +Cc: QEMU Developers
On 17 April 2015 at 14:03, Catalin Vasile <catalinvasile92@gmail.com> wrote:
> When are save() and load() handlers actually used?
> When are they trying to save and restore state?
These are used for:
* live migration
* VM state save/load (eg via monitor 'savevm' and 'loadvm'
commands or command line -loadvm option).
Note that the register_savevm() function is legacy and should
not be used in any new code. Devices should use VMStateDescription
structs instead.
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] register_savevm()
2015-04-17 13:40 ` Peter Maydell
@ 2015-04-17 13:54 ` Catalin Vasile
2015-04-17 14:02 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: Catalin Vasile @ 2015-04-17 13:54 UTC (permalink / raw)
To: Peter Maydell; +Cc: QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Does loadvm create new virtual devices (dev.init(), dev.realize(), etc.)
for the vm to run onto and then load VMStateDescription?
On Fri, Apr 17, 2015 at 4:40 PM, Peter Maydell <peter.maydell@linaro.org>
wrote:
> On 17 April 2015 at 14:03, Catalin Vasile <catalinvasile92@gmail.com>
> wrote:
> > When are save() and load() handlers actually used?
> > When are they trying to save and restore state?
>
> These are used for:
> * live migration
> * VM state save/load (eg via monitor 'savevm' and 'loadvm'
> commands or command line -loadvm option).
>
> Note that the register_savevm() function is legacy and should
> not be used in any new code. Devices should use VMStateDescription
> structs instead.
>
> -- PMM
>
[-- Attachment #2: Type: text/html, Size: 1161 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] register_savevm()
2015-04-17 13:54 ` Catalin Vasile
@ 2015-04-17 14:02 ` Peter Maydell
0 siblings, 0 replies; 4+ messages in thread
From: Peter Maydell @ 2015-04-17 14:02 UTC (permalink / raw)
To: Catalin Vasile; +Cc: QEMU Developers
On 17 April 2015 at 14:54, Catalin Vasile <catalinvasile92@gmail.com> wrote:
> Does loadvm create new virtual devices (dev.init(), dev.realize(), etc.) for
> the vm to run onto and then load VMStateDescription?
loadvm itself does not, no. You have to start QEMU with the
exact same configuration and command line options, which
means the usual startup will create all the devices and
connect them up. Then you can do a loadvm which will read
the state into all the existing devices.
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-04-17 14:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-17 13:03 [Qemu-devel] register_savevm() Catalin Vasile
2015-04-17 13:40 ` Peter Maydell
2015-04-17 13:54 ` Catalin Vasile
2015-04-17 14:02 ` Peter Maydell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).