Whilst investigating a migration issue, I noticed that the analyze-migration.py script had accidentally been broken by commit 61964.
I've implemented a quick workaround to parse the configuration section into a separate Python object, however the solution works by parsing the SaveState properties directly rather than reading them dynamically. This is because vmstate_save_state() doesn't have a valid QJSON object available at the time the configuration is written out which makes it tricky to include the configuration state in the JSON schema. This is probably a reasonable solution if the configuration state is deemed to be static, although more thought is required if it is deemed useful for the machine name to be made available in the analyze-migration.py JSON output or if the configuration properties should be read dynamically. Signed-off-by: Mark Cave-Ayland <mark.cave-ayl...@ilande.co.uk> Mark Cave-Ayland (1): migration: fix analyze-migration.py script scripts/analyze-migration.py | 13 +++++++++++++ 1 file changed, 13 insertions(+) -- 1.7.10.4
