mkossmann's Posts

Trying to Upgrade to 17.5 from 17.0.2 fails with the attached vmware-installer log Note the error message : "Exception: VMIS:[Errno 2] No such file or directory: path('/etc/security/limits.conf')" There is is no /etc/security/limits.conf on opensuse tumbleweed. So I created that file with touch. An that worked as workaround

Freshly booted system, checked with ps, that there is no vmware running: Extracting VMware Installer…done. The VMware Installer cannot continue if there are running virtual machines. Shut down or suspend running virtual machines before continuing. Press ‘enter’ to continue.: Any Ideas ?

I have no success so far accessing USB mass storage device from a Windows XP SP3 guest on a SUSE-11.1 ( kernel 2.6.27) host. When I connect the device ( I.e a Sandisk Cruzer USB drive) to an USB connector it is recognized by vmware and popup comes up : The following devices can be connected to this virtual machine using the status bar Or choosing VM->Remobale devices: SanDisk Gruzer Crossfire. If a choose to connect the drive another popup says: The specified device appears to be claimed by another deriver (usb-storage) ..... If I say OK there , nothing happens and the device never shows up in Windows. If I look now into the Windows device manager I see ,that the USB storage driver couldn't be started (Code 10). vmware.log shows : ec 31 11:14:48.294: vmx| USB: Found device [name:SanDisk\ Cruzer\ Crossfire vid:0781 pid:5204 path:6/2 speed:high family:storage] Dec 31 11:14:49.482: vmx| USBG: Skipping SetConfiguration(1) due to device quirks Dec 31 11:14:49.483: vmx| USBIO: Detect usb-storage class Dec 31 11:14:49.529: vmx| USBGL: submit URB failed 16 Dec 31 11:14:51.471: mks| MKS lock got type None Dec 31 11:14:54.368: vmx| USBGL: submit URB failed 16 Dec 31 11:14:56.614: mks| MKS lost grab Dec 31 11:14:57.990: mks| MKS lost grab Dec 31 11:14:59.389: vmx| USBGL: submit URB failed 16 Dec 31 11:15:04.395: vmx| USBGL: submit URB failed 16 Dec 31 11:15:05.086: vmx| USBG: Skipping SetConfiguration(1) due to device quirks Dec 31 11:15:05.086: vmx| USBIO: Detect usb-storage class Dec 31 11:15:05.095: vmx| USBGL: submit URB failed 16 Dec 31 11:15:05.750: vmx| USBG: Skipping SetConfiguration(1) due to device quirks Dec 31 11:15:05.750: vmx| USBIO: Detect usb-storage class Dec 31 11:15:05.757: vmx| USBGL: submit URB failed 16 Dec 31 11:15:06.472: vmx| USBG: Skipping SetConfiguration(1) due to device quirks Dec 31 11:15:06.473: vmx| USBIO: Detect usb-storage class Dec 31 11:15:07.158: mks| MKS switching absolute mouse off Dec 31 11:15:07.184: mks| MKS switching absolute mouse on Dec 31 11:15:14.763: mks| MKS lost grab and the linux syslog shows : Dec 31 11:14:54 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use Dec 31 11:14:59 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use Dec 31 11:15:04 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use Dec 31 11:15:04 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 Dec 31 11:15:04 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 Dec 31 11:15:05 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 Dec 31 11:15:05 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 Dec 31 11:15:06 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5 This problem doesn't show up On SUSE-11.0 with kernel 2.6.25 but also happens on 11.0 with kernel 2.6.27

Installed vmware 6.5 on SUSE 11.1Beta3 . Then started vmware. The result is a segmentation fault : mk@linux-6fqv:~> Logging to /tmp/vmware-mk/setup-6446.log modinfo: could not find module vmmon modinfo: could not find module vmnet modinfo: could not find module vmblock modinfo: could not find module vmci modinfo: could not find module vsock modinfo: could not find module vmmon modinfo: could not find module vmnet modinfo: could not find module vmblock modinfo: could not find module vmci modinfo: could not find module vsock /usr/lib/vmware/bin/launcher.sh: line 231: 6446 Segmentation fault "$binary" "$@" setup-6446.log contains no hint to the problem: Oct 26 17:49:41.047: app| Log for VMware Workstation pid=6446 version=6.5.0 build=build-118166 option=Release Oct 26 17:49:41.047: app| Host codepage=ANSI_X3.4-1968 encoding=ASCII Oct 26 17:49:41.047: app| Logging to /tmp/vmware-mk/setup-6446.log The attached core file, which seems to come from "modconfig --all" is produced by the segmentation fault. Any Ideas how to solve that problem ?

I'am running WS-6.0.1(alos tested with WS-6.02) with a SUSE-10.3 host with Windows XP SP2 guest on a ASUS M6886 notebook. If I configure to use eth0 ;which is the intel ipw 2200bg wireless interface , as vmnet0 , bridged networking doesn't work.There seems to be no network connection, the guest doesn't get its IP address by DHCP. But the wireless connection on the host works fine. This used to work with SUSE-10.2 ( and WS-6.0.0). If I reconfigure vmware to use eth1 (the Broadcom ethernet interface) as vmnet0, all works fine. SUSEfirewall is switched off, I haven't found any useful error messages in the log files yet. Any ideas how to debug and fix that problem ?