Re: Using KVM for Windows kernel debugging

[Vadim Rozenfeld <vrozenfe@redhat.com>]

On 08/19/2009 01:31 AM, duck wrote:
> I have never got this to work reliably. Occasionally I can get as far as
> making a debugger connection at boot-time, IIRC, but have never managed to
> use the deugger at all. You always seem to end up in some
> debugger-debuggee deadlock.
>    
It works.
However, getting into debug session is real pain in the neck.
Especially for the first time.
> I suspect that the serial link simulation is imperfect enough (lost
> interrupts and thus lost characters?) that you are out of luck for
> serial-link-based remote debugging, even though userland serial comms,
> e.g. using Hyperterm, seem to work fine.
>
> I was able to get debugging working, a year or two ago, under QEMU using
> the MIN_CYCLE_COUNT patch (I made a command line option called '-mcc' to
> allow this to be tuned at run-time) but IIRC this patch is irrelevant when
> KVM is used.
>
> Can anyone suggest a KVM patch which might help, even if it slows the
> debuggee VM down?
>
> Pity SoftICE got killed off :-)
>
> You could try http://www.sysersoft.com/ for a one-PC Windows kernel
> debugging solution. Seems to be a small Beijing software house which just
> sells on-line. Their product is not free, though there is a free trial.
> (I haven't tried it under KVM, though they advertise that it works
> under VxWxxx [censored]).
>    
Maybe we can use vm kd extensions project 
(http://www.nynaeve.net/?page_id=168)
as a starting point and fit it into kvm. AFAIK, VmWare and Virtual Box 
have done it already.
>    
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>