Anyone having experience with using windbg together with recent versions of
VirtualPC or VMWare? I remember VPC was not all that happy with debugging
before Microsoft got hold on it, but not sure about the present state.
I am very “happy” to hear about eventually problems and things not working,
and which of them is best suited at the moment for debugging.
I’ve been using VMWare for a while now with good luck. I’ve even done
back-to-back vmwares - one side for test, the other for kd. Not as
speedy as a real serial port in my experience, but works well. A
friend uses two vmwares on linux, back-to-back, for his windows
development, and it seems to work for him, though it’s not for
everyone.
I have used all three potential products for debugging - VMWare, Virtual
PC, and Virtual Server. All work, although all of them have their
little quirks.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc. http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ola J. Presterud
Sent: Saturday, April 30, 2005 4:03 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg with VPC or VMWARE
Anyone having experience with using windbg together with recent versions
of
VirtualPC or VMWare? I remember VPC was not all that happy with
debugging
before Microsoft got hold on it, but not sure about the present state.
I am very “happy” to hear about eventually problems and things not
working,
and which of them is best suited at the moment for debugging.
I have use windbg with VPC and it works fine. The only problem is if I type
.reboot. I have to stop and restart windbg even with the reset command in
the command line. Also you can’t start windbg until the VPC starts the VM.
Ken
-----Original Message-----
From: Ola J. Presterud [mailto:xxxxx@skanix.com]
Sent: Saturday, April 30, 2005 4:03 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg with VPC or VMWARE
Anyone having experience with using windbg together with recent versions of
VirtualPC or VMWare? I remember VPC was not all that happy with debugging
before Microsoft got hold on it, but not sure about the present state.
I am very “happy” to hear about eventually problems and things not working,
and which of them is best suited at the moment for debugging.
Ken: I am not having any of those issue with VPC 2004. I start WinDbg like
this:
“C:\Program Files\Debugging Tools for Windows\windbg.exe” -k
com:pipe,port=\.\pipe\vpc_com_1,reconnect
Takin
“Ola J. Presterud” wrote in message news:xxxxx@windbg… > Anyone having experience with using windbg together with recent versions > of > VirtualPC or VMWare? I remember VPC was not all that happy with debugging > before Microsoft got hold on it, but not sure about the present state. > > I am very “happy” to hear about eventually problems and things not > working, > and which of them is best suited at the moment for debugging. > > > Ola >
“Ola J. Presterud” wrote in message news:xxxxx@windbg… > Anyone having experience with using windbg together with recent versions > of > VirtualPC or VMWare? I remember VPC was not all that happy with debugging > before Microsoft got hold on it, but not sure about the present state. > > I am very “happy” to hear about eventually problems and things not > working, > and which of them is best suited at the moment for debugging. >
I’ve used WinDbg with VMWare Workstation 4.05 per the directions at http://silverstr.ufies.org/lotr0/windbg-vmware.html. It works some of the time, but getting WinDbg & VMWare in sync is a bit of a challenge; it often takes several restarts of VMWare to get WinDbg to connect to it.
I haven’t tried VPC, nor have I tried using VMWare with the latest version of WinDbg; it may be that the new WinDbg doesn’t have the timing issues I mentioned above.
The latest 4.x version of VMWare and the latest released version of Windbg
work fine. Just start the VMWare VM and stop at the boot.ini. Change the
startup time to -1 so it will not boot automatically. Then start Windbg,
then start the OS. Sometimes it may need a Ctrl+Alt+R to resync and get it
working. I occassionally have to end Windbg and restart it.
“Jeff Henkels” wrote in message news:xxxxx@windbg… > “Ola J. Presterud” wrote in message news:xxxxx@windbg… >> Anyone having experience with using windbg together with recent versions >> of >> VirtualPC or VMWare? I remember VPC was not all that happy with debugging >> before Microsoft got hold on it, but not sure about the present state. >> >> I am very “happy” to hear about eventually problems and things not >> working, >> and which of them is best suited at the moment for debugging. >> > > I’ve used WinDbg with VMWare Workstation 4.05 per the directions at > http://silverstr.ufies.org/lotr0/windbg-vmware.html. It works some of the > time, but getting WinDbg & VMWare in sync is a bit of a challenge; it > often takes several restarts of VMWare to get WinDbg to connect to it. > > I haven’t tried VPC, nor have I tried using VMWare with the latest version > of WinDbg; it may be that the new WinDbg doesn’t have the timing issues I > mentioned above. > >
The latest 4.x version of VMWare and the latest released version of
Windbg
work fine. Just start the VMWare VM and stop at the boot.ini. Change
the
startup time to -1 so it will not boot automatically.
I used VMWare 4.5 and it crashed sometimes when two virtual machines
are connected. But it works fine with VMWare 5.0.
Lei
On 5/3/05, Steve Dispensa wrote: > On May 3, 2005, at 9:13 AM, David J. Craig wrote: > > The latest 4.x version of VMWare and the latest released version of > > Windbg > > work fine. Just start the VMWare VM and stop at the boot.ini. Change > > the > > startup time to -1 so it will not boot automatically. > > Wow, neat trick! I never knew about -1. Thanks. > > -Steve > > > — > You are currently subscribed to windbg as: xxxxx@gmail.com > To unsubscribe send a blank email to xxxxx@lists.osr.com >
I make use of VMWare’s snapshot feature. Have a basic OS (with /debug in
boot.ini and without your driver under test), capture the snapshot, make
sure you revert to snapshot while restarting.
Now all you have to do is start and stop the machine (no reboot
required) and you always start from a clean state. I am using VMWare 4.0
-Udas
Lei Zhang wrote:
I used VMWare 4.5 and it crashed sometimes when two virtual machines
are connected. But it works fine with VMWare 5.0.
Lei
On 5/3/05, Steve Dispensa wrote: > >>On May 3, 2005, at 9:13 AM, David J. Craig wrote: >> >>>The latest 4.x version of VMWare and the latest released version of >>>Windbg >>>work fine. Just start the VMWare VM and stop at the boot.ini. Change >>>the >>>startup time to -1 so it will not boot automatically. >> >>Wow, neat trick! I never knew about -1. Thanks. >> >> -Steve >> >> >>— >>You are currently subscribed to windbg as: xxxxx@gmail.com >>To unsubscribe send a blank email to xxxxx@lists.osr.com >> > >
I made the changed “resets=0” to “reconnect” and it works!
Thanks!
Ken
-----Original Message-----
From: Takin Nili-Esfahani [mailto:xxxxx@hotmail.com]
Sent: Monday, May 02, 2005 2:03 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Windbg with VPC or VMWARE
Ken: I am not having any of those issue with VPC 2004. I start WinDbg like
this:
“C:\Program Files\Debugging Tools for Windows\windbg.exe” -k
com:pipe,port=\.\pipe\vpc_com_1,reconnect
Takin
“Ola J. Presterud” wrote in message news:xxxxx@windbg… > Anyone having experience with using windbg together with recent versions > of > VirtualPC or VMWare? I remember VPC was not all that happy with debugging > before Microsoft got hold on it, but not sure about the present state. > > I am very “happy” to hear about eventually problems and things not > working, > and which of them is best suited at the moment for debugging. > > > Ola >