VMware Communities : Thread List - Replay-Based Debugging

Connecting to x64 target

kernelgrunt — Fri, 06 Nov 2009 03:41:52 GMT

I am trying to hook up to a Win7 x64 boot in VMWare WS 6.5 using host platform XP x64. GNU gdb 6.3 from MinGW. Settings in vmx file:

bios.bootDelay = "3000"
debugStub.hideBreakpoints = "TRUE"
#debugStub.listen.guest32 = "TRUE"
#debugStub.listen.guest32.remote = "TRUE"
#monitor.debugOnStartGuest32 = "TRUE"
debugStub.listen.guest64 = "TRUE"
debugStub.listen.guest64.remote = "TRUE"

From gdb command-line:

(gdb) set architecture i386:x86-64
The target architecture is assumed to be i386:x86-64
(gdb) target remote localhost:8864
Remote debugging using localhost:8864
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout

If I use the 32-bit settings I can connect just fine at boot and step all the way until long mode is enabled.

Using the 64-bit settings I have tried connecting at boot, and I have tried connecting after I know 64-bit instructions are executing. Same behavior...no luck. Am I doing something obviously wrong?

Host could not participate in VCE after failed CPU replaced

Jawdat — Thu, 05 Nov 2009 11:48:47 GMT

This is an odd situation that we encounter which I would like to share in order to 1-shed some more light over, hopefully and 2- so it may be of help to someone in the same situation.

Couple of weeks ago we had a HW failure on one of the HP BL680c G5 blades where it just died, lights are on but no one home kind a thing. HP came in and with a new mobo, as they always do, replaced but still no joy, the savvey engineer then discovered that it is not one but two out of the four cpus are faulty. Ordered and replaced them and the host came back to life. Fine but for the life of me I could not get the 6 hosts cluster to recognise it as a VT enabled host although made sure the VT and the 'No-Execute Memory Protection' both are enabled in the BIOS. As a result this lone host would not vmotion to or from without the warning message about the CPU bit.

The only way to get the cluster EVC enabled again and be able to vmotion normally was to create a new cluster with EVC enabled and migrate all the hosts and VMs to it. When I did that the host that had a problem joined ok and was vmotioning as normal. I had manually recreate all the rules I had on the old cluster which was deleted and the new one renamed.

Now had anyone been in the same boat and what did they do if different.

Thank you

Debugging kernel shutdown in a linux guest OS

DAJames — Mon, 03 Aug 2009 17:22:25 GMT

I'm trying to investigate the shutdown of a linux kernel. I'm using a (slightly hacked) Ubuntu Hardy 32-bit system running under VMWare Workstation 6.5 on a 64-bit Windows Vista Host (Vista x64 is the standard environment for all developers here).

I've read VMWare provides some debugging support, but I have been unable to find any hard information on the extent of that support, and how to set it up. One of the difficulties I face is that I need to be able to debug the kernel's shutdown/restart sequence, which involves (or can involve, depending on the details of the platform) switching briefly back to real mode ... as I understand it tools like kdb and kgdb aren't able to debug across mode switches (they're protect-mode kernel tools)

I'm hoping that VMWare itself can use its virtualization of the hardware to provide some debugging support (is this how replay-based debugging works?) -- but how?

Cheers,
Daniel.

Howto : Debugging Windows Xp host and Linux VM guest or Linux VM Guest to Linux VM GUest

ganzorig85 — Mon, 12 Oct 2009 08:29:45 GMT

Hello

Is there any instruction that How to Debugging Windows Xp host and Linux VM guest. Now I am using Ubuntu 9.04 with kernel 2.6.31. But i can't find any appropriate kernel debugger version for Linux 2.6.31 like kgdb.

Please help me

LVM 1355 - One or more devices not found

rbnunes — Tue, 01 Jul 2008 00:23:22 GMT

Hello everyboy

someone already seen the error below ?

(LVM 1355 One or more devices not found (file system SAN03,472b8004-bc3671ce-d5cc-00145e7ba2c6) (0:03:20:52.310 cpu7:1061)

I lost my datastore (SAN03).

thanks,

Rafael Nunes

Loading symbols for Linux user processes

rruvinsk — Thu, 08 Oct 2009 21:44:14 GMT

Hello,

I'm trying to debug a multi-threaded application running inside a VM, both live and in replay mode. The VM is running RHEL 5, kernel 2.6.18-164-2-1. I've tried running the remote gdb on the host for this VM (also a RHEL 5 machine) as well as a Ubuntu 8.04 box. The results in both cases were identical. I'm running VMWare Workstation 6.5.3.

I can attach to the VM and, after issuing the "monitor linuxoffsets" command, see all processes. I can switch between them using the 'thread' command. However, I can't see backtraces. I suspect this is because the symbols aren't being loaded properly.

If I try to debug a live application, gdb makes no attempt to load the symbols at all, no matter what I do.

If I try to debug a replay session, gdb does attempt to load the symbols after I issue the "target remote" command. However, it looks for them on the machine where gdb is running, not on the guest being debugged. I have tried copying all required libraries to the machine where gdb is running and setting the solib-search-path and solib-absolute-prefix options. If I do that, gdb claims to successfully load all the symbols from the libraries, but the stacks are for the most part mangled. If I try to set breakpoints, they never get triggered.

I was wondering what is the correct procedure to get this to work. The User Manual has instructions for some of this, but they seem to be for Windows. gdb and Linux aren't at all mentioned.

Thanks,

Ray

Host CPU rqmts for Replay?

ohaya — Sun, 07 Jun 2009 03:11:21 GMT

Hi,

I am running VMware Workstation 6.5.2 under Win2K3 on a system that has an AMD Athlon 64 X2 5200.

I've enabled Replay in the settings, but when I click Replay->Record, I get a popup:

"Record/Replay is not supported on your processor."

Is it not possible to get Record/Replay to work with this OS/CPU combination?

Thanks,

Jim

GDB debug stub does not respond correctly to "T" thread alive queries...

visbrero — Thu, 10 Sep 2009 09:16:56 GMT

I have been trying to attach recent builds of gdb (archer's python branch: http://sourceware.org/gdb/wiki/PythonGdb) to the VMware debug stub. I've found 2 apparent gdb bugs and 1 that appears to be an issue with the VMware stub.

The gdb bugs can be found here, for completeness:

http://sourceware.org/ml/archer/2009-q3/msg00188.html

http://sourceware.org/ml/archer/2009-q3/msg00198.html

With those bugs fixed, I can perform an "info threads" after providing the linuxoffsets and get a list of all the live threads. However, attempting to switch to the thread via "thread GDBTHREADNUMBER" fails because when gdb asks about the thread, VMware's response makes it think the thread is dead. This causes it to not switch to the thread. For example, if the GDB thread number is 179 and the underlying thread id is 3008, "thread 179" results in a payload of "Tbc0". VMware responds with "E00" which makes gdb think the thread is dead, as per the spec on the command.

If I modify gdb so that remote_thread_alive in remote.c always returns true (and does not issue the command), things work as they used to work in my older setup.

I am using VMware workstation 6.5.3 with up-to-date Ubuntu 9.04 i386 guests on an Ubuntu 9.04amd64 host. In my old setup I used the gdb debugger that shipped with Ubuntu 9.04 with Workstation 6.5.2 (or maybe 6.5.1?). The system gdb no longer works, so I presume there was an update to gdb on 9.04 that broke things, but I have not investigated heavily since I'd rather use a modern gdb works (and can be scripted with python!) than figure out what ancient version works.

My idea of what works is: Attach with archer-gdb without having specified an executable. Tell it about the linux offsets, do "info threads", find the first thread in the process I care about, switch to that thread. Detach and quit. Attach with archer-gdb having specified an executable. Things are now in a state where I have a valid backtrace and gdb's understanding of the executable's layout in memory appears correct.

How

mayurdeolasee — Tue, 25 Aug 2009 11:54:02 GMT

How does the system work?

Debugging after serious error in client VM

DAJames — Tue, 11 Aug 2009 14:48:01 GMT

I have a problem with some code that runs in real mode from a linux kernel. At some point after my code is entered I get a pop-up n VMware saying:

*** Virtual machine kernel stack fault (hardware reset) ***
(snip a few lines of explanation)
Press OK to reboot thevirtual machine of Cancel to shut it down.

What I'd really like to do, though, is to debug it.

I have remote debugging of the kernel running, connected to gdb in another VM, but at the time that I get the stack fault in the debuggee VMware won't even let me switch to the debugging VM to try to break in with gdb. It's not clear whether this isbecause of a limitation in the way VMware is implemented, or just a result of the fact that the dialog box VMware displays is modal?
Is there some way to make the stack fault generate a breakpoint instead of a pop-up and a reset when the VM in which it occurs is being debugged?

If not, can I make that a feature request, please?

Cannot access memory at address when trying to set a breakpoint

aldep — Wed, 08 Jul 2009 20:53:47 GMT

Hi,

I am trying to debug Linux guest kernel on a Windows host. I am using MingW gdb and VMWare workstation 6.5.2 (actually the same error happens with VMWare server).

I added debugStub.listen.guest32=1 to the vmx file and was able to attach gdb on port 8832 (as described here: http://stackframe.blogspot.com/2007/04/debugging-linux-kernels-with.html).

I can see a stack trace, I can interrupt guest execution with Ctrl+C.

But when I try to put a break point at any function, I get erro, e.g.,

(gdb) b sys_open
Cannot access memory at address 0x80284c59

The same error happens when I try to view contents of the variable:

(gdb) p init_task
Cannot access memory at address 0x80a0c700

Could you please tell me how to fix this strange behavior?

Thank you,

Alex

P.S. I am not using "replay debugging" feature at all, but this discussion seems to be the most relevant place for debugging question

debug rhel

hxl — Fri, 12 Jun 2009 13:46:14 GMT

hi, i have already installed the RHEL 5 and the correct kernel symbol on my vmware.

but i can not find the vmlinuz with kernel symbol.

can any one tell me how to find that.

or give me some information about the kernel symbol.

"source-less" debugging with Replay?

ohaya — Sun, 31 May 2009 17:04:33 GMT

Hi,

I'm new to VMware workstation, and I have a question regarding the Replay capability.

I understand that Replay can be used with VS for debugging C/C++ programs, but that assumes that you have have the source for the original program. Can Replay be used in situations where you do not have the original source code?

Thanks,

Jim

Memory watchpoints emulation ?

J.F.V — Wed, 14 May 2008 14:31:19 GMT

Hello !

It seems like hardware watchpoints are unsupported in vmware workstation < 6.0.3

Is this a planed feature ?

I have enabled hiddenBreakpoints in the configuration file but the gdb client keeps
receiving vmware errors as soon as a hwbp is set and the debugged program is
continued.

The context of my problem is as follow: I am running an OS-less image starting
execution at 0x7c00. Another image is then overwriting the first one, at this
same address, and starts execution at 0x7XXX (e.g. a breakpoint on 0x7c00 is not
enough to catch the start of the new image).

Given that the code is many thousands assembly instr, it would have been just easy
to set a hwbp on 0x7c00 and see when the first image is overwritten.

How can vmware-ws help me to do that ?

Thanks

-JFV

Getting started: kernel symbols

kevoreilly — Mon, 07 Apr 2008 13:30:32 GMT

I have recently heard about the new debugging functionality that has been added to WS6, and I have been trying to get myself up and running remote debugging a linux machine.

However, having read Slava's blog and searched the forum, I am still unsure of one aspect of the setup of remote debugging; specifically kernel symbols. Perhaps my question betrays my lack of understanding or knowledge, but I hope that I am not asking a stupid question, and that others might find the answer helpful.

Basically the question is simple; from where does one obtain the kernel symbols in order to do this, and how exactly are they set up?

I appreciate this may be distro-specific, and the answer might be 'go to your distro's site and find them there somewhere'. I am using Ubuntu, and have used Synaptic to install 'linux-image-debug-2.6.22-14-386' (which matches in version number to the kernel on my 7.10 install) but whether this is the right thing or not I don't know.

Now if I do find the right kernel-with-symbols file that matches the kernel I am running in my virtual Ubuntu installation, do I then have to copy this to the host machine in order to pass to gdb when remote-debugging (as in: "(gdb) file vmlinux-2.4.21-27.EL.debug")? Now this may be obvious, but I can't see it mentioned anywhere.

So I am looking for a wee bit more information on how to get this all up and running, and would really appreciate any help that someone might be able to offer.

Cheers, Kev

Debugging a recording made after the application has started?

hajokirchhoff — Fri, 24 Apr 2009 10:04:45 GMT

Hi all, hello VMWare Team,
thanks a lot for replay-based debugging. This is a really, really wonderful feature.

Here is the question:

Host: Vista x64 on an Intel i7 with 6GB RAM with nVidia Graphics. Visual Studio 2008.
Guest: Windows XP 512MB

My QA team is creating recordings for debugging manually, using VMWorkstation. There are two possible sequences to do so:

1. Start the recording then
2. Start the application

which means the 'CreateProcess' event is contained in the recording, or

1. Start the application then
2. Start the recording.

which means, the 'CreateProcess' event is not contained in the recording. The recording starts with my application already running.

I have not managed to make replay-debugging work with the second order of events. When I try to debug that recording, it will start playback with my application running, but the VMWare Debug Plugin never finds the process inside the recording.

Am I right in my assumption that the VMWare Debug Plugin looks for the starting of my application inside the recording? And so I cannot debug applications that have already started when the recording begins?

Or is there something I am missing?

My QA team wants to use this feature to report bugs. Moving around a couple of GB is pretty cumbersome and sometimes they would like to start recording only later, some time into their testing session, even if that might mean we're possibly missing the cause of a bug.

BTW, I watched your talk on Google Talk and someone from the audience suggested a trigger and pre-trigger recording, where the system would on a failed testcase created a recording of the last 'n' minutes leading up to the failure. I really can't wait to get my hands on this, it would be extremely helpful for us.

A little more on our setup. I am working with Windows almost exlusively, but we also have several linux guys. We write software with many custom protocols with external hardware connected via ethernet. We are also desiging the hardware. I am sure you can imagine how much help this would be to us, not just for debugging the software on the PC but for debugging our hardware as well.

Best regards

Hajo

debugStub.listen.guest64.remote = 'TRUE' doesn't open a socket for remote connections

kirktrue — Thu, 09 Apr 2009 08:25:28 GMT

Hi,

I'm running a 64-bit Fedora guest on Fusion 2.0.3 and have added the following to my *.vmx file:

debugStub.listen.guest64 = 'TRUE'
debugStub.listen.guest64.remote = 'TRUE'

It appears VMware is picking this up as a see this in the vmware.log:

Apr 09 01:05:47.540: vmx| DICT debugStub.listen.guest64 = TRUE
Apr 09 01:05:47.540: vmx| DICT debugStub.listen.guest64.remote = TRUE

A little further down in the log I see this:

Apr 09 01:05:47.596: vmx| SOCKET creating new listening socket on port 8864
Apr 09 01:05:47.596: vmx| VMware Fusion is listening for debug connection on port 8864.
Apr 09 01:05:47.596: vmx| target remote localhost:8864

I was able to connect to the guest from the host via gdb, but I cannot connect via gdb from another machine. I checked netstat on the host, and I don't see port 8864 open at all. According to the MacOS X Security preference pane, my firewall is completely disabled.

Any ideas?

Thanks.

Debugging D programs

CyberShadow — Mon, 23 Mar 2009 17:39:46 GMT

Hello,

I'm trying to debug a hard-to-reproduce memory corruption problem in a D program. Like C++, D is a statically-typed language meant for compilation, and the reference Digital Mars compiler produces stand-alone executables. The compiler generates debugging information readable by Visual Studio, so by opening the executable in VS as a project, it's possible to debug a D program at source level without any additional extensions. However, when opening an executable as a project the VMware extension produces the following errors (from the log file):

23.03.2009 12:25:29: VMware Virtual Debugger loaded successfully.
23.03.2009 12:25:51: ERROR: pProject->get_Properties(&pProps)
23.03.2009 12:25:51: An error occurred in .\Connect.cpp at line 2132.
23.03.2009 12:25:51: An error has occurred in the application. For more information please see the log file. Its path is listed in the About box.
23.03.2009 12:25:51: ERROR: pProject->get_Properties(&pProps)
23.03.2009 12:25:51: An error occurred in .\Connect.cpp at line 2132.
23.03.2009 12:25:51: An error has occurred in the application. For more information please see the log file. Its path is listed in the About box.

Is it somehow possible to use VMware's replay-based debugging in this situation? Note that I've already tried many other debugging techniques (including interfacing with Valgrind and even writing my own memory debugger for D), so I would even go as far as writing my own debugger front-end for VMware's replay-based debugging interface. Which leads me to my second question: is there a documented way to send debugging commands to VMware, such as controlling replay blayback, setting memory breakpoints and reading data from process memory?

Thanks,
--Vladimir

trace expansion on release version

fireboo2009 — Thu, 05 Mar 2009 11:54:48 GMT

Is trace expansion feature available on release versions of VmWare Workstation? On debug version 6.0.1 after modifying preferences file pref.replay.enableTrace="TRUE" everything work: Trace button appears in Replay window, and gzip file (with trace text representation) generates. Debug version 6.5 i did not yet tested.

On release version - 6.0.1 and 6.5 : on Linux host: after modifying preferences pref.replay.enableTrace="TRUE" - Trace button appears, but pressing it has no effect - gzip file not generated.

VmWare Workstation 6.5 on MS Windows host: pressing Trace button while replaying leads to hangup.

Problemm remote debug linux kernel in two VMWare.

mia1978 — Tue, 24 Feb 2009 14:03:14 GMT

The problem, is 2 VMWare with an identical kernel, at loading of the
module of a kernel, it is loaded to different addresses in different
kernels, how it to correct? Thanks.

Debugging linux kernel (inside vmware) from Mac OSX

jpb000 — Thu, 18 Dec 2008 23:15:09 GMT

Hi,

I recently read http://www1.cs.columbia.edu/~carlosrene/?p=63

how you can basically debug a Linux kernel (inside vm) from native.

I have a Mac OSX and I'd like to debug a Linux kernel that's running in my vmware fusion.

How would that be possible? GDB remote works, but I also would like to import symbols from the kernel to my mac osx's GDB.

Please advise.

Thnks

Using KDB under Vmware

NigelCunningham — Tue, 27 Jan 2009 11:42:28 GMT

Hi all.

I'm trying to use KDB under VMware, but the keyboard doesn't respond after I press the break key. Is there a workaround available?

Regards,

Nigel

New bug when using remote kernel debugging

J.F.V — Sat, 24 Jan 2009 18:41:38 GMT

Hello all,

There is an annoying bug in remote debugging which is the following:

When disconnecting from the debugger on the client side, the vmware
wont restart but it will be impossible to connect again to the vmware-gdbserver.

This is quite annoying as we have to restart the VM after each quit of the client-side
debugger. Sometimes when the client-side debugger crashes, it makes kernel debugging
using vmware much more painful ;P

Would it be possible to patch it in the next WS ?

Thanks!!

-JFV

Bugs when using the remote debugging

camoroz0 — Sat, 10 Jan 2009 12:34:51 GMT

Hi there,

I noticed 3 bugs when using the VM with the remote debugging enabled. In my vmx, I have

debugStub.listen.guest32 = "TRUE"
debugStub.listen.guest32.remote = "TRUE"
monitor.debugOnStartGuest32 = "TRUE"
debugStub.hideBreakpoints= "TRUE"

Basically, I noticed:

Reading very big chunks of memory make the VM "panic loop" : Unexpected signal: 11. Loop on signal 11 -- tid 3144 at 0x081112a4. Try sending $m0,1000000#1a you will see the bug.
Only ~32 breakpoints available. We reached this limit when debugging.
When multiple guests are running and we try to debug one of them, the "non-debugged" ones freeze. I saw this when I had a Gentoo running in a Guest and I was debugging my boot loader.

Cheers,

PS: core file is too big to be added here.

linuxoffsets?

bramp — Wed, 24 Dec 2008 23:00:23 GMT

Hi,
I've been debugging FreeBSD from a Linux host. Now from my understanding the gdb "monitor linuxoffsets" is a non-standard feature which VMWare has added.

Now I wanted to get a better understanding of this. By setting this command, and therefore giving VMWare a bunch of offsets, does this allow VMWare to know all about the threads/processes within the OS, allowing gdb to infer more information about what it is debugging?

I'm however trying to debug a combination of the kernel and user-level application running on FreeBSD. It would therefore be very useful for a similar feature so that my gdb can more easily determine what module/process/thread I'm executing, etc.

So, does anyone know how I could abuse the linuxoffsets command to work for FreeBSD? or another way I can get gdb to figure out all the information itself?

thanks
Andrew

Debugging xnu-1228.9.59 using Fusion GDB server --> Can't get breakpoints to break

buzdelabuz2 — Tue, 30 Dec 2008 22:09:50 GMT

Hi,

I have tried the following:

1) Compile xnu-1228.9.59 DEBUG i386 and replace the mach_kernel file on OSX server running into Fusion
2) Setup the Fusion GDB server according to the information in the power guide (debugStub.listen.guest32=1)
3) Connect with GDB to localhost:8832

Everything is looking great up to that point. I can dump thread stacks, next, inspect/change anything I like ...
The setting of breakpoints seems to be functionning, except that the debugger never gets called when hitting them.
As a matter of fact, I don't seem to be able to break into the debugger at all after I issue a "continue" to the debugger.

It returns the control to the system, but I can never break again.

Does anybody know why the breakpoints are being set or why they aren't triggering the debugStub ?

Thanks in advance for your time.

2 questions - choosing a CPU to examine and reversing execution

212okins — Fri, 26 Dec 2008 20:49:39 GMT

Great work, guys from Vmware, the debugger is very useful indeed.
It looks like the remote monitor doesn't allow me to set the CPU that I want to examine.
When I type "bt" in gdb (version=6.8-debian) I see a stack trace that shows the state
of CPU 0 only but I'd like to check also what CPU 1 is doing.
Replaying is not enabled for my guest linux OS for now, as you can infer.
Why is replaying not supported in 2 CPU guest configurations?

Also I am wondering if the monitor can be augmented to work in conjunction with
the replay feature such that I can debug backward in time, for instance the
crash below is probably a manifestation of corruption that occurred some time in
the past. I'd like to be able to type "monitor reverse <something>" and observe the state of
the system as the effects of each instruction (or sets of instructions) get undone.

current crash I am investigating, snipped

#5 0xc02d4817 in error_code () at arch/i386/kernel/entry.S:592
#6 0xddebe870 in ?? ()
#7 0xc0123790 in profile_tick (type=0, regs=0xc02d2a10)
at kernel/profile.c:199
#8 0xc011845a in smp_apic_timer_interrupt (regs=
{ebx = -283400512, ecx = 4, edx = 170, esi = -2, edi = 4, ebp = 170, eax = -330820196, xds = 123, xes = 123, orig_eax = -17, eip = -1070781936, xcs = 96, eflags = 2097666, esp = 170, xss = -266306225}) at arch/i386/kernel/apic.c:1080
#9 0xc02d477a in apic_timer_interrupt ()
at include/asm-i386/mach-default/entry_arch.h:26

Setting registers is not supported ?

camoroz0 — Wed, 26 Nov 2008 22:17:15 GMT

Hi,

when using our debugger, we noticed that setting a register was not allowed when monitor.debugOnStartGuest32 = "TRUE" was set. Basically, the client sends a <gREGISTERS> or the equivalent Px=laddr, where x is the number of the register. None of these commands seems to be working, since we get an error " E00" from the server. If we disable monitor.debugOnStartGuest32 = "TRUE" everything is fine, but we are not able to break on 0x7c00...

Is it a known bug ? Is it gonna be supported in the future ? It'd be nice to have both features .

Thanks,

reverting to snapshot stops syncing

tstakland — Tue, 25 Nov 2008 18:48:12 GMT

I am setting up a testing enviroment with Novell GMS servers that talk to Novell Groupwise servers. Once I get a specific setup up and syncing together, I snapshot both boxes.

When I want to go back to that specific configuration to run some tests, the boxes don't sync any more. For example, I install GMS on one virtual machine and GW ver. 7 on another. After everything is working, I snapshot the GW machine, upgrade it from 7 to 8, and I get it working. I then revert to the snapshot with ver. 7, and the system no longer syncs with GMS.

What's causing this to happen?

configure vm network setting in sabayon linux

entc — Wed, 19 Nov 2008 05:06:10 GMT

hi can some one tell me how to configure bridge adapter in sabayon linux?

User-mode debugging via GDB stub on Windows

tdullien — Mon, 03 Nov 2008 15:23:29 GMT

Hey all,

we're using VMWare to debug stuff in a no-source situation, and we can use the GDB agent quite nicely to do binary-only debugging of kernel drivers etc. -- but we're having trouble dealing with user-mode debugging. Since VMWare doesn't appear to know much about Windows processes etc., how can we set breakpoints into a particular userspace process ?

Cheers,

Thomas Dullien

Zynamics GmbH

Support for Windows kernel mode debugging?

mmcculligh — Mon, 22 Sep 2008 20:14:39 GMT

Is there any support for debugging kernel mode drivers on Windows? I would assume this would be some kind of integration with WinDbg.

Logs eval

PabloCalvo — Wed, 29 Oct 2008 18:56:53 GMT

Can someone send me logs from ESX?

I'm installing splunk software to evaluate.

Replay debugging and Visual Studio 2003?

bodzio131 — Tue, 14 Oct 2008 10:21:04 GMT

Hi, is there any possibility to use vmware replay debugging with visual studio 2003?

Regards,
Bogdan

Problems debugging a Java app in a guest Xp froma a Host Xp wit VMWorksattion 6.5 beta2 1100678

VitaliSoft — Thu, 18 Sep 2008 07:42:48 GMT

Hi everybody, I'm trying to debug a java application trough Eclipse plug-in in a Xp virtual machine.

That's the problem: only very few times I was able to run the application in guest Xp starting from Eclipse in host XP.
I was never able to attach the eclipse debugger to the java app already running on guest system.

Any suggestion?

My final scope is to be able to debug an application during the reply of a recoded crash.

Thanks in advance

Roberto Vitali

LVM: 1355 One or more PEs inaccessible

Cyruse — Wed, 23 Jan 2008 14:05:50 GMT

Hi,

First off this is my first post in the communities so I apologize if this is in the wrong place. In a nutshell we have a three node cluster on a san, the san is divided into 3 data stores. A couple of days ago in the Tasks & Events we started recieving the following warning.

Issue detected on esx01.massillon.sparcc.org in Massillon City Schools LVM: 1355: One or more PEs inaccessible (files system Datastore3, 4692a2b0-0a1acdcf-bd38-0019bbe66186) (4:19:52:59.136 cpu2:1033)

I've done a fair but of searching in the knowledge base and on google and really haven't found anything on this. If any one could point me in the direction of some docs on this or offer some explanation it would be appreciated.

Thanks,

Cyrus

Interpreting an execution trace file of the recording

Jerome2 — Fri, 22 Aug 2008 14:16:42 GMT

I created an execution trace file of a recording and I am having difficulties interpreting its contents. I am attempting to trace an Executable (I.E.) to assist me in determining the cause of a page load failure. The content of the .gz that is created is illegible in its current format. Is there another utility that can be used to interpret /format the content of the .gz file?

about muti-guest os debug

yuanbor — Mon, 23 Jun 2008 14:29:42 GMT

hi,all

There are 2 guest linux os in one host machine. I can debug one guest perfectly if another guest is cloesed. But if both of them is running , there are some troubles. I find some answers to this question : lookup vmware.log to find the port(8864 or 8865) .

However, the port number is not always the same. Guest1 not always has port 8864 ,while guest2 not always has port 8865. So, what's my requirement is a config item to specify the connection port, is anywhere has one ?

Question about vmware coredump / vmw-gdb stub

J.F.V — Tue, 03 Jun 2008 15:19:19 GMT

Hello all

Let me first make precise that I am using vmware workstation 6.0.3 but this issue also
arises on vmware-ws 6.5b.

It happens that I have a strange behavior when debugging a subtle piece of code that does
the following:

switch back from protected mode to real mode
call some BIOS API
switch back from real mode to protected mode
continue the original program

When stepping this code in vmware, it works very well and never crash. However, when
executing this code without stepping, vmware crashes with a stack fault, and without
calling the BIOS routine properly.

My questions are as follow:

is there anyway to know where the code crash using the vmware coredump file (or another debug option ?)

is it possible that debugging into vmware change rights on memory (just like debugging a userland application

with gdb usually does). More generally, where can I get more information about the vmware gdb stub ?

is there any other known issue (vmware or other) about executing such code, that would explain the difference

of results between debugging into vmware and just letting it run ?

Thanks

JFV

Debugging a PXE image

J.F.V — Thu, 08 May 2008 16:28:12 GMT

Hello !

I just installed vmware workstation 6.0.3 evaluation and I want to debug an image executing in real-mode that is sent to the guest machine via PXE. I am using a dhcp server on the host machine and the guest machine boots correctly using PXE on the image I desire.

My wish now is to debug starting at address 0x7c00 (MBR). Thus I enabled debugging options in the .vxm file for that particular VM:

debugStub.listen.guest32=true
debugStub.listen.guest32.remote=true
debugStub.hideBreakpoints=true

The host machine has IP 192.168.1.2 and the guest IP get allocated via DHCP the IP 192.168.1.106. However I am not managing to do any debugging operation on the guest image. I run gdb on the host side and execute:

$ gdb
GNU gdb 6.6-debian
(gdb) file memtest
Reading symbols from memtest...(no debugging symbols found)...done.
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) target remote 192.168.1.106:8832
192.168.1.106:8832: Connection timed out.
(gdb)

I tried to use port 8832, 8833, etc, I tried to execute the "target remote" command at different moment of the guest boot (before, while, after booting), it always results in the same error messages "connection timed out" or "no route to host". I tried with vmnet interface up, then vmnet interface down, with the same unlucky result.

Given that I am not booting linux or any other kernel, I have put the guest type to "Other". This has the bad side effect to refuse any replay debugging as well (which I would have liked to try as well)

Any hint ?

Thanks very much

-JFV

Transfer Content

lakshmisystems — Fri, 18 Apr 2008 10:15:01 GMT

I am new to VMWare... Learner...Trying out.

I created a VMServer with FreeBSD as O/S. I created a virtual HDD and virtual CD Drive. I booted from virtual CD Drive using a ISO file. Made the virtual HDD as Bootable one. Then removed CD Drive and was able to boot successfully VM from virtual HDD.

Now my requirement is, I want to transfer the contents of Bootable Harddisk to another Physical Hard Disk or USB. This USB or Physical Hard Disk, I want to use to boot a machine.

Is this possible? If possible how to do? Help / Hint / Link - Anything is welcome.

Record and replay scope question

rini — Tue, 15 Apr 2008 15:44:05 GMT

Does record and replay work on multi-core machines or else only on uniprocessors?

What kind of bugs can it handle (concurrency, memory corruptions etc.)?

What is the recording overhead?

Catching linux at the very __start

djm1021 — Tue, 11 Dec 2007 19:49:24 GMT

One of the cool features of the new debugging features in WS 6.0 is the ability to debug a linux kernel, see:

http://stackframe.blogspot.com/2007/04/debugging-linux-kernels-with.html

I am trying to do just that but I would like to debug REALLY from the very beginning of Linux boot, at __start, which is the very first instruction that Linux executes. Using gdb, I am able to interrupt when the grub bootloader is loading Linux into memory and I am able to interrupt after Linux has started booting, but I haven't found a way to catch the point where grub has finished loading the Linux kernel and hands over control to Linux (by executing a longjmp I think).

Has anyone been able to do this?

More info from my efforts:

Setting a breakpoint at address doesn't work because the kernel has not been loaded yet so gdb can't write to that address. Apparently hardware watchpoints don't work from gdb to VMware, I assume because VMware doesn't expose the x86 debug registers. I tried single-stepping many times (e.g. "ni 10000000") but somewhere in the grub loading process, something happens and the command never completes. I tried "watch $eip==+address+" and that never completes either. However, "continue" gets past whatever point the single-stepping mechanisms doesn't get past and gets well into the kernel initialization process before I can interrupt it.

I know that when a guest is idle, VMware starts saving away the guest data so as to accelerate a future "Suspend" operation and avoid unnecessarily using host CPU cycles. I'm guessing that the problem I am seeing is that while gdb is doing a massive number of single-steps, VMware is under the impression that it might be a good time to start saving. Is there some way to disable this automatic save-for-suspension to see if this is what is actually causing my problem?

Two, is there any way to make the debug registers visible/virtualized for use by a guest kernel so that they can be used for hardware breakpoints and watchpoints?

Three, assuming the answer to the first two is NO, can anyone suggest another way for gdb to stop execution at precisely the right instruction?

Thanks for any help!

Dan

Cannot access memory at address *** during replay

qzy — Wed, 13 Feb 2008 21:40:00 GMT

When I use GDB remote debugging to modify a variable during replay. I get the error message "Cannot access memory at address ***". I can read the memory content but just cannot modify it.

Is it a feature that does not allow memory modification during the replay? Is there a way to get around that?

Thanks.

Why do we need the replay button?

Robert.Bu — Fri, 15 Feb 2008 02:26:54 GMT

If we do not allow user to modify the register/memory, I think the re-run action can re-produce the problem. Without user interruption/modification, the re-run shall be derterministic.

Recording format

wcray — Fri, 19 Oct 2007 19:45:38 GMT

Are the recordings in an open format? I have a recorded execution and I want to modify it. Is this possible?

serial line debugging

devzero — Sun, 27 Jan 2008 22:39:33 GMT

hello !

it`s very nice to have such advanced debugging feature in vmware, but i rarely use gdb because i`m no programmer.

my question is, why doesn`t vmware support a more basic and well established debugging technique out of the box and why do i need to use external tools for being able to do that?

i mean, it`s quite useful and very common practise to let linux kernel printk to serial line, so why not being able to telnet to the serial port in vmware?

see my feature request at http://communities.vmware.com/message/830847 or in your support database

how to debug one guest OS when multiple guest OSes are running on VMware?

colyli — Mon, 14 Jan 2008 16:22:50 GMT

These days, I am trying VMware 6 debugging. I know use "target remote localhost:8832/64" can connect to the runing guest OS in VMware. But now I run 2 guest OSes at the same time by VMware..

How can I debug a specific OS kernel of these 2 running OSes ? Can any one give me any hint. Thanks in advance

Guest kernel debugging only supported in Linux host?

qzy — Sat, 15 Dec 2007 05:32:02 GMT

It seems this functionality is only implemented in Linux host, which uses GDB remote debugging protocol?

Thanks.

Access physical memory of Guest OS

qzy — Mon, 31 Dec 2007 05:03:08 GMT

I need to debug the Guest application, and in order to do this, it seems I need to have access to the physical memory of the Guest OS in order to parse various kernel data structures (need to translate the Guest application's virtual address to the guest physical address), and set breakpoints in the Guest physical memory. All I need is something as GetGuestPhysicalMemory(void* addr). By the way, I'm running 32-bit Windows XP host and 32-bit Windows XP guest.

I know VMware has supported this for Linux Guest. However, I need to debug Windows Guest (instruction-level debugging is fine). So I think having access to the physical memory of the Guest is the first step to enable the Windows Guest app debugging.

It seems that in VMware workstation 5.0 (windows host) and before, the vmware-vmx.exe contains a filemapping object called VMwareMem<PID>Memory, <PID> is the process ID of vmware-vmx.exe (http://www.ddj.com/architect/184402033). It represents all the physical memory of the Guest OS. However, in VMware workstation 6.0.2 which is what I am using. It doesn't have this filemapping object anymore. What it has are several small filemapping objects named as VMwareMem<PID>PhysRegionX, X could be 0 - 20 or larger, and the number is not continues.

I think VMware must have this kind of information, since it has already implemented the Linux Guest application debugging, it has to parse the kernel data structure using physical memory of Guest as well. If I am wrong, please correct me:)

-Zhiyun

Installing LAT protocol/redirector on an NT4 virtual maching

rasimon3382 — Tue, 09 Oct 2007 13:28:11 GMT

I'm running XP with an NT4 virtual machine that needs to run the networking protocol LAT (a DEC terminal services protocol). I've installed the redirector and created the com ports, but can't connect to the remote machines. Does anyone know how to configure a machine to do this?

Debugging using VM WS6.0

devkpict — Fri, 30 Nov 2007 07:54:52 GMT

I installed VM WS on my SuSE ,I tried to debug my CentOS,

how should I proceed! iam using #32 bit machine

real mode guest debugging

therp — Thu, 01 Nov 2007 19:30:55 GMT

Hello everyone,

I wanted to toy around with the new vmware guest mode debugging feature. Integration with gdb is an excellent idea.

My intention was to start with something simple, namely the MBR.
Vmware starts, I connect to it via gdb's remote facility, the machine stops loading.
I set a break point with
"break *0x7c00" -- the initial MBR location.

but the breakpoint is simply not triggered! (neither with hbreak)

halting the execution in gdb with ctrl-c and poking around shows that the MBR is present at 0x7c00. When I jump to it forcefully with the jump command, the breakpoint is triggered. but for some reason the MBR can't be run twice and everything locks up (maybe I'm already in protected mode? I'm not sure what the windows boot sequence has down when it shows the boot.ini powered boot menu).

Any hints how I can get to real-mode debugging? The problem should be simple to reproduce, everyone has a boot loader

Awesome

JDLangdon — Thu, 20 Sep 2007 14:08:37 GMT

Now maybe I can get some of my questions answered.

What or how are VMware Admins using to monitor their VM's?

Problems importing from Backup Exec System Recovery 7

2ViDiskLib — Sun, 11 Nov 2007 17:41:25 GMT

I had no problems importing from BESR 6.5 but now that I have upgraded to BESR 7.0 I am no longer able to import into VMWare Server.

I am using BESR 7.0.2.23035 and VMWare Server 1.0.4 build-56528

After getting a copy of the latest V2iDiskLib.dll ver 1.0.2.0 from Symantec; I replaced V2iDiskLib.dll ver 1.0.1.0 (only found one reference of the file at C:\Windows\system32). After rebooting the system a number of times I am now getting this error in the log file:

I 2007/11/11 12:13:45 Validating embedded-mode output file C:\DOCUME~1\xx\LOCALS~1\Temp\1\vmware-xx\v2vTempFile2332.xml
I 2007/11/11 12:13:45 Embedded output file tested and cleared, path is valid
L 2007/11/11 12:13:45 V2VAPP <version> log: 11/11/2007 12:13:45 PM
L 2007/11/11 12:13:45 Version 1.5.2 build-45706
D 2007/11/11 12:13:47 Transition from step 0 to 1
D 2007/11/11 12:13:47 Transition from step 1 to 2
D 2007/11/11 12:14:07 Transition from step 2 to 3
I 2007/11/11 12:14:07 FromSourceVM asked to convert O:\xxxxx\xxxxxxx.sv2i
I 2007/11/11 12:14:07 MountDir is C:\mnt
I 2007/11/11 12:14:07 SupportDir is C:\DOCUME~1\xx\LOCALS~1\Temp\1\VpcCvt-2007.11.11-12.14
I 2007/11/11 12:14:07 InstallDir is C:\Program Files\Common Files\VMware\VMware Virtual Machine Importer\
D 2007/11/11 12:14:07 Checking script version against C:\WINDOWS\system32\vbscript.dll
I 2007/11/11 12:14:07 Helper system has VBscript version 5.7.0.5730
I 2007/11/11 12:14:07 V2V setup validated; installDir is C:\Program Files\Common Files\VMware\VMware Virtual Machine Importer\
D 2007/11/11 12:14:07 ValidateVmc validating O:\xxxxx\xxxxxxx.sv2i
W 2007/11/11 12:14:08 Caught an exception in ValidateVmc: errcode -2147221164
W 2007/11/11 12:14:08 TranslateError: original Source is Vmc2vmx.CoVPCConfiguration.1
W 2007/11/11 12:14:08 TranslateError: original Description is The converter has not been initialized.
W 2007/11/11 12:14:08 TranslateError: now err -2147213303: VMware Virtual Machine Importer has encountered an internal error: The converter has not been initialized.
E 2007/11/11 12:14:08 FromSourceVM error: VMware Virtual Machine Importer has encountered an internal error: The converter has not been initialized.

I am getting the same log errors on a Windows 2003 server and Windows XP

Thanks for in advance for any help.

some questions about porting linux driver to esx

Zaxedc — Tue, 06 Nov 2007 10:45:12 GMT

1. I can't us kmap_atomic. Is thers something else to substitute it?

2. how to dump my debug informations? dmesg is useless.

Thanks

cheers,

zax

Guest to host communication in VMWare

khushboo — Wed, 31 Oct 2007 22:46:08 GMT

Hi,

I am looking for some documentation on the guest to host communication in VMWare. I would like to use this channel to gain information about the CPU usage of the guest - either pushing information from the guest to the host, or the host pulling this information from the guest.

Thanks!

Cheer!

Khushboo

Problem installing 64 bit Guest OS

Tom Bokman — Fri, 26 Oct 2007 12:48:01 GMT

I have an HP ProLiant DL380 G5 running ESX 3.0. The hardware is 64 bit. I can create a Windows server 2003 R2 64 bit VM but when I try to power on I get error message: The CPU of the host is incompatible with the CPU feature requirements of VM; problem detected at CPUID level 0x80000001 register 'edx'. What is causing this problem and how do I fix it? Thanks.

Tom Bokman

Where do I post debug info and logs?

Fixxser — Fri, 26 Oct 2007 05:22:24 GMT

where and how do I post some debug info and logs?

64 bit apps issues - ESX 3.02

amcr@wm — Mon, 22 Oct 2007 22:58:55 GMT

Not sure what forum or if this is even appropriate - running ESX 3.02 (no patches yet) and get failures when installing a 64 bit app on a 64 bit 2K3 SP2 installation - ends with "verify you have sufficient priviliges to start system services". Were logged in with local account.

vmware-config error

Brodo — Sat, 20 Oct 2007 14:16:05 GMT

Hi All
I have just installed the VMWare player for Linux on my Intel E6700, Mandriva 2007.1 system.

When I run vmware-config.pl it gives me an error that it can't find the file "libXtst.so.6". Doing a file search shows that this file is alive and well in the
/usr/lib64 directory.

What directory should it be in so vmware-conf can find it or how do I tell this program the right place to look ?

And another newbie question, Will a Win XP guest be able to see and use a TV tuner/PVR card installed on the Linux host ?

TIA
Brodo

Multi thread program not working on FC6 (On VM Player)

sai_g — Mon, 15 Oct 2007 23:46:36 GMT

Hi,

I was trying to write and run some simple multi-threaded programs (using pthreads and compiled using GNU C compiler) on my FC6 installation running on VM Player (2.0.0 build-45731). For some reason the program doesn't seem to run. The program compiles fine, but doesn't run. Upon executing the program the program just doesn't enter the thread.

Any idea why this happens ? Does anyone know of any other OS installation on which thread programming works fine. ?

Thanks in advance.

Memory Allocation for a Citrix Terminal Server guest OS

VMware Rookie — Mon, 15 Oct 2007 17:43:56 GMT

Hello,

I have a Dell PE1950 with Plenty of CPU and 4GB of memory running win2k3 standard. I have a guest OS running win2k3 std. and Citrix. this terminal server will support between 30-40 concurrent users at any given time. I had allocated 3GB of memory for my Guest OS, and left 1GB for my host. im not sure if this is a proper ratio or not. I have tried moving it around a little, but to no avail.

I am having some performance issues on my guest OS:

- CPU of the guest get's pegged very often, while the host OS never gets past 10%

- The nic on the guest appears to be pegged according to the indicator light on the VMWare server console, but I am not noticing any network issues

I am not running any nic teaming software on the host (I've learned my lesson with the BACS). Any thoughts or suggestions? is there something I should be doing differently for a terminal server guest?

thank you

mismatched symbols for RH4 32bit

cutter_brown — Fri, 12 Oct 2007 00:07:55 GMT

Hi there,

I've been tasked with evalutating vmware workstation for debugging linux kernels. I'm currently having an issue with RH4 32 bit (2.6.9-5 smp). Its seems no matter what I do, I keep getting mismatched symbols:

0xc02ce600 in irq_entries_start ()
(gdb) bt
#0 0xc02ce600 in irq_entries_start ()
#1 0xc0104050 in default_idle () at arch/i386/kernel/process.c:99
#2 0xc01040b6 in cpu_idle () at arch/i386/kernel/process.c:161
#3 0xc03807ed in start_kernel () at init/main.c:573
#4 0xc0100211 in is386 ()
#5 0x0001b855 in ?? ()
#6 0xe5890000 in ?? ()
#7 0x8505c65d in ?? ()
#8 0x00c031a8 in ?? ()
#9 0x01b855c3 in ?? ()
#10 0x89000000 in ?? ()
#11 0x05c75de5 in ?? ()
#12 0xc03c50b8 in BIOS_revision ()
#13 0x00000001 in ?? ()
#14 0xe58955c3 in ?? ()
#15 0xc6c0200f in ?? ()
#16 0x31a88605 in ?? ()
#17 0xc88300c0 in ?? ()
#18 0xc0220f0e in as_remove_dispatched_request (q=0x0, rq=0xc037f000)
at drivers/block/as-iosched.c:1073
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I've tried using both the stock kernel-debug rpm package as well as building my own debug kernel and vmlinux. The result is the same. Maybe there is something obvious that I'm missing? We will have to continue using kgdb if I can't get this solution to be as effective.

Thanks for your help!

Cutter

in-guest recording control

wcray — Fri, 12 Oct 2007 16:13:42 GMT

Have the details of this been released yet? I want an application in the guest to trigger record/replay. Any thoughts or ideas?

Thanks

usb floppy not visible to an ms--dos vm

jimmieDV — Sun, 30 Sep 2007 17:43:39 GMT

I have read the two manuals "User's Manual" and "Guest Operating System Installation Guide" and cannot find out how to tell the ms--dos vm where the usb floppy is. The options mentioned in these texts are all grayed out. The windows explorer has no problem seeing the drive.

Can anyone help me with this problem ?

4 port was open

outtuo — Tue, 02 Oct 2007 12:22:52 GMT

I use vmware 6.0 on Xp. When I run a virtual XP and I use "superscan", 4 port was open 119 - 25 - 110 - 143. Somebody know why this port was open ? Because in a last version this port was not open when I scan.

PS: sorry for my english im not realy good

Thanks

outtuo

Getting started with replay-based debugging

ecl100 — Tue, 25 Sep 2007 15:21:32 GMT

Hi, all. If you would like to give Linux replay-based debugging a try, please see VMware engineer Slava Malyugin's recent blog article.

http://stackframe.blogspot.com/2007/09/application-debugging-with-recordreplay.html

What is "replay-based debugging"? Well, the idea is that you use the experimental Record/Replay feature in Workstation 6.0.1 to record the execution of a program running in a virtual machine. Then you control the replay of the program via a debugger. This is particularly useful when dealing with non-deterministic bugs (e.g., due to race conditions), because once the bug is recorded it can be replayed and investigated over and over in the debugger; and it will replay in exactly the same way every time.

I'd love to hear your experiences. Post them here if you like.

Enjoy. E.

Breakpoints

bschatz — Tue, 25 Sep 2007 07:32:36 GMT

Do you have hardware assisted breakpoints working? ie. break *0xcXXXXXX where the address is a valid linear address in the kernel?

It doesnt work for me, however in my case there is one wrinkle: at the time I set the breakpoint, I am in another virtual address space. Do breakpoints set in this manner work across all virtual address spaces?

Taking an alternative route, I have also tried manually inserting an INT3 instruction, but this causes a kernel stack fault.

The gdb didn't know about the int3 that you put manually, so it passed it to the Guest OS and it couldn't handle it.

Is there a way that I can instruct GDB to handle this manual int3?

Thanks,

bradley

New forum!

esiebert7625 — Wed, 19 Sep 2007 22:20:07 GMT

Just wanted to be the first post. This forum was added to discuss cross-product specific guest features like record/replay.

VMware Communities : Thread List - Replay-Based Debugging

Connecting to x64 target

Host could not participate in VCE after failed CPU replaced

Debugging kernel shutdown in a linux guest OS

Howto : Debugging Windows Xp host and Linux VM guest or Linux VM Guest to Linux VM GUest

LVM 1355 - One or more devices not found

Loading symbols for Linux user processes

Host CPU rqmts for Replay?

GDB debug stub does not respond correctly to "T" thread alive queries...

How

Debugging after serious error in client VM

Cannot access memory at address when trying to set a breakpoint

debug rhel

"source-less" debugging with Replay?

Memory watchpoints emulation ?

Getting started: kernel symbols

Debugging a recording made *after* the application has started?

debugStub.listen.guest64.remote = 'TRUE' doesn't open a socket for remote connections

Debugging D programs

trace expansion on release version

Problemm remote debug linux kernel in two VMWare.

Debugging linux kernel (inside vmware) from Mac OSX

Using KDB under Vmware

New bug when using remote kernel debugging

Bugs when using the remote debugging

linuxoffsets?

Debugging xnu-1228.9.59 using Fusion GDB server --> Can't get breakpoints to break

2 questions - choosing a CPU to examine and reversing execution

Setting registers is not supported ?

reverting to snapshot stops syncing

configure vm network setting in sabayon linux

User-mode debugging via GDB stub on Windows

Support for Windows kernel mode debugging?

Logs eval

Replay debugging and Visual Studio 2003?

Problems debugging a Java app in a guest Xp froma a Host Xp wit VMWorksattion 6.5 beta2 1100678

LVM: 1355 One or more PEs inaccessible

Interpreting an execution trace file of the recording

about muti-guest os debug

Question about vmware coredump / vmw-gdb stub

Debugging a PXE image

Transfer Content

Record and replay scope question

Catching linux at the very __start

Cannot access memory at address *** during replay

Why do we need the replay button?

Recording format

serial line debugging

how to debug one guest OS when multiple guest OSes are running on VMware?

Guest kernel debugging only supported in Linux host?

Access physical memory of Guest OS

Installing LAT protocol/redirector on an NT4 virtual maching

Debugging using VM WS6.0

real mode guest debugging

Awesome

Problems importing from Backup Exec System Recovery 7

some questions about porting linux driver to esx

Guest to host communication in VMWare

Problem installing 64 bit Guest OS

Where do I post debug info and logs?

64 bit apps issues - ESX 3.02

vmware-config error

Multi thread program not working on FC6 (On VM Player)

Memory Allocation for a Citrix Terminal Server guest OS

mismatched symbols for RH4 32bit

in-guest recording control

usb floppy not visible to an ms--dos vm

4 port was open

Getting started with replay-based debugging

Breakpoints

New forum!

Debugging a recording made after the application has started?