Comment #4 on issue 986 by [email protected]: VM hanging on 100%
after live-migration
https://code.google.com/p/ganeti/issues/detail?id=986
I debuged this a little more and found out that the monitor socket works,
I could get details like "info registers" (which were changing)
but creating screenshots would only give a black image
and "log [all]" wouldn't print anything into the logfiles (I even enabled
this on VMs which crashed before they migrated)
The only thing i noticed is that all other VMs had a "(halted)" in
there "info cpus" (I suppose this means that the VM was atm. idle)
# hanging VM
(qemu) QEMU 2.1.2 monitor - type 'help' for more information
(qemu) info cpus
* CPU #0: pc=0xffffffff81036228 thread_id=31975
CPU #1: pc=0xffffffff8103622f thread_id=31976
CPU #2: pc=0xffffffff81036228 thread_id=31977
CPU #3: pc=0xffffffff81036239 thread_id=31978
# running VM
(qemu) QEMU 2.1.2 monitor - type 'help' for more information
(qemu) info cpus
* CPU #0: pc=0xffffffff8102b36c (halted) thread_id=30967
CPU #1: pc=0xffffffff8102b36c (halted) thread_id=30968
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings