I had the same problem: I downgraded glibc from 2.2.5-1 to 2.2.4-25 and 
vmware works again

On Saturday 23 March 2002 11:39 am, you wrote:
> Hello,
>
> I'm unable to start VMWare3.0 with the latest kernel release.
>
> What I get is this: (VMWare's win98.log)
>
> Mar 23 17:33:51: VMX|Disk: Open(/home/arkay/vmware/win98/win98.vmdk)
> flags=0x0=.
> Mar 23 17:33:51: VMX|BigCOWDisk_OpenFromParent: Big Cow Disk
> /home/arkay/vmware/win98/win98.vmdk
> Mar 23 17:33:51: VMX|BigCOWDisk_OpenFromParent: COWDisk is Big capable
> Mar 23 17:33:51:
> VMX|COWDisk_OpenFromP(/home/arkay/vmware/win98/win98.vmdk) flags 0x0=
> diskNum=0
> Mar 23 17:33:51: VMX|FILEIO: Reverting to buffered IO for file
> /home/arkay/vmware/win98/win98.vmdkCOWDISK: Disk
> /home/arkay/vmware/win98/win98.vmdk Granularity = 128
> Mar 23 17:33:51: VMX|COWDISK: Open: /home/arkay/vmware/win98/win98.vmdk
> has Generation number 2624745838.
> Mar 23 17:33:51:
> VMX|COWDisk_OpenFromP(/home/arkay/vmware/win98/win98-02.vmdk) flags 0x0=
> diskNum=1
> Mar 23 17:33:51: VMX|FILEIO: Reverting to buffered IO for file
> /home/arkay/vmware/win98/win98-02.vmdkCOWDISK: Disk
> /home/arkay/vmware/win98/win98-02.vmdk Granularity = 128
> Mar 23 17:33:51: VMX|COWDISK: Open: /home/arkay/vmware/win98/win98-02.vmdk
> has Generation number 2624745838.
> Mar 23 17:33:51: VMX|BigCOWDisk_Close: closing 2 disks of BigCowDisk
> /home/arkay/vmware/win98/win98.vmdk
> Mar 23 17:33:51: VMX|(VMX) DeclareThread ide0:0 module=16 source=0x200000
> Mar 23 17:33:51: VMX|Creating thread 'ide0:0', type 16 from self, pid=9754
> Mar 23 17:33:51: VMX|Created AIO ide0:0 pid=9754 sharedArea=0x4028f000
> size=0x2000
> Mar 23 17:33:51: VMX|(SELF) DeclareThread ide0:0 module=16 source=0x200000
> Mar 23 17:33:51: ide0:0|(ide0:0) DeclareThread VMX module=1 source=0x10000
> Mar 23 17:33:51: ide0:0|NOT_IMPLEMENTED F(831):688
> Mar 23 17:33:51: ide0:0|AIO: ide0:0, Process 9754 panic.
> Mar 23 17:33:51: ide0:0|AIOSlave: Exit after panic.
> Mar 23 17:33:51: VMX|AIO: NOT_IMPLEMENTED F(831):688
> Mar 23 17:33:51: VMX|Backtrace:
> Mar 23 17:33:51: VMX|Backtrace[0] 0xbfffeeb8 eip 0x8053ce9
> Mar 23 17:33:51: VMX|Backtrace[1] 0xbfffeeec eip 0x8050896
> Mar 23 17:33:51: VMX|Backtrace[2] 0xbfffef58 eip 0x80ad5ce
> Mar 23 17:33:51: VMX|Backtrace[3] 0xbfffefec eip 0x80ae1aa
> Mar 23 17:33:51: VMX|Backtrace[4] 0xbffff004 eip 0x80adde6
> Mar 23 17:33:51: VMX|Backtrace[5] 0xbffff018 eip 0x80ae955
> Mar 23 17:33:51: VMX|Backtrace[6] 0xbffff024 eip 0x80aec6b
> Mar 23 17:33:51: VMX|Backtrace[7] 0xbffff03c eip 0x80bb8d6
> Mar 23 17:33:51: VMX|Backtrace[8] 0xbffff068 eip 0x80bb845
> Mar 23 17:33:51: VMX|Backtrace[9] 0xbffff22c eip 0x80bbba5
> Mar 23 17:33:51: VMX|Backtrace[10] 0xbffff25c eip 0x80badf5
> Mar 23 17:33:51: VMX|Backtrace[11] 0xbffff274 eip 0x80baf00
> Mar 23 17:33:51: VMX|Backtrace[12] 0xbffff28c eip 0x80adba8
> Mar 23 17:33:51: VMX|Backtrace[13] 0xbffff2a4 eip 0x80507f4
> Mar 23 17:33:51: VMX|Backtrace[14] 0xbffff414 eip 0x80907d8
> Mar 23 17:33:51: VMX|Backtrace[15] 0xbffff44c eip 0x809478e
> Mar 23 17:33:51: VMX|Msg_Post Error: msg.log.vmxpanic
> VMware Workstation PANIC: (VMX)
>
> AIO: NOT_IMPLEMENTED F(831):688
>
> Rgds,
> Rainer

Reply via email to