Kernel debugging on one machine using Virtual PC 2004 SP1 & Windows XP

You no longer need to buy another machine or a copy of SoftIce to do full kernel debugging using two machines. This is a good setup for learning & hobby projects.

Setup target VM
  1. Go to My Computer -> Properties -> Advanced -> Settings (Startup and Recovery) -> Edit
  2. Add '/DEBUG /DEBUGPORT=COM1' to the end of the settings in the boot file.

Setup host machine.

  1. Edit settings for VM, configure COM1 to use a named pipe. Eg. "bkslash-bkslash-dot-\pipe\debug"
  2. Start KD by running "kd -y SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols -k com:pipe,port=\\.\pipe\debug,resets=0,reconnect" or equivalent command.
  3. Restart target VM, you should see a message in KD saying "Connected to Windows XP..."

Reference: http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/20/482413.aspx

Comments

Anonymous said…
The commad has "resets=o" . It should be 0.
7:28 PM
Post a Comment

Popular posts from this blog

.NET Decompiler aka Disassembler aka Reflector This is the best .NET decompiler around and it is free. http://www.aisto.com/roeder/dotnet/ This will decompile .NET bytecode(including the base class library) into more than one language(C#, VB, J# etc).
Read more

Google Appengine

It was good while it lasted, Google AppEngine gave developers an easy way to create web applications without worrying about scaling it or being a sysadmin. There were numerous startups that built their products on Google Appengine. Even after beta, there was a fairly large free quota that made it a reasonable choice. But, the current pricing seems a bit ridiculous for those who are looking for a free or cheap solution or for those enjoyed the initial quotas. Perhaps, we were spoiled and Google’s goal is to get rid of free-riders which is not exactly evil from Google’s perspective. So, it is 2012 and welcome to reality since Google can’t maintain those quotas forever and the current free quotas are intended to only test your application before you go live. If for some strange reason, your application becomes popular and gets more than 1,000 users, you would end up scrambling for an alternate solution since you will find yourself paying through the nose. The quota system is complica
Read more

Did you ever have to analyze large log files before?

Well, I recently had to analyze a large log based dataset and decided to try out the ELK stack . Introduction: Please see this intro if you are not familiar with ELK, the rest of the blog assumes you know what they are. eg. elastic server, logstash & kibana. It is a popular server side tool to index, search & graph a large collection of logs or similar structured/unstructured data. This blog post mainly talks about my experience setting up this well known stack & the unexpected things learnt during the process. Goal : "How do I enable rich filtering & analysis on the large set of product logs beyond some simple scripting?" I thought I just had to upload a few log files to the server & then have some awesome graphs appear almost magically out of the box! Servers : "How do I get a server up and running?" There is a free trial for cloud based elastic stack. I signed up and got a 14 day free trial with 4 instance running on Google Clo
Read more