Local virtual machines VMFS (upgrade process)

Similar Questions

• Add NT user to the Group Admin Local (virtual machine in a field)

  Are there any custom script that we could write to add NT user a local administrator of a virtual computer that is in a domain as well? Any ideas? Thank you.

  In what context have you used it? This code example is part of a larger solution, with specific steps...

  in fact, the only command that must be executed is the net localgroup... order... the code a little older a workflow where I picked up the text in a reg temp file and then imported the reg file... the reg file create a runOnce registry who was apparently alone running if you connect to the new virtual machine until a first domain administrator - is not ideal... but using ONLY the command net localgroup in there that's what I found to work more consistently.

• 'Create a snapshot of the Virtual Machine' suspended the process - how to kill?

  I tried to rename a virtual machine when I received a message from VCenter that "another task is already underway."

  I did some research and found that the virtual machine, I am trying to rename is currently creating a snapshot of the Virtual Machine.  Or - at least the host thinks Yes.

  The snap was initiated by vpxuser about 20:00 in the night a few days - and is still ongoing.  I can't kill him since the VIC when it is directly attached to the host.

  Looking to my data warehouses - I don't see that he actually created the snap, because I see no 0000001 or something like that.   At this point, I don't like, I don't know why he even launched the snap in the first place.

  Is there a way I can kill that process with the help of the console?   It's hosted on vSphere 4.

  Sven

  You have restarted these services on the host computer?

  service mgmt-vmware restart

  restarting the service vmware-vxpa

  • Kyle

• virtual machine hardware upgrade and tools with a script

  Hello

  I'm looking for the script to upgrade multiple machines virtual vmware tools and upgrading of hardware version in a script after you run the script below.

  Get - VM | Select ' Name,@{N='ToolStatus; E={$_. ExtensionData.Guest.ToolsStatus}} |

  C:\Tools-Report.csv - UseCulture - NoTypeInformation csv export

  Any help on this will be appreciated.

  Thank you

  vm2014

  In fact, that should be enough

  Import-Csv C:\Tools-Report.csv - UseCulture |

  where {$_.} {ToolStatus - don't [VMware.Vim.VirtualMachineToolsStatus]: toolsOk} | %{

  $vm = get - VM $_. Name

  Update-tools - VM $vm - NoReboot

  }

• Host CPU is not compatible with the requirements of the virtual machine in the level 0 CPUI register x 1 'ecx '.

  I have a cluster of three ESX servers.  They are IBM 3650 and they are the exact same material bought at the same time.  They even the same exact versions of the firmware (bios, bmc, nic firmware, HBAs, raid, HDD firmware, rsa, etc.).  I started their reclassification of ESX 3.5u3 to ESX4 with all the latest patches.  Then I updated one moved some top vm and upgraded vmware tools and virtual materials without problem.  So, I went and upgraded the following ESX Server and has started moving the machines on that one and upgraded vmware tools and virtual hardware.  I tested the functionality of the ESX servers and they seem to work fine.  I vmotioned machine version 4 hardware virtual machine between the two developed level ESX host very well so I me with the upgrade process.  Then I had to vmotion, one of the virtual machines updated (version 7 of material) between the two ESX hosts newly improved and they won't vmotion.  It gives me the error CPU host is not compatible with the requirements of the judgment of the VM to CPUID level register 0 x 1 'ecx '.  The full error message is in the attachment.

  Apparently, the virtual machine hardware upgrade exposed a few additional things virtual machine that prevents vmotion to work.  I don't know what and I'm quite surprised because these machines are identical identical hardware and firmware.

  All of the suggestions.

  This is a known unfortunately problem

  http://KB.VMware.com/kb/1011294

• What is the difference between a virtual machine cloning and v2v conversion to a virtual machine

  What is the difference between a virtual machine cloning and v2v conversion to a virtual machine

  Cloning process is to duplicate a VM. V2V is deploy vm on vsphere environment to another virtual machine format (example: the workstation, hyper-v).

• black screen, when you open the virtual machine console

  Hi guys need help in answering the following questions:
  When you open the console of the virtual machine, the connection process is fine, but it stops at a black screen

  

  That's what I use:
  (1) Windows 7 x 32
  VMRC 2) 5.1.0.20447
  (3) Mozilla Firefox 18.0.1
  (4) VMware vSphere Client 5.1
  (5) Vcloud 5.1.0.810718

  Here is my log:

  13/01/29 10:15:42.100 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:42.101 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, VMRC_EVENT_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}"ID - 2 modes - message mode has 2-3
  29-01-2013 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:42.103 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:42.832 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C]}
  29-01-2013 10:15:42.833 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:42.845 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379] 10:15:43.901: control of the VM has not been created
  29-01-2013 10:15:43.902 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:15:43.909 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.909: control of the VM has not been created
  29-01-2013 10:15:43.923 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.923: control of the VM has not been created
  29-01-2013 10:15:43.925 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.925: control of the VM has not been created
  29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:44.275 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, VMRC_EVENT_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}"ID - 2 modes - message mode has 2-3
  29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:44.276 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:44.958 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD]}
  29-01-2013 10:15:44.959 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:44.970 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 10:15:46.770 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:46.770 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, VMRC_EVENT_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance ID 'vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}' - mode 4 - message mode has 2-3
  29-01-2013 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:46.772 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/ScriptableObject.cc:321]: ID of property not found: onMessage
  29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/VmrcPlugin.cc:2548]: onMessage Manager call failed
  29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:47.380 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996]}
  29-01-2013 10:15:47.381 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:47.388 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 10:17:20.197 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:13.788 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:13.792 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:15.303 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:59:15.308 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:59:15.324 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.324: control of the VM has not been created
  29-01-2013 10:59:15.326 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.326: control of the VM has not been created
  29-01-2013 10:59:33.283 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:33.284: control of the VM has not been created
  29-01-2013 10:59:33.540 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:59:33.540 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3

  Windows 7 x 32

  That's kinda our old friend is back.

  Two checklists

  1. check the version of the VM VGA driver, if that's the case, you must update the WDDM driver display driver.

  2. make sure that you use HW 7 and more.

  More info here

• How to make a small virtual machine

  I have two virtual machines created with VMWare Workstation, which I'm running on another computer using VMWare Server. I need to send a colleague virtual machines, so it can debug problems that I pointed out, but virtual machines are simply too large. Each compressed (zipped) folder is 12 GB. I checked and the virtual disks are not previously affected - it says on the VMWare server. Change the disk option: "disk space is not preallocated for this virtual disk. Content of the virtual disk is stored in a single file. »

  I need to download the virtual machines and the process takes forever - I compressed the individual files and I'm trying to download the / 3GB zips one at a time, but it is still too slow.

  I checked the VMWare Tools | Tab Shrink and who is disabled with the message "Shrink is disabled for this virtual machine. Shrink is disabled for linked clones, parents of clones related, préalloués disks, snapshots and other factors. »

  Is it possible to do all of the smaller virtual machine file? I just want to share the virtual machine so that the problem can be reproduced and debugged... Best way to do this?

  Any help will be appreciated!

  I did this and was able to add the virtual computer to my inventory, start it and run "Shrink" of VMware Tools.

  He ran on the disks withou any error, however, the vmdk file size is the same as before you run Shrink: 16 GB. Is this correct? Does this mean that I can't not smaller than that?

  Assuming that Shrink in VMware Tools under VMware Server worked as it is supposed to...

  According to the vmware.log file disk hard virtual is a disc is 16 GB monolithicSparse (single growable file) and assuming that you used the option t 0 and not of t 2 when using vmware-vdiskmanager then if after a shrink operation is 16 GB in size at first thought I would say that the disc was full however consider what follows.

  How much free space is reported when you look at the properties for the C: drive in Windows Explorer (to the breast of the guest)?

  In General, the amount of used space is the size, it should be after a shrink operation.

  There are a few thing that can be done to help reduce the final size before shrinking...

  IIRC in Windows Vista, the system restore default to 15% of the size of the hard drive so purging the Restore Points could save as much as 2.4 GB on a 16 GB drive.

  Purge the cache of the browser (I.e. the temporary Internet files in Internet Explorer).

  Delete the contents of the file folder and C:\Windows\Temp.

  Disable Hibernation and delete the C:\hiberfil.sys (hidden by default) file because this file is the size of the amount of RAM to the virtual machine is affected.

  There is more that can be done which has already been mentioned however covers the main sectors that can decrease the shrunken size of a virtual hard disk.

• ESXi 4.1 upgrade to ESXi 5.5 while all virtual machines and data warehouses

  We have two servers ESXi 4.1.0 348481 (Essentials) and we need to upgrade to ESXi 5.5 for support of Windows Server R2 2012. We intend to use the interactive upgrade. We want to ensure that the virtual machine is preserved. More precisely VMFarm001 where ESXi is installed in the same data store as VMServer1. VMServer1 is our largest server and cannot be migrated to another data store easily because we are not allowed for vMotion.

  The following layout

  VMFarm001

  Dell PowerEdge R710

  Data store:

  Storage1 - 1.36 TB

  VMServer1 - MS Server 2003

  Install ESXi

  Storage2 - 1.82 TB

  VMServer2 - MS Server 2008 R2

  VMServer3 - MS Server 2008 R2

  VMFarm002

  HP ProLiant ML350 G5

  Data store:

  Storage1 - 95GB

  Install ESXi

  ISOs

  Storage2 - 1.82 TB

  VMServer4 - MS Server 2008 R2

  VMServer5 - MS Server 2008 R2

  I have a feeling I'm worried for nothing given that option during the ESXi upgrade and keep the VMFS datastore.

  Thank you

  Yes, that's correct.

  I recently finished the upgrade of lots of stand-alone hosts ESXi 4.1 (with local storage only) to 5.1 and all were successful. The same process applies to 5.5, so you shouldn't have a problem with preservation of VMFS data warehouses (and all virtual machines).

• Update Manager upgrade of the ESXi host that he is running in a virtual machine does

  That is the question.  Here is some information.  We were a completely virtualized environment for several years.  2 guests ESXi collocated 5.5 to different data centers connected of course by a VPN site-to site.  The VPN itself is provided by VMs and vCenter runs in a VM to one of the sites as Update Manager is to proceed with installing it. If the vCenter and/or VPN VMs are down, we have a very cool backup method to gain access to and manage ESXi and its console.   Some of you who read the rest of the present will be tempted to suggest to architecting our environment differently, but we are very pleased with the way it is thank you very much :-)  Appreciate all the answers but really just responded to this specific question.

  The reason why we want to Update Manager is really just to be able to upgrade easily ESXi in the future without enter in the console and the execution of orders, etc.  I realize the documentation and blogs on this topic that ESXi may need to go into maintenance mode and stop the virtual machines running on it (not a cluster if no migration) how ESXi is lose connection to the Update Manager (if the remote host) or a stop Update Manager (if the local host).  So the question is, is that the process of updating managed by Update Manager an atomic operation at that crucial moment or a sequence of operations depend on continuous connectivity and control of Update Manager.  Ddoes ESXi, then perform the upgrade and restart regardless - that would be great - or he'll just stand there in maintenance mode to learn more about disconnected now / stop Manager update pending.

  Your answers are greatly appreciated.

  Please, tell me if I understand you:

  Ask yourself if you can upgrade the host running Update Manager VM? And you cannot migrate the virtual to another host machine because there is no cluster in place and no shared storage?

  If your answer is YES to both questions, I can tell you that you cannot use Update Manager, since you must put your host in Maintenance Mode and therefore you will need to stop all virtual machines running, including the VM Manager Update.

• All of my virtual machines are "busy" after upgrading Linux

  I upgraded from Slackware64 13.37 abreast (close enough to the new version 14.0 - kernel 3.2.29) and installed vmplayer 5.0.0 build-812388.

  Vmplayer installation was possible with the "-ignore-errors option, like the previous version."

  When I try to play any of my images .vmx, I always get an error "the virtual machine is busy.".

  In the windows client, vmplayer creates a directory of "lck" with a lock file '.lck"in there.

  Remove this file does not resolve the issue.  If I don't remove this file and try to run the virtual machine again, vmplayer leaves.

  When running from the command line, I get this:

  vmplayer $ Windows_7.vmx
  Login to /tmp/vmware-lupe/vmware-modconfig-24735.log
  file name: /lib/modules/3.2.29/misc/vmmon.ko
  support: external
  License: GPL v2
  Description: monitor Machine virtual VMware.
  Author: VMware, Inc..
  depends on:
  vermagic: 3.2.29. mod_unload SMP
  Abandoned

  The above mentioned log file:

  2012 09-26 T 16: 53:01.299Z | vthread-3 | I120: Log for VMware Workstation pid = 24735 version = version 9.0.0 Build = build-812388 option = output
  2012 09-26 T 16: 53:01.299Z | vthread-3 | I120: The process is 64-bit.
  2012 09-26 T 16: 53:01.299Z | vthread-3 | I120: Host codepage = ISO-8859-1 encoding = ISO-8859-1
  2012 09-26 T 16: 53:01.299Z | vthread-3 | I120: Host is Slackware Linux 3.2.29. 14.0
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: Msg_Reset:
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: ----------------------------------------
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: Msg_Reset:
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / home/lupe/.vmware/config ': no such file or directory.
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: ----------------------------------------
  2012 09-26 T 16: 53:01.298Z | vthread-3 | I120: Optional preferences PREFS not found in home/lupe/.vmware/config file. Using the default values.
  2012 09-26 T 16: 53:01.299Z | vthread-3 | W110: Connecting to /tmp/vmware-lupe/vmware-modconfig-24735.log
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Reading in info for the vmmon module.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Reading in info for module vmnet.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Reading in info for the vmblock module.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Reading in info for vmci module.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Reading in info for the vsock module.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Definition of vsock to depend on vmci.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Created new pathsHash.
  2012 09-26 T 16: 53:01.307Z | vthread-3 | I120: Modinfo calling over 'vmmon.
  2012 09-26 T 16: 53:01.309Z | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012 09-26 T 16: 53:01.309Z | vthread-3 | I120: Modinfo invoking on "vmnet".
  2012 09-26 T 16: 53:01.311Z | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012 09-26 T 16: 53:01.311Z | vthread-3 | I120: Modinfo invoking on 'vmblock '.
  2012 09-26 T 16: 53:01.312Z | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012 09-26 T 16: 53:01.312Z | vthread-3 | I120: Modinfo calling over 'vmci.
  2012 09-26 T 16: 53:01.314Z | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012 09-26 T 16: 53:01.314Z | vthread-3 | I120: Modinfo calling over 'vsock.
  2012 09-26 T 16: 53:01.315Z | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.

  He complains about parameters and a missing config file but load the default values.

  I see nothing more that show some kind of error.

  How can I solve this?

  You must load modules into the kernel:

  vmware-modconfig --console --install-all
  
  Older versions do it automaticly but for some reason i don't know you have to do it manually.
  

• upgrade from version 4 to version 7 virtual machine

  Hi all

  Thanks for the support you provide

  I plan to upgrade my VMs running in version 4 to version 7. Is there a step by step procedure that must fallow? Please let me know if any body has any difficulty in it. I need to know about the upgrade NIC & SCSI adapter in virtual machines in particular. Please see the light on my notebooks.

  Concerning

  tdsk.

  Scott lowe also made a great step by step how to upgrade your virtual machines to version 7 and make the most of the new features with HW version 7 here: http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/

• upgrade required Fusion 1.1 to 2.0.5 lost initial virtual machine environment and Windows data... no help on a recovery?

  Thank you for taking the time to read.

  My brand new MacBook Pro came pre-installed with VMWARE Fusion intentionally, so I could run a Windows XP environment to migrate from the 10 years of content from Outlook to Entourage. Everything worked very well when one day, VMWARE said that I had to upgrade. I did and have not been able to run a Windows environment since. My Outlook and Windows configuration data is not available and I have 4 attempts to vmwarevm. When I try to load the original VM, I get an error/warning message: "this virtual machine is obsolete." It's the guest who has begun the process of upgrading to 2.0.5.

  I need access to my first setup of Microsoft Office and Outlook. no indication on how to access my previous data would be great.

  Thanks for any help at all!

  Kind regards

  Jeff

  The error"The VMware Tools resume script did not run successfully in this virtual machine. "is the crux of the problem here...

  I could try to delete the files from the virtual .vmss machine and see if you can connect.

  Right-click on the Virtual Machine window computer virtual library > show in Finder

  Make a right click the .vmwarevm bundle > Show Package Contents

  In this window, trash all .vmss files, and then try and turn on the Virtual Machine.

  Note that this is the same as pulling the plug on a physical pc stuck/frozen.

  Let us know if this helps =)

• Size of the virtual machines on the local data store

  What is the best way to determne the (total) disk space using a virtual machine? We have several virtual machines on local data warehouses and would like to estimate roughly how much disk space to the total number of virtual machines use to caculate how much storage SAN, they will consume. Is there an 'easy' way to socket this information?

  The most accurate way would be to calculate the total space used by the virtual machine files in the data store.

  Connect to the service console

  Navigate to the vmfs volume

  Navigate to the vm folder

  -h.

  This will give you files for this particular virtual machine related to the amount of disk space used by all the vm

  Méhul

• The former "cannot change the power state of virtual machine: the process has exited with an error: end of the error message" thing again (Fedora 8/Server 1.08)

  OK, this problem beautifully undescriptive I've seen caused by what seems to be dozens of things happening for me.

  I made the mistake of horrible update my FC8 kernel to the latest one (2.6.26.8 - 57.fc8).  Mind you, that's all that's changed.  It was with a 1.06 server with happiness and perfectly good computers running virtual in use before the upgrade.

  After the new kernel and reboot, I had to rebuild vmmod.  I had to get a fix of any - any later that I used with my previous kernel (116 does not solve the problem of compiling) so I used all-any117d.  Update like a champion.

  Try to turn on a VM and Ihanta!, the above error.

  Nothing else was changed.

  I tried the upgrade to VMware Server 1.08.  Used all-new any117d - update OK.

  Error again.

  I have re-run the compilation, this time to say 'yes' to what the installation script to "adjust the permissions of all virtual machines in xxxlist" or whatnot.

  Error again.

  1. status of /etc/init.d/VMware

  Networking networking on/dev/vmnet0 is running

  Invited only on/dev/vmnet1 network is running

  Network invited only on/dev/vmnet8 is running

  NAT networking on/dev/vmnet8 is running

  Responsible vmmon module

  Loaded module Vmnet

  FWIW, I compile as long as root, but have always run VMware server from my UID nonroot.

  What now?

  I'm in the same boat.  Fedora 8 2.6.26.8 - 57.fc8 #1 SMP

  I have tried uninstalling/reinstalling v1.0.6 thru 1.0.8 with all 116 updates and 117d.   117D compiles with every version of server but when I try to turn on a virtual computer I get this error.

  Cannot change the power state of virtual machine: the process has exited with an error:

  vmxvmdb: name of the Index generated by the configuration file

  POST (no connection): Version mismatch with vmmon module: expected 138.0, obtained 168.0.

  You have a bad version of the module kernel "vmmon.

  Try reinstalling VMware Server.

  POST (no connection): failed to initialize the surveillance apparatus.

  Failed to initialize the virtual machine.

  End of the error message.

  I found several posts other people have this problem but

  they are months with no recent activity and nothing that solved the problem.  I found appeared

  to get a fix, one updated the all an update that corrects the problem for

  2.6.26 performing several nuclei, but the link for the update on TI-psycho appears to be dead.  Here is the link to the discussion

  http://Fedoraforum.org/Forum/showthread.php?t=199026&page=2

  Of course, I would like to know how to solve this problem as well.

  Thank you