vmware failure on current Debian/Sid
Something on the current Debian/Sid (03/23/2003) is causing
vmware-3.2.0 (build 2230) to break. The symptom is that vmware starts
up as normal, then just at the time of login (shortly after clicking
the login icon), the X-window image of vmware virtual machine (in my
case Windows-XP) simply vanishes. I have tried several things
including downgrading the compiler to v2.95 of gcc and recompiling the
kernel and all modules (including the vmware modules), using the
xfree86 xserver instead of the nvidia server, etc. All give the same
result. Finally, I transferred to vmware images over to a
Debian/Testing machine, and it works just fine. Further, I transfered
a vmware virtual machine from a Debian/Testing machine (separate and
different virtuam machine running Windows-XP), and it failed on this
Debian/Sid machine. Therefore, it is an issue with the Debian/Sid
software of some kind. Below is the relavant section from the vmware
log file at the time of failure:
above this deleted...
.
.
.
Mar 23 15:08:26: VMX|VBE call 0x4f00 bx 0x0b98 cx 0x0200 es 0x2000 di 0x0000
Mar 23 15:08:26: VMX|VBE: DATA OFFSET from VGA BIOS = 0xb98, size=512
Mar 23 15:08:26: VMX|VBE: VESA VideoModePtr = 0xc0000bc2
Mar 23 15:08:26: VMX|F(127): LES GV_MP #UD count=1
Mar 23 15:08:26: VMX|F(122):1189 eip=804dc521
Mar 23 15:08:45: MKS|MKS lock got type None
Mar 23 15:09:00: VMX|Guest: Win32 Toolbox: Version: $Name: build-2230 $
Mar 23 15:09:00: VMX|TOOLS setting the tools version to '1025'
Mar 23 15:09:00: ide0:0|BigCOWDisk: Wrote version 1025
Mar 23 15:09:01: VMX|GuestRpc: Channel 0, registration number 1, guest application toolbox.
Mar 23 15:09:03: VMX|Caught signal 7 -- pid 2369
Mar 23 15:09:03: VMX|SIGNAL: eip 0x4010e384 esp 0xbffffaf8 ebp 0xbffffb0c
Mar 23 15:09:03: VMX|SIGNAL eax 0x133 ebx 0x4 ecx 0xd0 edx 0x0 esi 0x8 edi 0x81d5718
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffaf8 : 0x081eeb00 0x080bbbcd 0x00000004 0x000000d0
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb08 : 0x00000000 0xbffffb18 0x0806bc65 0x081c4100
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb18 : 0xbffffb2c 0x08053793 0x081eeb00 0x081c4100
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb28 : 0xbffffd01 0xbffffd08 0x0804c0bd 0x00000001
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb38 : 0xbffffd44 0xbffffe23 0x40000608 0x39363332
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb48 : 0x40011100 0x00000005 0x4004d4e8 0x400114ac
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb58 : 0x00000005 0x00000004 0xffffffff 0xffffffff
Mar 23 15:09:03: VMX|SIGNAL stack 0xbffffb68 : 0x080dd48d 0x080dd453 0x080dd456 0x081d5718
Mar 23 15:09:03: VMX|Stopping virtual machine...
Mar 23 15:09:03: VMX|Your core dump size limit is 0 kb.
Mar 23 15:09:03: VMX|Attempting to dump core ...
Mar 23 15:09:03: Floppy|Floppy IPC closed the connection with thread VMX (0x081c40c8)
Mar 23 15:09:03: Floppy|Floppy IPC Exiting because the "VMX" thread is unexpectedly gone.
Mar 23 15:09:03: ide0:0|ide0:0 IPC closed the connection with thread VMX (0x081c40c8)
Mar 23 15:09:03: ide0:0|ide0:0 IPC Exiting because the "VMX" thread is unexpectedly gone.
Mar 23 15:09:03: MKS|MKS IPC closed the connection with thread VMX (0x080e9784)
Mar 23 15:09:03: MKS|MKS: Thread VMX exited unexpectedly.
Mar 23 15:09:03: UI|UI IPC closed the connection with thread MKS (0x081ff6bc)
Mar 23 15:09:03: UI|UI: Thread MKS exited unexpectedly.
--
James D. Freels, Ph.D.
jdfreels@comcast.net
Reply to: