diff options
| author | Peter Xu <peterx@redhat.com> | 2024-12-06 18:08:33 -0500 |
|---|---|---|
| committer | Fabiano Rosas <farosas@suse.de> | 2025-01-09 17:38:41 -0300 |
| commit | 7815f69867da92335055d4b5248430b0f122ce4e (patch) | |
| tree | 7350cdb885970df8e9c20dcf952d7a6c45225993 /rust/qemu-api | |
| parent | b93d897ea2f0abbe7fc341a9ac176b5ecd0f3c93 (diff) | |
| download | qemu-7815f69867da92335055d4b5248430b0f122ce4e.zip qemu-7815f69867da92335055d4b5248430b0f122ce4e.tar.gz qemu-7815f69867da92335055d4b5248430b0f122ce4e.tar.bz2 | |
migration: Add helper to get target runstate
In 99% cases, after QEMU migrates to dest host, it tries to detect the
target VM runstate using global_state_get_runstate().
There's one outlier so far which is Xen that won't send global state.
That's the major reason why global_state_received() check was always there
together with global_state_get_runstate().
However it's utterly confusing why global_state_received() has anything to
do with "let's start VM or not".
Provide a helper to explain it, then we have an unified entry for getting
the target dest QEMU runstate after migration.
Suggested-by: Fabiano Rosas <farosas@suse.de>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20241206230838.1111496-2-peterx@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'rust/qemu-api')
0 files changed, 0 insertions, 0 deletions