On 08/28/2009 04:55 PM, Chris Lalancette wrote:
While reproducing this issue, I also noticed that we wouldn't
always properly propagate an error message. In particular, I
found that if you blocked off the migration ports (with iptables)
and then tried the migration, it would actually fail but we would
get no failure output from Qemu. Therefore, we would think we
succeeded, and leave a huge mess behind us. Execute the monitor
command "info migrate", and look for a failure string in there
as well.
ACK! Thanks for reproducing my precise failure mode, too, especially
since it turned out to be a second bug.
Paolo