Hello Anthony,
> virsh migrate-setmaxdowntime
The migrate-setmaxdowntime operates with milliseconds, but apart from
that, we were able to migrate the VM under heavy load (8 CPUs running at
100%, load being 17-20 constantly)
We used a maximum downtime of 1000 milliseconds and it popped to the
o
> It works like a charm, even without shared storage, but when we try to
> migrate a VM under a little pressure (a HTTP server gets some 1-5
> requests/sec) the migration process hangs at 99%.
The maxdowntime is probably too low for the migration to complete. Try
setting it to a higher value :
vi
