Confirmed that doing
kvm -drive file=lucid.img,cache=unsafe,index=0,boot=on -m 512M -smp 2 -vnc :1 -monitor stdio
and doing 'savevm savevm5'
takes about 2 seconds.
So, for fast savevm, 'cache=unsafe' is the workaround. Shoudl this bug then be marked invalid, or 'wontfix'?
Confirmed that doing
kvm -drive file=lucid. img,cache= unsafe, index=0, boot=on -m 512M -smp 2 -vnc :1 -monitor stdio
and doing 'savevm savevm5'
takes about 2 seconds.
So, for fast savevm, 'cache=unsafe' is the workaround. Shoudl this bug then be marked invalid, or 'wontfix'?