Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Can’t boot WinXP in VB with debugging enabled
- This topic has 1 reply, 1 voice, and was last updated 13 years, 8 months ago by
Anonymous.
-
AuthorPosts
-
February 6, 2012 at 11:46 #349
Anonymous
ParticipantHello,
I have the following setup:
– Host operating system: Windows 7 x64
– Guest operating system running on the latest VB (4.1.8): Windows XP x86I want to use the guest operating system to debug a driver I’m writing. For this, I want to setup VirtualKD 2.6. I have performed these steps in the following order
1) Install VB
2) Setup Windows XP x86 SP3 + installed all currently available updates
3) On the host OS, I ran VirtualKDSetup.exe
4) Using a shared folder, copied vminstall.exe from the target folder to my guest OS.
5) On the guest OS, I ran vminstall.exe, used standard settings and restarted the guest OS
6) On the host OS, started vmmon64.exe
7) Tried to boot “Microsoft Windows XP Professional [VirtualKD] [debugger enabled]”However, when I try to boot (i.e. step 7), the screen simply goes black and nothing happends (I waited for several minutes). Any ideas where I went wrong?
Thanks
February 6, 2012 at 12:51 #1961Anonymous
ParticipantOK, I guess I should learn to read…
From WinDbg:
Windows XP Kernel Version 2600 UP Free x86 compatible Built by: 2600.xpsp_sp3_gdr.111025-1629 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0 System Uptime: not available Break instruction exception - code 80000003 (first chance) ******************************************************************************* * * * You are seeing this message because you pressed either * * CTRL+C (if you run kd.exe) or, * * CTRL+BREAK (if you run WinDBG), * * on your debugger machine's keyboard. * * * * THIS IS NOT A BUG OR A SYSTEM CRASH * * * * If you did not intend to break into the debugger, press the "g" key, then * * press the "Enter" key now. This message might immediately reappear. If it * * does, press "g" and "Enter" again. * * * *******************************************************************************The solution was to press g followed by Enter which resumed the VM.
-
AuthorPosts
- You must be logged in to reply to this topic.