All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uri Lublin <uril-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: duck-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Is there any way to get Windbg to work with QEMU/KVM?
Date: Thu, 13 Dec 2007 11:35:38 +0200	[thread overview]
Message-ID: <4760FCEA.4040808@qumranet.com> (raw)
In-Reply-To: <OF6F10E645.9C7DF3C6-ONCA2573AF.0023131F-CA2573AF.0024E904-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org>

duck-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org wrote:
> G'day folks.
>
> After blindly trying applying an oldish QEMU patch mentioned here
> (http://www.damogran.de/blog/archives/14-WinDbg-and-QEMU.html) I got ever
> so slightly further, to the point that I reached the Windbg command prompt
> and could enter commands (e.g. '.dl'). All I got back were sporadic errors
> such as "couldn't find KTHREAD entry at blah" and other "it's nae workin'
> cap'n" sort of messages.
>
> Can it be made to work? Others seem to have claimed to have done it. Seems
> I am so near but so far!
>   
Try hacking qemu/qemu-kvm.c:pre_kvm_run() with something like that:

+#if 1
+#define MIN_CYCLE_COUNT 100
+		{
+                    static int cycle_count;
+		  
+		    if (++cycle_count > MIN_CYCLE_COUNT) {
+                        cycle_count = 0;
+                        return 1;
+                    }
+		}
+#endif



-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

      parent reply	other threads:[~2007-12-13  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12  6:43 Is there any way to get Windbg to work with QEMU/KVM? duck-j34lQMj1tz/QT0dZR+AlfA
     [not found] ` <OF6F10E645.9C7DF3C6-ONCA2573AF.0023131F-CA2573AF.0024E904-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org>
2007-12-12 11:34   ` Dor Laor
     [not found]     ` <475FC72C.7070506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13  1:28       ` duck-j34lQMj1tz/QT0dZR+AlfA
     [not found]         ` <OFB934B8E7.F5AD5E7A-ONCA2573B0.0007F3A1-CA2573B0.00081680-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org>
2007-12-13  9:14           ` Dor Laor
2007-12-13  9:35   ` Uri Lublin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4760FCEA.4040808@qumranet.com \
    --to=uril-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=duck-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.