ers
Subject: Re: Virtual machines volume lock manager
I would advise trying to reproduce.
start migration, then either:
- configure timeout so that it''s way too low, so that migration fails due to
timeouts.
- restart mgmt server in the middle of migrations This should cause migration
to fail - and
I would advise trying to reproduce.
start migration, then either:
- configure timeout so that it''s way too low, so that migration fails due
to timeouts.
- restart mgmt server in the middle of migrations
This should cause migration to fail - and you can observe if you have
reproduced the problem.
Hi Andrija
Sorry for the late reply.
Im using 4.7 version of ACS. Qemu version 1:2.5+dfsg-5ubuntu10.40
Im not sure if ACS job failed or libvirt job as I didnt see into logs.
Yes the vm will be in paused state during migration but after the failed
migration, the same vm was in "running" state
I've been running KVM public cloud up to recently and have never seen such
behaviour.
What versions (ACS, qemu, libvrit) are you running?
How does the migration fail - ACS job - or libvirt job?
destination VM is by default always in PAUSED state, until the migration is
finished - only then the
