my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.
Related
Use case is something like this. We need to use the Bluez BT stack on linux. There is also dependency of an iOS app that controls BT testing on iOS (On mac). The execution flow triggers mounting of the file system from linux onto mac and tries to build the xcode project and use the .app file that gets generated after the build is successful
If the xcode build command is run manually on Mac directly, there is no problem
xcodebuild test-without-building -project ios_bluetooth/ios_bluetooth.xcodeproj/ -scheme
ios_bluetooth -destination id=uuid -only-
testing:ios_bluetoothUITests CONFIGURATION_BUILD_DIR=./Build/Products/Debug-iphoneos -
derivedDataPath ./ios_bluetooth/DerivedData/ arguments=TESTS_STA_BLUETOOTH_ON
From Linux, after the mount, by default it mounts to /var/root/ProjectFolder/Dependencies. Running the xcodebuild command results in issues in terms of permission. Issue can be see even if logged in as root on mac. Is there a way to circumvent this issue and get the xcode project to build? Any help in this regard is appreciated.
In my linux machine, I'm trying to send a file over to a Windows machine via:
scp fileNameA user#windowServer:fileNameA
I get the following message:
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
What's prompting this message?
I've installed OpenSSH on the windows machine, and I can successfully SSH into it. I don't want to use WinSCP, FileZilla, etc, because I have to automate this in a script. This has to be done from the Linux machine, so I'm not interested in doing pscp from the Windows machine.
I have met the same problem today.
I think it is an issue in the new version of OpenSSH, which was published few days ago. I reverted previous version (v7.6.1.0p1-Beta), which was working correctly on my VM from https://github.com/PowerShell/Win32-OpenSSH/releases and problem was fixed without any changes in configuration.
I just fixed the same problem by moving my installation of OpenSSH from C:\Program Files\OpenSSH to C:\OpenSSH.
I had to first uninstall it properly using the provided script in Win32-OpenSSH and then follow back the information provided there https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH but only changing the path to C:\OpenSSH.
I met a similar issue today, trying to copy files to a Windows server running OpenSSH-Win64. I solved the problem by adding C:\Program Files\OpenSSH, which is the recommended installation location, to the Windows path:
Open the Control Panel, go to the System and Security section and open up System.
Click on Advanced System Settings and, in the System Properties dialog box, click Environmental Variables.
In the System Variables section of the dialog box, select Path and click Edit....
Click New, add the OpenSSH folder path and click OK to apply the change.
Then, do not forget to restart the OpenSSH service, either in the service management console or by running net stop sshd, followed by net start sshd in an elevated console.
I try to build a reproducible automated build environment based on Debian 8.1 Jessie.
I created a boot iso image based on a netinstall image and put a preseed.cfg file in int for automatic installation.
I managed to get it bootable with BIOS and UEFI and can install a KDE Developer Debian in VMWare Workstation 11 fully automated.
I have also a server iso image to install a debian Server with Jenkins, both with BIOS and UEFI Boot.
But after the installation, the Version with UEFI Boot shows a black Screen when started.
I can blindly log in, start the gui with "startx" and see my installed xfce desktop. When i quit xfce the console is usable and visible.
I tried suggested bootparameters "nomodeset" and "vga=Linux" that i found with google to no avail.
I also tried to debug the boot prozess, to find out which command leads to a blank screen, but i did not find the right place to delay the processes at bootup so i can see when the messages dissapear (quiet bootparameter was removed :-)
I also tried to reset the console to no avail.
Can anybode point me to a tool that does the same "switching" like X so the console is useable?
Can anybody give me some hints how to debug the bootprocess to find out which command is causing this behaviour?
I dont want to install X because this should be a headless server system later.
I managed to get my system to boot using the kernel command line modprobe.blacklist=vmwgfx, or placing 'blacklist vmwgfx' in /etc/modprobe.d/*.conf
I assume it is some bug in the vmwgfx module, however as this workaround works for me I have no immediate need to investigate further.
I downloaded Suse Linux 32bit 3.16.6.2.0 as an iso, burned a DVD and installed it as a dual OS with my Win 7. Now, to get the WLan Stick to work....
Using the Win OS I downloaded two files :
ndiswrapper-1.59.tar.gz and fwlanusb-1.00.00.tar.gz
I moved them into the Linux partition and ran the ./install files as instructed.
With both of these installation it requires running a makefile script. In both cases it comes to a crashing stop when /lib/modules/kernel3.16.6.2.0/build is not found.
The 'build' subdirectiory or file is not present. Can I call up one of the rpms to get this part of the Linux OS installed?? Which rpm??
Solving the problem with my WLAN Stick is especially hard because often the Linux documentation says : "in order to make you your internet connection function you must download xyz".
Please install the kernel-source RPM for your running kernel. If this doesn't help already, please make sure that a symlink from /lib/modules/kernel3.16.6.2.0/build to /usr/src/linux exists.
So I am using Ozone OS which is basically just fedora with a cool theme, and a lot less crap installed. I tried installing VMWare Horizon view client from here: https://my.vmware.com/web/vmware/details?downloadGroup=VIEWCLIENTS_LINUX_32&productId=421&rPId=7320
and then i renamed the file to vmware.bundle, when i make it runnable with:
chmod +x vmware.bundle
i ran the file using:
./vmware.bundle
this is what happens in my terminal
VMWare Horizon Client is an x86 application but you are trying to install it to an x64 Linux.
To run this installation, you may need to install 32-bit runtime libraries. Do you want to proceed? (yes/no)yes
Extracting VMware Installer...done.
but when i try going to the application menu, I can find VMware anywhere
There is really no such thing as ".bundle" files on Fedora. The only format for installable software on Fedora are RPM files.
All that this ".bundle" file appears to be, is the vendor's custom installation script, that's all. It's not any kind of a standard packaging format, of any kind.
You will be able to find a newly-installed application on your application menu only if the application correctly installed a .desktop file in the right location. If this installation script did not do so, you won't get anything in the application menu.
It is the application script's responsibility to install a .desktop file in order for the application to appear in the application menu.
try running /bin/vmware
that is the default install location