I've reproduce it now and it's already fixed in the upcoming WS 4.5.2. I can't say when it out, but it's not far away. Thanks, Tommy edward winston wrote:
I am having the same issue with 9.1 and VMWare 4.5.1.
My system is an MSI K8T Master2 FAR board with dual opteron 240. Everything else seems to be working fine (SATA, nVidia) but when i try to start VMWare the machine locks up.
I am going to give a stock kernel a try but would like to stick with the SuSE kernel if possible.
Has there been any update regarding this problem? Should i wait for the next SuSE kernel update via YOU?
Thanks, edward
On Sat, 08 May 2004 18:39:28 +0200 detlef oertel <oertel@uib.de> wrote:
Hello,
my vmware 4.5 worked well under suse 9.0 amd64. But after the Update to suse 9.1
(uname -a:Linux sepia 2.6.4-54.3-default #1 Wed Apr 28 14:04:54 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux)
it freeze the complete system if I power on any VM. (I have to reset/restart the system)
The vmware-any-any-update65 didn't change anything. (Also the updates 60 and 61.....)
vmware-config.pl tells: ----------snip (....) Building for VMware Workstation 4.5.x or VMware GSX Server 3.0.0. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /lib/modules/2.6.4-54.3-default/build/include/.. SUBDIRS=$PWD SRCROOT=$ PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.4-54.3' CHK include/linux/version.h *** Warning: Overriding SUBDIRS on the command line can cause *** inconsistencies CC arch/x86_64/kernel/asm-offsets.s CHK include/asm-x86_64/offset.h CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-config2/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config2/vmmon-only/common/hash.o CC [M] /tmp/vmware-config2/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config2/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config2/vmmon-only/common/task.o CC [M] /tmp/vmware-config2/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-config2/vmmon-only/vmcore/compat.o CC [M] /tmp/vmware-config2/vmmon-only/vmcore/compilercheck.o CC [M] /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-config2/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config2/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config2/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.4-54.3' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config2/vmmon-only' The module loads perfectly in the running kernel.
This program previously created the file /dev/vmmon, and was about to remove it. Somebody else apparently did it already.
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmnet-only' make -C /lib/modules/2.6.4-54.3-default/build/include/.. SUBDIRS=$PWD SRCROOT=$ PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.4-54.3' CHK include/linux/version.h *** Warning: Overriding SUBDIRS on the command line can cause *** inconsistencies make[2]: »arch/x86_64/kernel/asm-offsets.s« ist bereits aktualisiert. CHK include/asm-x86_64/offset.h CC [M] /tmp/vmware-config2/vmnet-only/driver.o CC [M] /tmp/vmware-config2/vmnet-only/hub.o CC [M] /tmp/vmware-config2/vmnet-only/userif.o CC [M] /tmp/vmware-config2/vmnet-only/netif.o CC [M] /tmp/vmware-config2/vmnet-only/bridge.o CC [M] /tmp/vmware-config2/vmnet-only/procfs.o LD [M] /tmp/vmware-config2/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config2/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config2/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.4-54.3' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config2/vmnet-only' The module loads perfectly in the running kernel. (....) --------snap
my vmware is: 4.5.1 build-7568
Petr (the mantainer of the vmware-any-any-updates I think) wrote on: http://www.vmware.com/community/thread.jspa?threadID=1310 according to this problem: "I have no idea how to continue - it definitely works on stock 2.6.4 kernel, so it may be just almost anything, VMware's bug or SuSE's one."
Any help in this mailing list? Does it work at anyone with suse 9.1 amd64 ?
thanks
detlef oertel
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com