Parag Warudkar wrote: > Avi Kivity <[EMAIL PROTECTED]> writes: > > >> Parag Warudkar wrote: >> >>> And this in dmesg - >>> kvm_handle_exit: unexpected, valid vectoring info >>> and exit reason is 0x9 >>> >>> >> Exit 9 is a hardware task switch, which is not supported by vmx. It's >> unlikely solaris is using it; probably some other failure before caused >> it to take the wrong route. >> >> > > Yeah something obviously went wrong when the installation got stuck earlier. > One thing which is good is that the installation seems to get stuck at the > same place every time. > > Is there a way to know where it is getting stuck down under > in the bowels of KVM? > >
You can add a signal handler to qemu/kvm-qemu.c to call kvm_get_regs() and print them out. From the rip you can see what Solaris is doing (assuming you have debug symbols). -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
