On Thu, Feb 13, 2014 at 12:08:37AM +0530, Kashyap Chamarthy wrote:
[. . .]
Try a couple more things
- Run `qemu-sanity-check` in L1 -- Of course, this fails too.
- Invoke (from a different shell, as root) QEMU directly with gdb
debugging options -s -S with
On Thu, Feb 13, 2014 at 12:08:37AM +0530, Kashyap Chamarthy wrote:
The 'qemu-kvm' command-line just hung at:
$ ./run libguestfs-test-tool
[. . .]
-chardev
socket,path=/home/tuser1/src/libguestfs/tmp/libguestfspCGc1F/guestfsd.sock,id=channel0
\
-device
Heya,
With latest Fedora Rawhide Kernel, I see a nested KVM guest hanging at
boot (not unusual). Rich once suggested this[1] to try to attach gdb to
the nested L2 guest to find out where_ it's stuck, tonight I set out to
try it out (with KVM TCG).
Below is all what I tried.
In guest hypervisor
