diff options
| author | Jason Andryuk <jandryuk@gmail.com> | 2020-10-13 15:05:06 -0400 |
|---|---|---|
| committer | Anthony PERARD <anthony.perard@citrix.com> | 2020-10-19 16:33:28 +0100 |
| commit | 8959e0a63a3a681a31ff8397d9345a88e6d905bf (patch) | |
| tree | 20c52f0ce6a2945594757e6080f9a900e64945ad /tests/test-crypto-tlscredsx509.c | |
| parent | c4583c8c394ee49ce7d5271f572abd3b000fa9e4 (diff) | |
| download | qemu-8959e0a63a3a681a31ff8397d9345a88e6d905bf.zip qemu-8959e0a63a3a681a31ff8397d9345a88e6d905bf.tar.gz qemu-8959e0a63a3a681a31ff8397d9345a88e6d905bf.tar.bz2 | |
hw/xen: Set suppress-vmdesc for Xen machines
xen-save-devices-state doesn't currently generate a vmdesc, so restore
always triggers "Expected vmdescription section, but got 0". This is
not a problem when restore comes from a file. However, when QEMU runs
in a linux stubdom and comes over a console, EOF is not received. This
causes a delay restoring - though it does restore.
Setting suppress-vmdesc skips looking for the vmdesc during restore and
avoids the wait.
The other approach would be generate a vmdesc in qemu_save_device_state.
Since COLO shared that function, and the vmdesc is just discarded on
restore, we choose to skip it.
Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Message-Id: <20201013190506.3325-1-jandryuk@gmail.com>
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Diffstat (limited to 'tests/test-crypto-tlscredsx509.c')
0 files changed, 0 insertions, 0 deletions