Freezing of construction-2496824 VMWare Workstation 11.1.0
Hello
I have a Windows 7 x 64 using Workstation 11.1.0 host (assessment of the trial). I have a Windows 8.1 Pro x 64 running virtual machine. It is the only virtual machine running. A few minutes after starting the virtual machine, the virtual machine and the Workstation locks.
I do Ctrl + Alt + Delete and open the host Task Manager. VMware.exe is always 25% of the CPU (I have a Core i7-4600U, so there are 4 cores with hypertheads). VMware - vmx.exe CPU usuage varies. My only option is to kill the process vmware.exe. Then, the host runs normally. To run the windows 8.1 host once again, I have to restart the computer, as it says the prompt is used.
When the computer restarts normally that's fine. But this time he started running slow after a minute. I opened the windows Task Manager. Once it is open (after 10 minutes) I found that the CPU utilization was only 1% or more. After 10 or 15 minutes of looking around, I started to kill the VMware processes. After that I took some to the host ran normally. It's working normally now.
The issue of freezing happened 4 or 5 times in two or three days. When I kill computer vmware.exe always goes back to normal.
I did a few things like proactive:
(1) add folder VM to the exclusion list antivirus, windows search, exclusion of our backup software list exclusion list.
(2) remove the floppy and CD drive from the list of virtual machine hardware. I read that could cause a hang upwards.
The event log does not contain something interesting. I have attached all newspapers of vmware, I have for the machine virtual windows 8.1.
Any suggestions on what I can do next to try to solve this further?
The host is not lock it just the vmware workstation app. I wanted to clarify that.
Other than the VM Pro 8.1 Windows only other VM I have is Windows XP Mode. I started the XP Mode VM and it has always worked very well after having worked in the virtual machine for an hour. I then restarted the VM of Windows 8.1 and three minutes later, he locked and workstation. I see two vmware - vmx.exe treated one to 25% CPU usage in Task Manager (I presume VM Windows 8.1) and the other with barley any use of CPU (likey XP Mode). Vmware.exe also has 25% CPU usage as before.
I'm in the resource monitor and to suspend the process vmware - vmx.exe which uses 25% cpu and now a workstation and the XP Mode VM work properly. I then clicked on 'stop' the machine virtual windows 8.1 and has resumed the vmx process. VM stop the 8.1 Windows workstation with success. Workstation and the XP Mode VM still work normally.
So certainly issue between the workstation and the machine virtual windows 8.1 but I am not a guru vm or work station, so I can't determine what is the question.
Edit
Repeat the question. Is a wait analyze on vmware.exe chain in resource monitored and must wait on himself: "one or more threads to vmware.exe wait to finish i/o network." and "vmware.exe PID XXXX 6208" Thread. So some kind of blocking of the thread? When I suspend the vmware - vmx.exe running to my VM of Windows 8.1 then the vmware.exe CPU usage goes to 0%. But the wait vmware.exe watch chain still he waits on itself with the same message as above. I then return to the vmware-vmx process and the CPU goes up to 25%.
I can fix things without killing the process vmware or vmx suspend windows 8.1 vmx process, use windows 7 taskbar live preview for click shutdown (square button) and then resume the vmx process. At that point the 8.1 windows vm shutsdown immediately and the workstation (with the xp mode vm) is operating normally.
He has worked to find a few days but starting to give me this problem.
Edit2
OK problem solved I think. Our IT technician installed Malwarebytes Anti-malware over another anti-virus/anti-malware program. Which was causing the computer to 'lock' (run slow but cpu was near 0% so desire ' cpu loading) during start, sounds a different problem than what I saw, but it may affect both workstation. Also my VMs used NAT so I tried to switch to bridged and disabled the NAT and DHCP service. Featured two fewer services to run. Don't know which of those (if any) was causing the problem, but after those changes it works (for the most part very well).
Wes
Tags: VMware
Similar Questions
-
Given Info:
Host server: HP 585g 5 series with 2 x Quad Core AMD procs and 32 GB of RAM.
Host operating system: RHEL5U4 64-bit with no other applications installed except vmware workstation 7.0
VMware Guest storage device: we use a NAS (5 X 1 TB SATA disks) on the same subnet as the host server running Jumbo frames. (Since the introduction of the SIN, we migrated virtual machine of the local/u01 to nfs mounted IP: / vmimages using hard materials & wsize and rsize = 32768)
VMware Guest: 2 X OEL4U7 & 2 RHEL4U8 X 64-bit (all have completely disc and 5 GB or 8 GB of RAM) during the construction of each virtual computer we select the procs and 2cores by proc, giving to each 4procs of the machine. All machines are bridge with their own Maildo IP do not necessarily all the VMS at the same time, but we do not run a pair of them for development and testing. We have vmware tools installed on all of our virtual machine. We aren't on a network of single private from the internet so it didn't there virtually no chance that I would be allowed to get the newspaper.
Unknown problem
During the execution of our virtual machine, we'll do the normal work (construction of an Oracle database) and then exit no where the screen freezes. When this happens, it may be 30 sec, up to 5 minutes or more before the screen becomes available. developers discovered question b/c they could get kicked from the server (ssh); and then she started to occur frequently on the console as well. I have a monitor server that I use to ping the machine while it hangs and when I ping the ip address of the virtual machine that freezes up, it will return the host is unreachable, then all of a sudden the ping works, and life resumes. I have not all snapshot settings or anything like that set up.
The first looking through discussions, we thought it was our problem mounting NFS or the time sync issue b/n host and VM, we very well those who listen now, but nothing helped.
-One of our colleagues believe it might have something to do with the use of multiple processors, instead he Recon using a proc by VM and a carrot...
Question: what I read, in the best practices of VMware, we should be good, but do not know why we freeze all the time. Help, please.
Hello
If you have opened a support case I can't help you any further.
I don't work for VMware and do not have access to these areas
_________________________
VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual
-
Win 10 VMware® Workstation 12 Pro upgrade to 12.0.1 or 12.1.0 keyboard and mouse freeze
Win 10, 64-bit (Build 10586) 10.0.10586, VMware® Workstation 12.0.0 Pro all right.
If I update to VMware® Workstation 12.0.1 or now VMware® Workstation 12.1.0
and restart the system 10 Windows, the keyboard and the mouse freezes.
There is no way to have a system that responded to the questionnaire.
The Start button / stop and restore to you last saved Point is the only solution to support the system.
Someone has a similar problem?
Win 10, 64-bit (Build 10586)
VMware® Workstation 12.0.0
K270 keyboard and mouse USB Logitech M185
Best regards
Franz
New mouse-keyboard combination with Bluetooth adapter and all is fine now.
Franz
-
Installation of VMWare Workstation 11 freezes with gray screen!
Hello
I know this is a very known issue, but difficult to solve, I can't install VMWare Workstation V11 (tried with the old version 8, the same) since as soon as I click Setup, I have a gray screen and installation seems suspended it.
Tried the same thing with VMWare Player, same result, even with older versions...
No way to close the gray screen, unless you kill the process.
My case is laptop Thinkpad T510, native W7 64-bit, processor Intel i5, 4 GB ram, Java utility installed and 100% updated, Nvidia GPU, nothing strange.
Microsoft Security essential only running, no other AV or firewall...
I tried to save two files reading autour on this community, but this does not solve the problem.
I see not what is a well known problem and it is absurd does not have a way to solve it on VMWare...
Any help is very appreciated!
Thank you very much
Concerning
Denis Ferrari
Hi all
problem solved right and - in my case - was a strange key with a small '' L '' name to cancel here:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\
It may be useful
-
using the VMware workstation 100% disc
Hi all
I have amd multi-purpose 8350 with 12 GB of ram and 1 TB hard drive (no ssd). I created a few 10 vms and when I try to start few of them suddenly disk use increases to 100%. I turn them all at the same time, I give some time between each vm poweron. Always the same problem occurs. In addition, even after some time, after activating my vms, same problem occurs. on my windows host computer, the use of the disc is 100% most of the time. because of this my vmware workstation crashes and I am not able to do anything. I have to wait until the use of the disc is free again. I disabled windows search on my host machine, but no luck.
I added the lines on all my machines virtual vmx files but no use.
MemTrimRate = '0 '.
mainMem.useNamedFile = "FALSE".
sched.mem.pshare.Enable = "FALSE".
prefvmx.useRecommendedLockedMemSize = 'TRUE '.
Can someone help me out here?
Thank you
Chaitanya.
Hi Shawn,
Thank you for your response...
At start-up, if it's slow, it's fine. But it happens all of a sudden, even when I'm working. When it freezes, I can't do anything. Just count numbers to kill some time... I have to wait until he's back to normal and I donno when it happens.
While I was looking on the internet, someone posted on an Internet site that disabling superfetch-bit, and windows update services can reduce disk performance. I'm 100% sure they are stopped on my windows host computer. So, I disabled the. But I was really surprised to see the performance of disk after I disabled the services. Now, I have a lag for a few seconds and that occurs only when I start the vms system. After that they are running no problem at all. I donno why a stopped service would cause such an impact. Subsequently, if I do not have a service, I turn it off, turn it off.
Finally, after you turn off the 3 services, I have no problem.
Thank you
Chaitanya.
-
Core upgraded to 4.0 on Centos 7 VMWare Workstation 11 won't build the virtual network device
As shown in the topic, I have manually compiled kernel 4.0 for my installation of CentOS 7. After the installation of the kernel (in rpm mode, followed the instructions here: How to compile a Kernel - The Way CentOS ) installed all 3 rpm, kernel, kernel-headers and kernel-devel and then tried to start my installation of workstation with it leads to having to re - build the components (as usual)
It does not, when it came to the compilation of the network management module. See attached log file that it generated.
I also tried to uninstall, downloaded VMware-Workstation-Full - 11.1.0 - 2496824.x86_64.bundle and re-installed with the same result.
Any help would be appreciated!
aaand..., I fixed my only problem!
Credit:
https://wiki.archlinux.org/index.php/VMware
just applied the 3.19 patch and He-voila!
-
VMware Workstation 10.0.3 on Debian Wheezy compilation error
Hello
I am trying to run VMware Workstation 10.0.3 on Debian Wheezy with custom RHEL kernel 3.10.0 - 4.
Installation went well but when I try: vmware-modconfig - console - install-all I get the following error:
Stopping VMware services:
Demon of authentication makes VMware
VM communication interface socket family is
Virtual machine communication interface is
Virtual machine monitor makes
File system is blocking
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-Df4vT2/vmmon-only '.
/ usr/bin/make /lib/modules/3.10.0-4-pve/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.10.0-4-pve'
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/task.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-Df4vT2/vmmon-only/vmcore/moduleloop.o
/tmp/modconfig-Df4vT2/vmmon-only/Linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
LD [M] /tmp/modconfig-Df4vT2/vmmon-only/vmmon.o
Construction modules, step 2.
MODPOST modules 1
CC /tmp/modconfig-Df4vT2/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-Df4vT2/vmmon-only/vmmon.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.10.0-4-pve'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-Df4vT2/vmmon-only '.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-Df4vT2/vmmon-only '.
CP f vmmon.ko. /... vmmon.o
make: leaving directory ' / tmp/modconfig-Df4vT2/vmmon-only '.
Using 2.6.x kernel build system.
make: entering directory ' / tmp/modconfig-Df4vT2/vmnet-only»
/ usr/bin/make /lib/modules/3.10.0-4-pve/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.10.0-4-pve'
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/driver.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/hub.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/userif.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/netif.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/bridge.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/filter.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/procfs.o
CC [M] /tmp/modconfig-Df4vT2/vmnet-only/smac_compat.o
/tmp/modconfig-Df4vT2/vmnet-only/filter.c: in function 'VNetFilterHookFn ':
/tmp/modconfig-Df4vT2/vmnet-only/filter.c:262:16: error: 'hooknum' undeclared (first use in this function)
/tmp/modconfig-Df4vT2/vmnet-only/filter.c:262:16: Note: each identifier not declared is reported only once for each function it appears in
make [2]: * [/ tmp/modconfig-Df4vT2/vmnet-only/filter.o] error 1
make [2]: * waiting unfinished...
make [1]: * 2 error [_module_/tmp/modconfig-Df4vT2/vmnet-only]
make [1]: leaving directory ' / usr/src/linux-headers-3.10.0-4-pve'
make: * [vmnet.ko] error 2
make: leaving directory ' / tmp/modconfig-Df4vT2/vmnet-only.
Cannot install all modules. See the log for more details.
Is there a solution for this?
Thank you
I just found a solution:
- CD/usr/lib/vmware/modules/source
- CP vmnet.tar vmnet.tar.bak
- tar - xvf vmnet.tar
- VI vmnet-only/filter.c
- replace all the entries with - #if LINUX_VERSION_CODE > = KERNEL_VERSION (3, 13, 0) to #if LINUX_VERSION_CODE > = KERNEL_VERSION (3, 10, 0) and save the file.
- tar vmnet.tar - uvf vmnet-only
- RM - r vmnet-only.
- VMware-modconfig - console - install-all
-
Installation of VMWare Workstation on Fedora 20 10.1
Hello VMWare community!
So I tried for the past few days to install VMWare on my workstation. I tried both VMWare Workstation 9 and 10, but that didn't work either. The problem is just after installation, when are compilation of kernel modules.
Here is the log:
[root@hunt33rsmobilelinux downloads] # cat /tmp/vmware-root/vmware-modconfig-10793.log
2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Log for VMware Workstation pid = version 10.0.1 10793 = build = build-1379776 option = output
2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: The process is 64-bit.
2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Host codepage = UTF-8 encoding = UTF-8
2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Host is the version of Fedora Linux 3.13.4 - 200.fc20.x86_64 20 (Heisenbug)
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/config ': no such file or directory.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Optional preferences PREFS not found in root/.vmware/config file. Using the default values.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: PREF cannot verify the permissions for the preferences file.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/preferences ': no such file or directory.
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------
2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: PREF cannot load the user's preferences.
2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | W110: Connecting to /tmp/vmware-root/vmware-modconfig-10793.log
2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.
2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Created new pathsHash.
2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".
2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.638 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.638 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vmmon module.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for module vmnet.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vmblock module.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for vmci module.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vsock module.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Definition of vsock to depend on vmci.
2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmmon.
2014-03 - 01 T 14: 43:20.723 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
2014-03 - 01 T 14: 43:20.723 + 01:00 | vthread-3 | I120: Modinfo invoking on "vmnet".
2014-03 - 01 T 14: 43:20.724 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.
2014-03 - 01 T 14: 43:20.724 + 01:00 | vthread-3 | I120: Modinfo invoking on 'vmblock '.
2014-03 - 01 T 14: 43:20.725 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.
2014-03 - 01 T 14: 43:20.725 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmci.
2014-03 - 01 T 14: 43:20.727 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.
2014-03 - 01 T 14: 43:20.727 + 01:00 | vthread-3 | I120: Modinfo calling over 'vsock.
2014-03 - 01 T 14: 43:20.728 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
2014-03 - 01 T 14: 43:20.735 + 01:00 | vthread-3 | I120: must be installed: vmnet status: 0
2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.
2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".
2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.748 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.748 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: Kernel header path comes from FileEntry: /lib/modules/3.13.4-200.fc20.x86_64/build/include
2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: update the kernel header path to the /lib/modules/3.13.4-200.fc20.x86_64/build/include
2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.837 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.837 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.838 + 01:00 | vthread-3 | I120: Compiler found at "/ usr/lib64/ccache/gcc.
2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: Got gcc version "4.8.2.
2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.
2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: With the help of the compiler provided by the user "/ usr/lib64/ccache/gcc.
2014-03 - 01 T 14: 43:20.844 + 01:00 | vthread-3 | I120: Got gcc version "4.8.2.
2014-03 - 01 T 14: 43:20.844 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.
2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: Try to find a PBM adapted for the core "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: No corresponding PBM set has been found for the core "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.
2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.853 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.853 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.
2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: Temp dir using ' / tmp '.
2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.
2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".
2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check
2014-03 - 01 T 14: 43:20.870 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.
2014-03 - 01 T 14: 43:20.870 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!
2014-03 - 01 T 14: 43:20.951 + 01:00 | vthread-3 | I120: Modinfo invoking on "vmnet".
2014-03 - 01 T 14: 43:20.953 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.
2014-03 - 01 T 14: 43:20.993 + 01:00 | vthread-3 | I120: The setting for vmnet destination path to ' / lib/modules/3.13.4-200.fc20.x86_64/misc/vmnet.ko '.
2014-03 - 01 T 14: 43:20.993 + 01:00 | vthread-3 | I120: Extraction of the source vmnet "/ usr/lib/vmware/modules/source/vmnet.tar".
2014-03 - 01 T 14: 43:20.996 + 01:00 | vthread-3 | I120: Extract successfully the vmnet source.
2014-03 - 01 T 14: 43:20.996 + 01:00 | vthread-3 | I120: Module construction with the command ' / usr/bin/make - j8 - C/tmp/modconfig-zXW96r/vmnet-only-automatic generation HEADER_DIR=/lib/modules/3.13.4-200.fc20.x86_64/build/include CC = / usr/lib64/ccache/gcc IS_GCC_3 = no ".
2014-03 - 01 T 14: 43:22.104 + 01:00 | vthread-3 | W110: Vmnet failed. Cannot run the command build.
I have tried of course updated everything. yum update is ok, so I'm a bit with no idea.
So, did you ever find this problem?
Thank you
Matthew
- Fedora is not a host for VMware Workstation/Player-supported operating system. Note that although not officially supported as a host nevertheless operating system I run it under Fedora 20, but with the stock kernel.
- I do not think that the 3.13.4 kernel is still supported, even on a supported host OSes.
- Take a look at: VMware modules & core 3.13
-
VMware Workstation 10.0.1 and Windows 7 VM crash on CentOS 6.5 host
Just upgraded to 6.5 CentOS 64-bit (2.6.32 - 431.el6.x86_64). After the updates and reboot I launched VMware Workstation 10.0.1 as I normally and began my OpenVPN (Wheezy Debian) VM with all the problems. I then started my Windows 7 64-bit VM and the entire army what OS hangs and I have to reboot using the reset button.
I was able to reproduce twice in a row. The Windows 7 VM seems to start fine and then when I type my credentials in and it starts to load the office which is when everything goes south and the host completely freezes.
The Windows 7 VM has nothing too complicated installed in it. Some Epson software to start uTorrent and printer in network at startup. Steam does as well, but it is not auto-login or do anything really.
I just did some testing of synthetic load and covered all 8 cores (much more than the usual load) up to 24 GB, 32 GB of RAM and 50% of CPU on the host computer and things remained stable. I thought that a second question could be RAM related because after a soft on boot the Windows 7 VM running I am to about 7 GB of RAM used on the host computer and from the WIndows 7 VM would put me over 8 GB, which resembled a number of nice where things might go wrong If it is RAM related.
Log files:
kdump(1): https://Paste.Fizi.ca/?f5c7c3e6945f8ce4#hPoN0VUJbPKA07hbDPWuE1D0e9FC7Ss8RNvF5Qv7yy0=
vmware - 0.log: https://Paste.Fizi.ca/?05d42cd929bb5237#Zgbtlm7R+bZEHEOs5uSyA6Xin6FOOflWYWvNnHnxksM=
Any ideas?
Looks like I need to learn how to use the forum search tool.
It is a dupe of VMware Workstation - 10.0.1 fails after the software update from RedHat-6.
-
Another VMWare Workstation Fedora 19 x 64 wire
I tried for 2 weeks almost to install vmware player or vmware workstation 10.1 6 on fedora 19 x 64
The process I followed was simply by downloading the file from the vmware website, run it, then run the application.
It starts fine with no errors, but when I try to start a virtual machine the following error message indicates:
Unable to open/dev/vmmon: no such file or directory. Please ensure that the "vmmon" kernel module is loaded.
and then displays this error:
Could not initialize the surveillance apparatus.
and this:
Cannot change the power state of VM: internal error
So after searching around, I tried to build modules with
VMware-modconfig - console - install-all
But it fails with the following error message.
.......
make [1]: entering directory ' / tmp/modconfig-pnqYny/vmnet-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-pnqYny/vmnet-only.
CP f vmnet.ko. /... vmnet.o
make: leaving directory ' / tmp/modconfig-pnqYny/vmnet-only.
From vmware (via systemctl): work for vmware.service failed. See "systemctl situation vmware.service" and "journalctl - xn" for more details.
[NOT]
Cannot start the services
journalctl - xn
-Newspapers are beginning to Mar 2013 - 11 - 12 12:33:24 AST, end my 2013-11-18 12:02:44 AST. --
And the journal file vmware-modconfig - 15432.log
shows:
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Log for VMware Workstation = 15432 pid = 10.0.1 version build = build-1379776 option = output
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: The process is 64-bit.
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Host codepage = UTF-8 encoding = UTF-8
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Host is the version of Fedora Linux 3.11.8 - 200.fc19.x86_64 19 (Schrödinger's cat)
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Msg_Reset:
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: ----------------------------------------
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Msg_Reset:
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/config ': no such file or directory.
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: ----------------------------------------
2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Optional preferences PREFS not found in root/.vmware/config file. Using the default values.
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: initialized! Lets do this thing...
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Obtaining information on the use of the kernel running.
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Created new pathsHash.
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Setting header 3.11.8 path - 200.fc19.x86_64 to "/ lib/modules/3.11.8-200.fc19.x86_64/build/include".
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Validation of path ' / lib/modules/3.11.8-200.fc19.x86_64/build/include ' for kernel version "3.11.8 - 200.fc19.x86_64.
2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: using GCC to preprocess check
2013 11-18 T 12: 05:30.285 + 03:00 | modconfig | I120: Pre-treated UTS_RELEASE, obtained the value "3.11.8 - 200.fc19.x86_64.
2013 11-18 T 12: 05:30.285 + 03:00 | modconfig | I120: The path of the header ' / lib/modules/3.11.8-200.fc19.x86_64/build/include ' to the core "3.11.8 - 200.fc19.x86_64" is valid. Boo!
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vmmon module.
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for module vmnet.
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vmblock module.
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for vmci module.
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vsock module.
2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Definition of vsock to depend on vmci.
2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: Try to find a PBM adapted for the core "3.11.8 - 200.fc19.x86_64.
2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: No corresponding PBM set has been found for the core "3.11.8 - 200.fc19.x86_64.
2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: Compiler found in ' / usr/bin/gcc ".
2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: Got gcc version "4.8.2.
2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.
2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: Temp dir using ' / tmp '.
2013 11-18 T 12: 05:30.443 + 03:00 | modconfig | I120: Setting for vmmon destination path to ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko '.
2013 11-18 T 12: 05:30.443 + 03:00 | modconfig | I120: Extraction of the vmmon sources of "/ usr/lib/vmware/modules/source/vmmon.tar".
2013 11-18 T 12: 05:30.448 + 03:00 | modconfig | I120: Extract successfully the vmmon source.
2013 11-18 T 12: 05:30.448 + 03:00 | modconfig | I120: Module construction with the command ' / usr/bin/make - j4 - C/tmp/modconfig-dbIkzQ/vmmon-only-automatic generation HEADER_DIR=/lib/modules/3.11.8-200.fc19.x86_64/build/include CC = / usr/bin/gcc IS_GCC_3 = no ".
2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Vmmon successfully built. Module is currently at "/ tmp/modconfig-dbIkzQ/vmmon.o".
2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Found the vmmon symvers file to ' / tmp/modconfig-dbIkzQ/vmmon-only/Module.symvers '.
2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Installation vmmon of /tmp/modconfig-dbIkzQ/vmmon.o to lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko.
2013 11-18 T 12: 05:32.056 + 03:00 | modconfig | I120: Save the file ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko '.
2013 11-18 T 12: 05:32.233 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.
2013 11-18 T 12: 05:32.234 + 03:00 | modconfig | I120: Save the file ' / usr/lib/vmware/symvers/vmmon-3.11.8-200.fc19.x86_64 '.
2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.
2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: The setting for vmnet destination path to ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko '.
2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: Extraction of the source vmnet "/ usr/lib/vmware/modules/source/vmnet.tar".
2013 11-18 T 12: 05:32.419 + 03:00 | modconfig | I120: Extract successfully the vmnet source.
2013 11-18 T 12: 05:32.419 + 03:00 | modconfig | I120: Module construction with the command ' / usr/bin/make - j4 - C/tmp/modconfig-dbIkzQ/vmnet-only-automatic generation HEADER_DIR=/lib/modules/3.11.8-200.fc19.x86_64/build/include CC = / usr/bin/gcc IS_GCC_3 = no ".
2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Vmnet successfully built. Module is currently at "/ tmp/modconfig-dbIkzQ/vmnet.o".
2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Found the vmnet symvers file ' / tmp/modconfig-dbIkzQ/vmnet-only/Module.symvers '.
2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Installation vmnet of /tmp/modconfig-dbIkzQ/vmnet.o to lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko.
2013 11-18 T 12: 05:34.832 + 03:00 | modconfig | I120: Save the file ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko '.
2013 11-18 T 12: 05:35.004 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.
2013 11-18 T 12: 05:35.004 + 03:00 | modconfig | I120: Save the file ' / usr/lib/vmware/symvers/vmnet-3.11.8-200.fc19.x86_64 '.
2013 11-18 T 12: 05:35.185 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.
2013 11-18 T 12: 05:35.484 + 03:00 | modconfig | I120: We now stop. Ready to die!
The version of the kernel (uname - r)
Watch: 3.11.8 - 200.fc19.x86_64
The header/devel packages are installed
RPM - qa | grep kernel
shows:
core-tools-libs - 3.11.8 - 200.fc19.x86_64
kernel-devel - 3.11.7 - 200.fc19.x86_64
core-tools - 3.11.8 - 200.fc19.x86_64
libreport-plugin-kerneloops - 2.1.9 - 1.fc19.x86_64
kernel-devel - 3.11.8 - 200.fc19.x86_64
kernel-modules-extra - 3.11.7 - 200.fc19.x86_64
kernel - 3.11.8 - 200.fc19.x86_64
kernel-headers - 3.11.8 - 200.fc19.x86_64
ABRT-addon-kerneloops - 2.1.9 - 1.fc19.x86_64
kernel-devel - 3.9.5 - 301.fc19.x86_64
kernel-modules-extra - 3.9.5 - 301.fc19.x86_64
kernel - 3.11.7 - 200.fc19.x86_64
kernel - 3.9.5 - 301.fc19.x86_64
kernel-modules-extra - 3.11.8 - 200.fc19.x86_64
Note I tried various fixes available online, but none seems not to work too.
I would appreciate any assistance to resolve it.
Thank you all.
Alaa-Problem solved.
I had to disable "Secure Boot" on my laptop.
Thank you all.
-
VMware Workstation 9: could not open/dev/vmmon: no such file or directory
I'll have a plethora of problems installing and get VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0 - 26-generic).
I experienced exactly the same process on my laptop and it works perfectly, while on the desktop, it seems that everything breaks. Could someone give me some kind of help / advice on how I can do to get this working. I tried full uninstall / reinstall of the software, headers of the kernel, kernel images, different kernels, patches here on fresh installs of everything I can think of. Here are the issues I encounter in the order of importance (or so I think):
(1) whenever I try to open my new (and virtual) machine, I get the error sequence of:
"Could not open/dev/vmmon: no such file or directory. " Please make sure that the "vmmon" kernel module is loaded. '--> 'Failed to initialize the device monitor. "->" cannot change the power state of VM: could not find a valid peer to connect to '
(2) every time I try to run the following command to configure the modules on a completely fresh setting (reinstalled kernel, vmware) I get the following output:
sudo modconfig vmware - console - install-all
Stopping VMware services:
Demon of authentication makes VMware
VM communication interface socket family is
Virtual machine communication interface is
Virtual machine monitor makes
File system is blocking
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmmon-only '.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/task.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
CP f vmmon.ko. /... vmmon.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
Using 2.6.x kernel build system.
make: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only»
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/hub.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/userif.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/netif.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/bridge.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/filter.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/procfs.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.
CP f vmnet.ko. /... vmnet.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmblock-only.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:285: warning: assignment of incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:296: warning: passing argument 1 of the "putname" incompatible pointer type
include/Linux/FS.h:2052: Note: expected ' struct filename *' but argument is of type ' char *'
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o
/tmp/modconfig-G9S0TM/vmblock-only/Linux/inode.c:49: warning: initialization from incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:38: warning: initialization from incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a cast
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'
LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!
Warning: "putname" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmblock-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.
CP f vmblock.ko. /... vmblock.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmci-only.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/driverLog.o
LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmci-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.
CP f vmci.ko. /... VMCI.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vsock-only '.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/util.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/driverLog.o
LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!
CC /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vsock-only '.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.
CP f vsock.ko. /... vsock.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface failed
Family of VM communication interface socket failed
File system is blocking
Virtual Ethernet failed
Demon of authentication makes VMware
Cannot start the services
(3) I often get the Ubuntu "this program has planted" messages on "/ usr/lib/vmware-installer/2.1.0/vmis-launcher" "' (this message of crash always occurs when you run the"vmware-modconfig"above command on a new installation.
(4) at different times during Assembly and have VMware workstation on my system I get Ubuntu hangs on "/ usr/lib/vmware/bin/appLoader" and even "/ bin/su" (especially when you are trying to install - su NEVER blocks anywhere else).
Thoughts / ideas on what is happening on earth / what could have caused this all go so downhill / how to go about fixing?
Thank you
Solved.
The problem is that for another program I used gcc - 4. 4 instead of later. Restore the (by update-alternatives - config
) for gcc, g ++ and CPC - bin. Not a very graceful exit to have a version not valid I would say, maybe some sort of basic check could be added to ensure that the correct versions are present?
-
(Beginner) of the initial steps for the new installation of vmware workstation & guest os
Hi, very new for the virtual machine. I need help on what type of software (vmware), need and the first steps of the installation.
Current configuration: a portable 3 separate HD, 1 computer = Windows 7, 2 = XP, 3 is Linux RH. I have manually swap HD to work on each operating system.
Req: A laptop with Windows 7 as main OS and two other OS (XP and Linux) Guest.
(1) I prefer not to install OS and the entire application again for the guest operating system (XP and linux), will like to convert, copy, etc.
(2) can I install multiple OS (XP) for testing of applications and then delete them?
(3) can I use a different version of an application in a guest operating system?
The software that I need to buy:
VMware workstation 7.1
Version of the converted VMware? (this may be free, I think)
ThinApp 4. ???
If these are vmware software that I need is a step by step installation, in particular of the convert.
Thank you, ralph
Hi Raoul,.
Welcome to the forums.
VMware vCenter Converter Standalone is a free download that is accessible to everyone, so you can use it to convert your existing machines.
For testing purposes, you can create a virtual machine "or" with all standard applications, and then use the function 'linked-clone"of the workstation. In this way, you can have several machines quickly with the same basic configuration to test different applications.
It is more complicated to have multiple versions of the same application in a single virtual machine. ThinApp seems to be the solution, but it should require the application packages (I have no experience with ThinApp) construction. It's a bit complicated just to test. Way the easiest would be to create a new virtual machine for each version of the application.
Workstation and the converter are very easy to install if you use a standard configuration.
Good luck.
Concerning
Franck
-
VMware Workstation 7 crashes on Windows XP SP3
Hello
When I run VMware Workstation 7 on my pc, it freezes even if I do not run any machine.
I can't close it, or end the task by the Task Manager (as it also crashes).
I need to force close down using the power button.
My pc specs are:
Windows XP SP 3
Intel Core 2 Quad Q9400 CPU @ 2 .66GHz
2 GB of RAM
Address extension physical (it freezes with and without PAE)
I should mention that it worked in the past. It happened last week.
Any idea?
Dan
Dan,
have you installed anything new or updates (Windows update, virus scanning modes, rules of firewall,...)
As a first step, try to disable the firewall and anti-virus. If this allows to check their records.
André
-
Problem with configure vmware workstation 6.5 with Ubuntu 9.04 64 bit latest kernel
for the Intel-driving problem, I installed a new kernel for Jaunty.
Normally, if you change the kernel, need new VMWARE-Workstation, but it does not work.
I'm getting the following answer
vmware sudo
Login to /tmp/vmware-root/setup-26435.log
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
ModInfo: vmmon module is not found
ModInfo: module vmnet is not found
ModInfo: module vmblock is not found
ModInfo: vmci module is not found
ModInfo: vsock module is not found
Stopping VMware services:
Virtual machine communication interface is
Virtual machine monitor makes
File system is blocking
Using 2.6.x kernel build system.
do: enter the directory ' / tmp/vmware-root/modules/vmmon-only '.
do /lib/modules/2.6.31-999-generic/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of
make [1]: Entering directory ' / usr/src/linux-headers-2.6.31-999-generic'
CC /tmp/vmware-root/modules/vmmon-only/linux/driver.o
In file included from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:31:
/tmp/vmware-root/modules/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.
include/Linux/poll.h:67: error: previous declaration of 'poll_initwait' is here
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.
/tmp/vmware-root/modules/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.
make [2]: * /tmp/vmware-root/modules/vmmon-only/linux/driver.o error 1
make [1]: leaving directory ' / usr/src/linux-headers-2.6.31-999-generic'
make: * http://vmmon.ko error 2
make: leaving directory ' / tmp/vmware-root/modules/vmmon-only '.
and the SETUP LOG
Juli 28 19:20:55.486: app | Journal for VMware Workstation pid = 24193 version 6.5.2 = build = build-156735 option = output
Juli 28 19:20:55.486: app | Host codepage = UTF-8 encoding = UTF-8
Juli 28 19:20:55.486: app | Login to /tmp/vmware-root/setup-24193.log
Juli 28 19:20:56.550: app | Extract the sources of the vmmon module.
Juli 28 19:20:56.600: app | Module construction with the command: / usr/bin/make
C - / tmp/vmware-root/modules/vmmon-only self-build SUPPORT_SMP = 1
HEADER_DIR=/lib/modules/2.6.31-999-generic/build/include
CC = / usr/bin/gcc = GREP / usr/bin/make IS_GCC_3 = no VMCCVER = 4.3.3
and a box with this
Error
Failed to build the kernel module.
Check the log file
Does anyone know a Solution?
Thank you
Greetings
Stefan
-
Computer laptop D830 DELL
V9.04 Ubuntu Jaunty 64 bitLatest Version of VMWare Workstation
-
< / div >
If you want to use the latest kernels that you should look for patches to update - look at this forum to find the last.
http://communities.VMware.com/thread/221724?TSTART=0
___________________________________
-
Can not take new snapshot or manage old snapshots VMware Workstation 6.5.1
I had a stable system of VMware Workstation 6.0 for a long time. I upgraded to 6.5.1 several months ago and it has not been stable. The last symptom is that I can't manage existing snapshots or create new images. The log file of the user interface indicates there is a fault of locking a file. I've gone through the other suggestions of the VMware community, but these have not helped.
Environment:
The host is Windows XP SP3 + updates
Guest is Windows XP SP3 + updates
VMware Workstation 6.5.1 build 126130
Symptoms leading to the situation:
Turn comments off
VM > overview > Snapshot Manager
Take a snapshot
Delete one before (old snapshot)
Wait a while, the bar of progression and GUI finally indicates success
Delete an another prior (old snapshot)
Wait a long time, progress bar freezes, the host OS Task Manager shows process VMware is inadmissible
Click on the upper right corner, 'X' in the Snapshot Manager to close the application, Windows gives error inadmissible usual cancel or continue, cancel selected
Windows offers to send symptom information to Microsoft for the diagnosis
Restart the host operating system
Start VMware, power reviews (it powers on OK)
Repeat the mistake (VMware Snapshot Manager crashes on delete old snapshot)
Restart the host operating system
Consider the suggestions in the community of VMware Workstation, suggestions are to delete the .lck or .lck files for comments, run chkdsk
A ran CHKDSK D: /F /R (no problem found)
Renamed all .lck files in the folder structure customer (renowned specific folders follow below)
Start VMware powered reviews, case comments (it starts very well)
Watch VMware directory, confirm that there is no new .lck files/folders
Use VMware Snapshot Manager, try to take pictures or delete old snapshot - both fail, suspended process, must cancel
Here is an excerpt of "UI current log file" (C:\Documents and Settings\gperkins. MERITER\Local Settings\Temp\vmware-gperkins\vmware-gperkins-2268.log)
Apr 16 14:27:57.853: vmui | File unexpected error updating cache snapshot of Foundry of blocking: the file is already in use
Apr 16 14:27:57.853: vmui | Could not update the snapshot tree: tree inconsistent state.
Apr 16 14:28:00.666: vmui | FILE: WaitForPossession timeout on "D:\vmware\WinXP VA33100XP\Windows XP Professional.vmsd.lck\M17021.lck" due to a local process (3660)
Apr 16 14:28:00.712: vmui | FILE: FileIO_Lock on 'D:\vmware\WinXP VA33100XP\Windows XP Professional.vmsd' failed: lock has expired
Apr 16 14:28:00.712: vmui | In SHORT: Impossible to open and lock file "D:\vmware\WinXP VA33100XP\Windows XP Professional.vmsd".
Apr 16 14:28:00.712: vmui | SNAPSHOT: SnapshotConfigInfoRead failed for the file "D:\vmware\WinXP VA33100XP\Windows XP Professional.vmx": cannot lock the file (3)
Here is a list of old .lck files that I renamed (within each are .lck files which are not renamed):
D:\vmware\WinXP VA33100XP\Delete-me2-Windows XP Professional.vmx.lck
D:\vmware\WinXP VA33100XP\Delete - me - Windows XP Professional - 000001.vmdk.lck
D:\vmware\WinXP VA33100XP\Delete - me - Windows XP Professional - 000002.vmdk.lck
D:\vmware\WinXP VA33100XP\Delete - me - Windows XP Professional - 000003.vmdk.lck
D:\vmware\WinXP VA33100XP\Delete-me-Windows XP Professional.vmdk.lck
D:\vmware\WinXP VA33100XP\Delete-me-Windows XP Professional.vmsd.lck
D:\vmware\WinXP VA33100XP\Delete-me-Windows XP Professional.vmx.lck
Any advice/suggestions would be welcome.
With the VM power off and out the VMware Workstation (close the app) try to remove the *.lck files
Now start Workstation and see if you still have questions
Maybe you are looking for
-
Your AppleTV can download movies in mode 'sleep'?
I was wondering if you could rent a movie and I have AppleTV (generation 4) download the movie in his sleep.
-
Problem with webcam not fixed with Vista SP1 on Portege M700
The Vista SP1 does nothing to the failure of Vista to recognize the built-in webcam Portege M700.The existing forum thread mark this question as a response, despite the link to the document toshiba mentioning the error messages entirely different fro
-
Hi everyone, on my laptop was installed so password every time when I start I to fill it, but now I can't use the password but I don't ' know how to do. I tried to get into the Bios but I can't (using the work of did'n of F8 and Del key). Can someone
-
Pavillion DFV6: Windows 7 do not restore from DVD hp when you are almost finished.
I have a Windows 7, which was compromised by the virus and virus, then viruses withdrew. Therefore, the infographic was considered compromised including any recovery partition. Then,. data backup I order recover CD from HP, pay money for them. I turn
-
At startup until a message appears - impossible to find this thing - you can reinstall.
A few days ago I installed new software for I tunes - something I've done many times. But this time it failed. I don't think that anything - but when I turn on my computer now a box appear head "APSD Daemon.exe" saying that they could not find "MSC