I'm seeing behaviour that looks like this on karmic/amd64, only a suspend/resume doesn't "fix" the VM. It stays hard locked. I can connect to it on the virtual serial console or via VNC, and it shows what was there before the migration, but it never unlocks and starts working.
I'm seeing behaviour that looks like this on karmic/amd64, only a suspend/resume doesn't "fix" the VM. It stays hard locked. I can connect to it on the virtual serial console or via VNC, and it shows what was there before the migration, but it never unlocks and starts working.