Snapshot fails on VMWare Workstation 11 Pro
Hello
I have created a virtual machine on VMWare Workstation 11 Pro with Windows Server 2008 R2 and baptized "HYP". When I'm trying to take a snapshot, I get the following message:
VMware Workstation cannot find the virtual disk 'G:\YP.vmdk '. Check that the path is valid and try again.
The system cannot find the specified file
Cannot open disk 'G:\HYP-000001.vmdk' or one of the snapshot disks it depends on.
Necessary to the VM to suspend operation and the VM could not continue to run.
After that I click OK in the message box that precedes, the virtual computer turns off and then I can turn it on again - I get the following message:
File not found: YP.vmdk
This file is required to power on this virtual machine. If this file has been moved, specify the new location.
Note that I might be able to on and off this machine virtual without problem before I tried to take the snapshot.
How is that possible I could have it fixed?
Thank you very much!
I found where it was. When I was creating this virtual machine, I indicated the location for the new virtual machine as any new drive G. After I had removed this virtual machine and created a new in 'G:\FolderName', the new virtual machine begins to create fine snapshots.
It is important to specify the folder (not just a new drive letter) as the location for the new virtual machine.
Tags: VMware
Similar Questions
-
VMware Workstation 11 Pro doesn't work on Ubuntu 15.10 x 64.
Hello
I used Ubntu 15.04 x 64 as the host for VMware Workstation 11 Pro. It was working fine.
I've upgraded to Ubuntu 15.10 x 64, and now my computer does not open.
When I try vmware-Installer:
$ vmware-Installer
GTK-Message: could not load module '-gtk-module unity ": libunity-gtk - module.so: Nao e possible open land of objetos compartilhado: land UO diretorio nao found
(vmware - install .py: 5489): Gtk-WARNING *: Nao faith possible service a tool of temas no module_path: "murrine"
...
...
...
GTK-Message: could not load module 'canberra-gtk-module': libcanberra-gtk - module.so: Nao e possible open objetos compartilhado land: land UO diretorio nao sown
$ vmware-Installer - l
Product product name version
==================== ====================
VMware-workstation 11.1.2.2780323
How to solve this problem, please?
Hello
The problem has been resolved by the release of VMware Workstation 11.1.3:
$ sudo /etc/init.d/vmware status Module vmmon loaded Module vmnet loaded $ sudo /etc/init.d/vmware stop Stopping VMware services: VMware Authentication Daemon done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done $ sudo /etc/init.d/vmware start Starting VMware services: Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet done VMware Authentication Daemon done Shared Memory Available done $ vmware-installer -t Component Name Component Long Name Component Version =========================================== =================================================== ==================== vmware-installer VMware Installer 2.1.0.2758308 vmware-player-setup VMware Player Setup 7.1.3.3206955 vmware-vmx VMware VMX 7.1.3.3206955 vmware-vix-core VMware VIX Core for Linux 1.14.4.3206955 vmware-network-editor VMware Network Editor 11.1.3.3206955 vmware-network-editor-ui VMware Network Editor User Interface 11.1.3.3206955 vmware-tools-netware VMware Tools for Netware 9.9.4.3206955 vmware-tools-windows VMware Tools for Windows 9.9.4.3206955 vmware-tools-winPre2k VMware Tools for Windows (Pre 2000) 9.9.4.3206955 vmware-tools-freebsd VMware Tools for FreeBSD 9.9.4.3206955 vmware-tools-solaris VMware Tools for Solaris 9.9.4.3206955 vmware-tools-linux VMware Tools for Linux 9.9.4.3206955 vmware-usbarbitrator VMware USB Arbitrator 14.1.5.3206955 vmware-player-app VMware Player Application 7.1.3.3206955 vmware-vix-lib-Workstation1100andvSphere600 VMware VIX Workstation-11.0.0-and-vSphere-6.0.0 Lib 1.14.4.3206955 vmware-workstation-server VMware Workstation Server 11.1.3.3206955 vmware-ovftool VMware OVF Tool component for Linux 4.1.0.2982904 vmware-vprobe VMware vProbe 7.1.3.3206955 vmware-workstation VMware Workstation 11.1.3.3206955 $ vmware-installer -l Product Name Product Version ==================== ==================== vmware-workstation 11.1.3.3206955
-
VMware Workstation 12 Pro - mouse stops working
I have VMware Workstation Pro 12. I used it for weeks without problem. Suddenly the mouse will stop working on a virtual computer. This happens while the guest is initialized and running. I click on another window and click back, and the mouse does not work in the comments. This happens in all guests, regardless of the operating system. The only way to solve this problem is to restart the host. Then I can use the guests still once for 15-20 minutes until the problem reoccur.
This problem has been resolved. Once I realized that the problem was related to all audio, I was able to narrow the search down to VMware Workstation, audio, and the click of the mouse.
This is another article here that describes the problem.
I've updated my Lenovo Realtek drivers for laptop (from Lenovo) to version 6.0.1.7576.
-
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
-
VMware Workstation 12 Pro Maximum number of standard error of virtual Macines
I get this error when I open many clones of virtual machine to WIn 2K12R2. now, I opened a new instance of workstation for
run a new VM clones. I don't have this problem in the Workstation 11.0.2
There is a limitation in Windows that will sometimes hit when an instance of VMware Workstation tries to manage a lot of virtual machines simultaneously. If the workstation user interface knock this architectural limit (which can happen to about 28 VMs), the user interface will break.
Earlier versions of workstation had a check in place to prevent that from happening, but that the cheque has been omitted by mistake of recent versions, you to eventually open a little more VMs, but risk of accident. 12 workstation restores the audit. In a future version of Workstation I hope will eventually be restructured to avoid the underlying limitation altogether, but we are not yet there.
This particular limitation is not related to the total number of virtual machines that are running on the computer host, so (as the message says) you should be able to simply open a second instance of VMware Workstation and run several virtual machines in this second case. If I remember correctly, I think that we have a strict limit of 64 virtual machines running simultaneously on Windows hosts.
I hope this helps!
--
Darius
-
Upgrade Windows 8.0 invited to 8.1 fails in VMware Workstation v10?
Hello.
Everyone knows about this problem? I tried two W8 (English and French) VM different images (1 GB RAM) and cannot be properly upgraded. Need me to:
(Picked in English) language selection screen.
Choose an option: 'Disorder (refresh or reset your PC or use advanced tools)' or 'turn on your PC.
What's wrong? I never had this problem on my real desktop PC.
Thank you in advance.
jmattson wrote:
This is probably the problem. 8.1 Windows no longer includes the SCSI card drivers. Upgrade your SCSI card virtual, and you should be good to go.
Modify the text in the configuration is considered to be an upgrade? Laughing out loud. I wonder why VMware never mentioned this when 8.1 is out.
-
The title says it all: I have guests Windows Pro 10 tree on a host Windows 10 Pro running VMware Workstation 12 Pro, and I can not access shared folders of the host within the VM settings (\\vmware-host\shared records), or the mapped Z: drive.
Shared folders on the host computer using the normal windows, sharing mechanism are perfectly accessible from the guests. Shared folders on the guests using the normal windows, sharing mechanism are perfectly accessible from the host. Only those shared in the virtual computer settings are not available,
I tried to remove and then re-add files, to temporarily disable and sharing, but also re - install VMware tools, with no chance of return. The device worked fine until my clients running Windows 7 and 8.1.
I know there are questions like that all over the forum, but I have found no working solution for workstation Pro (and Windows 10).
Someone at - it ideas?
There was another thread a few days on the same subject, where it has been fixed by completely uninstall VMware Tools, by restarting the OS invited and reinstall the tools (Important: not only do a "repair" install). Have you tried full uninstall-reboot-reinstall of tools?
See you soon,.
--
Darius
-
Failed to create virtual machine using VMWare Workstation 11 (test)
Hello people,
I installed VMWare Workstation on my machine Windows 10 and trying to create multiple virtual machines to test the object. I have done this before on the Windows 7 computer and did not face any problems, but this time, as soon as I gave the location of the file to deploy an operating system it comes up with some fatal errors as error BLK_CACHE IOERR if I have enough space on the HARD drive and everything is not going further. So, my question is if my computer has compatible with Windows 10 problems or there is something else that would cause this problem. Any help or comments would be appreciated on this topic.
Thank you!.
Thanks for your answer, Noel
I was going through discussions in the community with similar and found subjects that VMWare had released 12 pro workstation that supports Windows 10 entirely. I personally installed it on my physical machine and it works. Here is the link for the release of Workstation 12 notes.
-
6u2 ESXi host nested on VMware Workstation for Linux referee v12
Hello all, I have
I have a lab environment virtual running in VMware Workstation for Linux v12, and my ESXi hosts do not work correctly on one of the virtual networks. All my troubleshooting suggests a problem with nested ESXi hosts that may be a bug, but I want to assure you that I did everything properly first. That's why I post here with the hope that if I made a mistake that maybe someone else can point out he me.
Physical system
8 core Intel Xeon 2.1 GHz CPU
128 GB of RAM
OS - kernel Linux 64 - bit w/3.19.0-32-generic Linux Mint 17.3 (fully updated from this announcement)
VMware Workstation 12 Pro - 12.1.1. Build-3770994 (fully updated from this announcement)
Nested ESXi host VM
ESXi v6.0.0 (Build 3825889, completely updated from this announcement)
4 cards 'physical' (only 3 used for now)
-all use the e1000 NIC hardware virtual, but also tried vmxnet3 NIC with no difference
-vSwitch0 use vmnic0 & 1 vmnet16 of virtual network in a pair of active / standby
-vSwitch1 uses vmnic2 on network virtual vmnet18
-vmk0 used for management on vSwitch0 and vmk1 for iSCSI on vSwitch1
-"Promiscuous" mode and forged passes enabled on all Port vSwitch groups (activating or turning off these features makes no difference)
Test performed until now
I checked that all the IP addresses and network masks used are correct.
With the help of vmkping I ping other nodes on the network vmnet16 with success.
With the help of vmkping I tried to ping the other nodes in the network vmnet18, but that has failed.
I have depolyed other non - ESXi VMs on the vmnet18 network, and they are able to ping each other, but are unable to ping or ping by the ESXI host.
I tried various material virtual NIC as mentioned before, but without changes in the results.
I tried to use only local network instead of the vmnet18 guest network segments with no change in results.
When I find out the status of the network adapters on the ESXi host through vCenter or host incorporated client vmnic0 & 1 time display network information, but vmnic2 shows no networks. Yet, I know that there is a network with different VM communicate on it. Moreover, I was able to get all of this work on a Windows system running 10 Workstation (this is the laptop that my employer gives me with).
Having built nested ESXi labs on different platforms as well as physical environments in the past, I'm very confused as to why I can't get this special configuration to work. At this point my gut tells me that this is probably a bug any with the nested themselves ESXi hosts. Since I can get all this work on vmnet16 including the management of ESXi hosts and the VCSA that I use, I am sure that my vSwitch configuration is correct (other than the IP address space and vmnic configurations is bascially the same). Because I can get other virtual machines to communicate over the network vmnet18 I don't see how can be a VMware Workstation for the issue physical Linux host. Is there something obvious I'm missing here? I read on the ESXi hosts nested under VMware Workstation after having known problems and bugs with networking. If anyone else has experienced this?
Thanks for any help others can provide!
Kind regards
Patrick
Well, the problem is now resolved. The problem was what covelli was trying to explain, but I couldn't because the physical host network adapters being mentioned.
The problem on the Linux host, but it was a problem of permissions with the virtual Ethernet adapters. The following article has the fix:
With the help of Ethernet virtual cards in Promiscuous Mode on a Linux host (287) | VMware KBEven if I launched the workstation under the root user I have yet met this problem and which still makes no sense to me, but change the permissions solve the problem. I was not getting an error message on my Linux Mint and Ubuntu system, but when I tried on a second box of Linux Mint that I just got the error has been generated, and the error message was the above link it contains.
So, here's what I learned:
(1) the question has nothing to with a VMware Workstation definition that you can configure.
(2) the question has nothing to do with a physical network card.
(3) the question has nothing to do with any vmnic on the nested ESXi host.(4) apparently virtual Ethernet adapters are not the correct permissions when created.
All you have to do to fix this is:
(1) open a terminal.
(2) run the command ' sudo chmod a + rw/dev/vmnet * "(don't forget to run this each time that you create a new virtual network).
You can also create a group, as shown in the link above and simply give this group the correct permissions. Personally, I think it's easier to just give everyone the rw permission.
I appreciate the help that others have offered. I did not understand what was asked for in previous answers because of the terms that have been used.
-
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
-
VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host
Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.
After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release 2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit. 2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8 2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final) 2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory. 2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory. 2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values. 2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log 2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel. 2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash. 2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include". 2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers 2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci. 2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon". 2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet". 2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock". 2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci". 2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock". 2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0 2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel. 2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include". 2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers 2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers. 2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions 2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include 2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include 2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc" 2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7". 2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc". 2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7". 2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp". 2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel. 2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include". 2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h 2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64". 2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid. Whoohoo! 2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers 2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers. 2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions 2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet". 2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko". 2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source. 2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command.
Hi, I faced the same problem, and now I have corrected this issue.
He was vmnet.ko, at least for me.
Here's how to solve,
You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko
Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.
And then run vmware, if you fail at the first, please run again.
If so, you can run vmwre!
I hope this will help you.
Good day.
-
VMware Workstation failed to mount the physical disk 10TB
VMware workstation or any other product vmware does support more than 2 TB of physical disks?
I am trying to connect a 5 of 10 TB raid enclosure and mount it on my ubuntu vmware workstation machine. The common error that I receive is when mounting the reader on ubuntu and I think it might have something to do with the size of the file.
I am running vmware workstation 12 in windows 10.
The disk is taken offline in windows and I'm under WS as an administrator.Error VMDK CONTENT DiskPart Info Operation failed on the file "\\.\PhysicalDrive1".
If the file is located on a remote file system, make sure that the network connection and the server on which resides this disk to work correctly. If the file is saved on a removable medium, link media.
Select Retry to retry the operation.
Click Cancel to end this session.
Select continue to pass the error to the guest operating system.
I/o error, dev sdb, sector 11721553632
I/o error, dev sdb, sector 11721552128
I/o error detected. File system stop
Please unmount the file system and to rectify the problem (s)
metadata I/O error: block 0x2baa8b100 ("xlog_bwrite") error 5 numblks 8200
can not read the superblock
# Disk DescriptorFile
version = 1
Encoding = "windows-1252".
CID = 6f4a8bb1
parentCID = ffffffff
isNativeSnapshot = 'no '.
createType = "fullDevice."
# Description of the measure
RW 23441768448 DISH '\\.\PhysicalDrive1' 0 partitionUUID \\?\scsi#disk & ven_h #w & prod_raid5 #5 & 19bb575e & 0 & 010000 #{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
# The database disk
#DDB
ddb.adapterType = "free".
ddb.geometry.biosCylinders = "1024".
ddb.geometry.biosHeads = "255".
ddb.geometry.biosSectors = "63".
DDB. Geometry.Cylinders = "16383.
DDB. Geometry.Heads = "16".
DDB. Geometry.sectors = "63".
ddb.longContentID = "55c8f3052c372c02465d66656f4a8bb1".
DDB. UUID = "60 00 C2 97 8 a 7 c c2 cb - 9 a 27 51 78 58 a7 e6 3f"
ddb.virtualHWVersion = "12".
H/W RAID5
Disc ID: 00000000
Type: SATA
Status: Offline (policy)
Path: 1
Target: 0
LUN ID: 0
Path: PCIROOT (0) #PCI (1C07) #PCI (0000) #ATA (C01T00L00)
Current read-only State: No.
Read-only: No.
Boot disk: No.
Disk swap file: No.
Disk hibernation file: No.
Crash dump disk: No.
Cluster disk: No.
The official version said that WS allows only virtual up to 8 TB of disk.
According to my own tests, it only limits the size of the VMDK for 'New - VM' Assistant.
Once you have a greater vmdk - just tried a vmdk 10TB - WS won't complain about the size.
I don't expect that WS will prevent the physical disks to use inside a virtual machine that is already configured.
So in your case I think you started WS with a normal user account.
Try to start as administrator WS - maybe even using the administrator account.
I think that then it will work.
Unfortunately, the error messages produced by vmware.exe are not really accurate-, so there is no way to know if you really have a bad super block.
To test if this is really the problem and not just an error message - poor try to mount the drive directly.
Please post the vmdk - want to know if there is something unusual about 5.5 TB in the disk. -
Cannot install VMware Workstation on Windows 8.1 Pro 64 bit 11.1.1 - Please help
You want to install VMware Workstation 11.1.1 on new 8.1 Windows Pro 64-bit PC.
I had VMware Workstation 11.1.0, and deleted the original installer but did not finish the installation of the new version
The installer gets about 2/3 way (progress bar) and then crashes, Windows Installer says Event Viewer hung.
Race tried without firewall and AV, always not install question
A ran the installer with / clean option and then tried again, but still he did not finish the installation process (crashes at the same place)
Noticed in the Manager tasks that VMware Installer runs at about 14% of CPU, but nothing happens
I'm really at a loss as to why I can't install VMware Workstation 11.1.1, all the other soft\ware settles very well.
Please could someone help me?
Thank you
Peter
Ran Windows Update Troubleshooter
It fixed a number of things
I could then install VMware Workstation
No idea but why the installer got himself in this State
-
Hi all
The MSI failed with the error message as "could not write value vmware - tray.exe in \SOFTWARE\Microsoft\Windows'CurrentVersion\Run key. Make sure you have fufficient access to that key, or contact your support staff' while trying to install vmware workstation 11.1.0 in windows 8.1.
I tried to call the installer with run as administrator but it does not help, please suggest me overcome this error.Hi Vincentand welcome to the VMware communities!
This error indicates that you have some security software (antivirus or antimalware software) that protects the part of the registry. Can you try to temporarily disable all security software on your host computer and see if the installation can move forward?
See you soon,.
--
Darius
-
VMware Workstation 10.0.5 MSI failed
I'm upgrading to VMware Workstation 10.0.5 since 10.0.4. The upgrade process has deleted 10.0.4, but when trying to install v10.0.5 I get an error:
The MSI 'C:\Users\Ethan\AppData\Local\Temp\VMware_1422579427\vmwareworkstation_x64.msi' failed.
I did the following with no fruit:
- Monitoring of VMware KB 1031302 and 1308 KB
- Copy the "C:\Users\Ethan\AppData\Local\Temp\VMware_*\" directory to another location of the command execution
msiexec.exe /i vmwareworkstation_x64.msi EULAS_AGREED=1
However, I got a different error:Failed to install the hcmon driver.
- Ran CCleaner registry cleaner
- Tried to (re) install VMware 10.0.4, however I still had the impossible "msi" error
I found two newspapers, which are listed below. I have searched without finding a solution, any help would be greatly appreciated!
Hi etnguyen03etnguyen03,.
Here are 3 useful links when Workstation Setup error occurs on Windows.
It will be useful.
VMware KB: Cleaning after incomplete uninstall on a Windows host
VMware KB: Troubleshooting a MSI error when a VMware product or installation of tools
Need to reinstall Windows Installer in Windows 7 - Microsoft Community
Given that you've tried the KB 1031302 and 1308 KB, the third link may be more useful.
According to the answer in the third link:
Please clean the related keys under: HKEY_LOCAL_MACHINE \Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
Check the following registry key and clean all entries in the key, you will find:
HKEY_LOCAL_MACHINE \System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Thank you!
Maybe you are looking for
-
How can I disable the menu drop-down list on the back button?
I use a laptop and my hands are not too clever. Whenever I click on the 'back' button, I get the drop-down list, which means that I must then back up my hand to the pad (gently!) to move the pointer, and then try again. It may take me several attempt
-
I'm not sure if I have correctly implemented this code? (day and hour mode) sets, I want corresponding time stamp control with the mode appropriate to the day. For example: 05:00 morning 10:00 per day... and so on. My concern is with my implementatio
-
Windows xp sp 1, when I get to the step "I agree" after reading the license, nothing haapens aggremnet?
-
my hotmail account has been blocked, and I'm trying to recover it, but can't seem to enter the forum private to that effect. the link in the email that I received does not take me for a login to use the pin code that was given to me. where should I
-
I have windows vista Home premium 64-bit installed on my sony vaio cs36gj, which was not install updates. \niehter is running thing fixit. How updated?