Some more followup questions below to help me debug before I start
digging in.......
On 05/09/2013 06:20 PM, Chegu Vinod wrote:
Setting aside the mlock() freezes for the moment, let's first fix your
crashing
problem on the destination-side. Let's make that a priority before we fix
the mlock problem.
When the migration "completes", can you provide me with more detailed
information
about the state of QEMU on the destination?
Is it responding?
What's on the VNC console?
Is QEMU responding?
Is the network responding?
Was the VM idle? Or running an application?
Can you attach GDB to QEMU after the migration?
/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
-cpu host \
-name vm1 \
-m 131072 -smp 10,sockets=1,cores=10,threads=1 \
-mem-path /dev/hugepages \
Can you disable hugepages and re-test?
I'll get back to the other mlock() issues later after we at least first
make sure the migration itself is working.....
