ESXi host goes to the State and the virtual machine does not restart on other host does not

Similar Questions

• Avalibale features in the free ESXi version - auto start the virtual machine and scripts shoutdown?

  Hey all,.

  Evaluating 60A expired on my ESXi (5.0.0.623860) host which runs a couple of virtual machines. Virtual machines have been setup to autostart when the host said, but now the assessment is complete, the virtual machine no longer autostart.

  In addition, I ran a simple scipt using PowerCLI. This was shot issue a stop host command, which in turn stop the gracfully VMs, then stop the host: the script command were:

  Connect-VIServer -server mysESXiHost -User root -Password xxxxxxx
  Stop-VMHost mysESXiHost -Confirm:$false -force
  

  If I run these commands from the PowerCLI confirmation, I see the following error message:

  Stop-VMHost : 08/12/2012 17:01:52    Stop-VMHost        fault.RestrictedVersion
  .summary
  At line:1 char:12
  + Stop-VMHost <<<<  mysESXiHost -Confirm:$false -force
      + CategoryInfo          : NotSpecified: (:) [Stop-VMHost], RestrictedVersi
     on
      + FullyQualifiedErrorId : Client20_VmHostServiceImpl_ShutdownVmHost_ViErro
     r,VMware.VimAutomation.ViCore.Cmdlets.Commands.StopVMHost
  

  What I read, I thought that current same ESXi of execution in the free license must always let these things happen, or am I wrong?

  Chris

  There are two things to note:

  (1) the fault of . RestrictedVersion.summary details can be found here http://www.virtuallyghetto.com/2011/06/dreaded-faultrestrictedversionsummary.html

  (2) regarding Auto Start, fairytale look here http://blogs.vmware.com/vsphere/2012/07/clarification-on-the-auto-start-issues-in-vsphere-51-update-1.html

• In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

  Hello

  Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

  I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke"»

  I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

  FYI: we have changed the domain 3 months ago, but it has never be a problem.

  I have google and search several Forum. So far, I tried to:

  -restart the service vmware-auth as an administrator

  -launch vmware.exe administrator

  stop/start the vmx86 service

  -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

  -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

  -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)
  

  -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

  -Open the virtual machine using the drive == > does not work either.

  This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

  Even a newly created WM (boneless), unbootable! :-(

  *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

  I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

  Of after what I saw (and what little I understand), it's as if the CPU is not detected?

  The two newspapers have this line:

  FeatureCompat: EVC masks:

  but the non-working goes - we with

  Module CPUID initialization failed.

  While working it display information on CPU (hostCPUID name / family / type... etc...)

  Any idea is welcome.

  I'll answer me to my problem!

  A lot of research to this knowledge.

  In summary: don't mess with the processor affinity... or keep it in mind!

  Response to distinguish:

  I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

  This is the reason of *my* question. Perhaps it might help someone else?

  TIPS:

  For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

  Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

  ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

  15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

  LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

  Post edited by: cbiero (LSB and MSB...)

• NPIV enabled on the virtual machine, but not seen in the comments

  Hello

  I have a 5.0 with an HBA qlogic esxi. I created a VM and rhel is installed.

  Then I activated the npiv on this virtual machine and saw that it generated node WWN and port WWN.

  However, when I logged in the comments, I am not able to see the names of ports in

  / sys/Class/scsi_host/Host {n} / device / fc_host:host {n} / port_name

  Are there additional configuration on the side of the virtual machine to allow the WWNS within the guest?

  Thanks in advance.
  

  Hello

  This is a very detailed description of all the required tasks for use with VMware NPIV.

  NPIV: N-Port ID Virtualization

  Kind regards

  Ralf

• Windows on VM - says my copy of Windows 7 on the virtual machine is not authentic

  I have the Virtual Machine on a Mac and am running Windows 7 on the virtual machine.  I get a message that my copy of windows is not genuine, so, how do I get a product key.
  I get a message from Microsoft that this copy of Windows is not supported.  If I need to buy Windows overall, how can I download it to VM?

  You can purchase a license for the edition you installed and change the key and activate it on the Internet.

  http://www.Microsoft.com/Windows/buy/default.aspx

  http://Windows.Microsoft.com/en-us/Windows7/get-a-new-Windows-product-key

  Click Start, right click on computer

  Click on properties

  Scroll down to the Windows Activation

  Click on the link "change product key".

  Enter the product key and click next to activate via the Internet.

• AutoSave is slow when the virtual machine is not active

  When I actively use a Windows 2000 Server VM and AutoSave is triggered, it's very fast.  But if I did not use the virtual machine for a while, it takes some minutes and minutes.  If I'm trying to go back to the virtual machine, I have to wait indefinitely for the automatic backup complete.

  Is it possible to set the priority for the automatic backup feature?

  Are you talking about VMware Fusion AutoProtect feature, or something else (perhaps in the comments)? Offhand, it seems that when you have not used within a certain time, Fusion got paged out. Taking the automatic snapshot requires paging backward, which can take some time. You can test this theory by looking at activity monitor and looking at the pageout/publication numbers when you see an automatic preview slow.

  Pageouts and pageins are controlled by OS X and not something we have control over. Adding RAM to the Mac, it is more likely merger will stay in memory and avoid this situation.

• With instant full VM LUN and now the virtual machine will not start or register

  Hello

  I have a case here, where we have a virtual machine that quickly filled the logic unit number and the snapshot is currently 110 GB. It is now available on the new LUN space, but the VM does not start and he was also addressed as 'unknown' in the viclient. I tried to cancel the registration and check-in again, but he refuses to register. It seems that the snapshot is damaged.

  When you try to save it, I get the following in hostd.log:

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': (17) successfully opened size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': open with success (21) size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  Referred to as registry: AXAPTA/AXAPTA.vmx

  Vmsvc indicates file is loaded, by: /vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA.vmx

  I also tried to copy virtual machines directory down to a local PC and run via VMware Converter, but I get the message "the source VMware Consolidated Backup"filename.vmx"has a missing catalog file.

  1. VMware - v

  VMware ESX Server 3.5.0 build-130756

  Any help is appreciated.

  Lars

  The problem (according to the newspaper) is AXAPTA_1-000001 - delta.vmdk no AXAPTA_1-000002 - delta.vmdk (the error on the second snapshot is probably because of the broken parent snapshot).

  The descriptors are ok, which means that the VMDK itself is broken.

  If you do not have a backup, you can try the following:

  -Copy the files in another data store

  -change the second snapshot descriptor to point to the basedisk as the parent

  -Try and mount the drive

  -If you're lucky, you should be able to recover at least some data of

  -If the disklib is complaining again then the two snapshots are broken - which is unlikely

  Depending on how old the second snapshot (the older one is better it is) the method above will not help.

• ROM of the Virtual Machine is not supported

  I have a VMware ESXi 4 environment where I'm currently under several SLES 11 virtual machines with FT.  I went to activate FT another, but when I try and enable it, I see this error:

  -ERROR task-2477-vm-1033 - vim. VirtualMachine.createSecondary: vim.fault.VmConfigIncompatibleForFaultTolerance:

  {(vim.fault.VmConfigIncompatibleForFaultTolerance)

  dynamicType =,

  MSG = 'Device 'Virtual machine ROM' is not supported.',

  },

  MSG = "Configuration of virtual machine for the no fault tolerance."

  }

  I looked around, but couldn't understand what he complains.  I compared the configuration to the other SLES11 VMs I have under my feet, but I don't see the difference.  Thank you!

  Matt

  Hello.

  You have VMI or paravirtualization, activated in this guest SLES?  It is not supported with FT.

  Good luck!

• Discover the virtual machine with VMware View 4.5.  "That underlies the virtual machine is not available.

  I have installed the following to an ESX 4.1 server:

  -VMware View connection server (Server 2008 R2 Ent)

  -V - Center (Server 2003 Std)

  Install the VMware Client with Local Mode 4.5 to a laptop

  Installed VMware Agent to a Windows XP and Win7 is a guest vm on the ESX Server.

  I can connet with success both of these machines.

  When I try to extract either of these machines, I get the error message after 2% saying, "underlying this desktop virtual machine is unavailable.

  

  Can someone tell what to do to solve this problem?  I can't find anything so far for this error.

  Thank you

  Did you install and configure a forwarding server?

  -Mike

• Windows Server 2003 physical to the virtual machine does not start

  I have converted a windows server machine 2003 virtual machine image.  Conversion completed successfully but the machine image custom virtual boot I get the blue screen of death which is probably do the scsi driver being changed during the conversion of my question is: how to install these drivers once the pc has been converted? I try to avoid to do from scratch with constraints of time it takes to get this virtual image starts, please help

  Semper Fi

  You must use SCSI.  Replace your SCSI controller during the conversion.

  ... also, I'm under the assumption that the destination ESX (i)?

• Register the virtual machine does not properly

  I run the following script, but it does not work as expected.

  $ESXHost = 'test - 01.Test.com '.

  $ResourcePool = get-VMHost $ESXHost | Get-ResourcePool | Get-View
  $vmFolder = get-View (Get-data center-name $Datacenter |) Get - Folder - name "vm") user.user
  $vmFolder.RegisterVM_Task ("[TIER2_VMSHARED_LASCX02_LUN2017]" + $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $null ")

  When the script is run, it saves the VM on Test-04?  Any suggestions?

  E4F

  The last parameter to RegisterVM_Task is the host where you want the guest to save.

  You pass $null, so DRS will decide for you.

  If you want a specific host, you can do

  $ESXHost = "Test-01.Test.com"
  $esx = Get-VMHost -Name $ESXHost $ResourcePool = $esx | Get-ResourcePool | Get-View $vmFolder = Get-View (Get-Datacenter -Name $Datacenter | Get-Folder -Name "vm").id
  $vmFolder.RegisterVM_Task("[TIER2_VMSHARED_LASCX02_LUN2017] " +  $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $esx.Extensiondata.MoRef)
  

• Alarm, based on the State of the virtual machine

  Hello

  I just started to evaluate the vFoglight to monitor our infrastructure VMware and so far, I really like the product, but there are a lot of things to take.

  Y at - it a predefined alarm that will enhance and alert and send me an email if a virtual machine crashes or goes offline? The default rule "VMW Virtual Machine power status change" will do that?  I feel that this will tell me if the virtual computer is shut down or restarted, but could not workout if it marked the top if a virtual machine has frozen or crashed.

  In the past I did using the base "no heartbeat Mike" in vsphere.

  Any help would be appreciated

  Thank you

  Dan

  Hi Dan,.

  The Virtual Machine VMW power state change will do as below:

  Goal
  This rule triggers an alarm if a virtual machine has been suspended or powered down recently.

  The rule definition
  Conditions                                                                                           State   Action
  The virtual machine was not suspended or updates turned off recently.     Normal no
  The virtual machine has been suspended recently.                               No warning
  The virtual machine has been powered down recently.                                Reviews email VMware admin

  Maybe you can add, action of e-mail to the severity of the warning from the rule.

• Crash when the instant withdrawal: State of the virtual machine is 'unknown (invalid) '.

  Hi all

  Currently, I'm in the middle of a nightmare: a few moments I tried to delete a snapshot that has been there for a while on one of my virtual machines. Of course, it can take a loy of time for this kind of operation to achieve, so I waited patiently so that it reaches its end.

  But in the middle of it my host had a kernel panic (I'll have to diagnose this one).

  When I got to new host, the virtual machine was not the webui, try saving it shows the machine as being "unknow (invalid)"...

  I scoured Suur intrenet for a while, but everything I have read until knowledge is quiet frightneging.

  Currently, the directory that stores all the files of the virtual machine is looking as follows:

  drwxrwxrwx 2 root root 4096 12 October 2008 564d583c-363e-0c7a-96e0-cd07d5b1a8e1.vmem.lck

  -rw - 1 root root 2147221504 2 May 20:31 colossus2_2new - f001.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_2new - f002.vmdk

  -rw - 1 root root 1074266112 Jan 11 22:27 colossus2_2new - f003.vmdk

  -rw - 1 root root 528 2 May 20:31 colossus2_2new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f003.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_3new - f004.vmdk

  -rw - 1 root root 2147221504 Jan 11 22:35 colossus2_3new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:35 colossus2_3new - f006.vmdk

  -rw - 1 root root 661 2 May 20:32 colossus2_3new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_4new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:34 colossus2_4new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:35 colossus2_4new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:42 colossus2_4new - f006.vmdk

  -rw - 1 root root 661 2 May 20:35 colossus2_4new.vmdk

  -rw - 1 root root 1868365824 2 May 22:13 colossus2_5new-000001 - s001.vmdk

  -rw - 1 root root 1637482496 2 May 22:13 colossus2_5new-000001 - s002.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s003.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s004.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s005.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s006.vmdk

  -rw - 1 root root 2096824320 2 May 22:13 colossus2_5new-000001 - s007.vmdk

  -rw - 1 root root 554369024 2 May 22:13 colossus2_5new-000001 - s008.vmdk

  -rw - 1 root root 1728839680 2 May 22:13 colossus2_5new-000001 - s009.vmdk

  -rw - 1 root root 2114191360 2 May 22:13 colossus2_5new-000001 - s010.vmdk

  -rw - 1 root root 1659371520 2 May 22:13 colossus2_5new-000001 - s011.vmdk

  -rw - 1 root root 1527775232 2 May 22:13 colossus2_5new-000001 - s012.vmdk

  -rw - 1 root root 1578958848 2 May 22:13 colossus2_5new-000001 - s013.vmdk

  -rw - 1 root root 1611792384 2 May 22:13 colossus2_5new-000001 - s014.vmdk

  -rw - 1 root root 1602945024 2 May 22:13 colossus2_5new-000001 - s015.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s016.vmdk

  -rw - 1 root root 2085617664 2 May 22:13 colossus2_5new-000001 - s017.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s018.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s019.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s020.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s021.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s022.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s023.vmdk

  -rw - 1 root root 132055040 2 May 22:13 colossus2_5new-000001 - s024.vmdk

  -rw - 1 root root 327680 2 May 22:13 colossus2_5new-000001 - s025.vmdk

  -rw - 1 root root 65536 2 May 22:13 colossus2_5new-000001 - s026.vmdk

  -rw - 1 root root 1582 Mar 8 17:53 colossus2_5new - 000001.vmdk

  drwxrwxrwx 3 root root 4096 2 May 22:14 colossus2_5new - 000001.vmdk.lck

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:37 colossus2_5new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:38 colossus2_5new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:39 colossus2_5new - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:41 colossus2_5new - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f007.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f008.vmdk

  -rw - 1 root root 2147221504 2 May 20:43 colossus2_5new - f009.vmdk

  -rw - 1 root root 2147221504 2 May 20:45 colossus2_5new - f010.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f011.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f012.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f013.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f014.vmdk

  -rw - 1 root root 2147221504 2 May 20:48 colossus2_5new - f015.vmdk

  -rw - 1 root root 2147221504 Feb 11 13:19 colossus2_5new - f016.vmdk

  -rw - 1 root root 2147221504 8 Mar 17:17 colossus2_5new - f017.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:02 colossus2_5new - f018.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f019.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f020.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f021.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_5new - f022.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:04 colossus2_5new - f023.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f024.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f025.vmdk

  -rw - 1 root root by 6553600 Jan 11 23:05 colossus2_5new - f026.vmdk

  -rw - 1 root root 1562 2 May 20:35 colossus2_5new.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f007.vmdk

  -rw - 1 root root 1075576832 2 May 20:31 colossus2 - f008.vmdk

  -rw - 1 root root 8684 2 May 20:19 colossus2.nvram

  -rw - 1 root root 714 2 May 20:31 colossus2.vmdk

  -rw - 1 root root 821 2 May 20:31 colossus2.vmsd

  drwxrwxrwx 2 root root 4096 2 May 22:13 colossus2.vmsd.lck

  -rwxr-xr-x 1 root root 2680 may 2 21:35 colossus2.vmx

  -rw - 1 root root 264 Jan 11 22:25 colossus2.vmxf

  -rw - rr 1 root root 98347008 1 October 2008 gparted-live - 0.3.9 - 4.ISO

  -rw - rr 1 root root 1581428 Jan 13 11:53 0.log - vmware

  -rw - rr 1 root root 771239 19 Dec 12:59 vmware - 1.log

  -rw - rr 1 root root 76388 Jan 11 23:21 vmware - 2.log

  -rw - rr 1 root root 10161063 2 May 20:18 vmware.log

  The vmx file contains the following:

  #! / usr/bin/vmware

  . Encoding = 'UTF-8 '.

  config.version = '8 '.

  virtualHW.version = "7".

  floppy0. Present = "FALSE".

  MKS. Enable3D = 'TRUE '.

  pciBridge0.present = 'TRUE '.

  pciBridge4.present = 'TRUE '.

  pciBridge4.virtualDev = "pcieRootPort"

  pciBridge4.functions = '8 '.

  pciBridge5.present = 'TRUE '.

  pciBridge5.virtualDev = "pcieRootPort"

  pciBridge5.functions = '8 '.

  pciBridge6.present = 'TRUE '.

  pciBridge6.virtualDev = "pcieRootPort"

  pciBridge6.functions = '8 '.

  pciBridge7.present = 'TRUE '.

  pciBridge7.virtualDev = "pcieRootPort"

  pciBridge7.functions = '8 '.

  vmci0. Present = 'TRUE '.

  NVRAM = "colossus2.nvram."

  virtualHW.productCompatibility = "hosted".

  FT.secondary0.enabled = 'TRUE '.

  Tools.Upgrade.Policy = "useGlobal".

  powerType.powerOff = 'soft '.

  powerType.powerOn = "hard."

  powerType.suspend = "hard."

  powerType.reset = 'soft '.

  displayName = "colossus2."

  extendedConfigFile = "colossus2.vmxf".

  scsi0. Present = 'TRUE '.

  scsi0.sharedBus = 'none '.

  scsi0.virtualDev = "free".

  memsize = "4096".

  scsi0:0. Present = 'TRUE '.

  scsi0:0. FileName = "colossus2.vmdk".

  IDE1:0. Present = "FALSE".

  IDE1:0. FileName = ' / vmachines/colossus2/gparted-live-0.3.9-4.iso '.

  IDE1:0. DeviceType = "cdrom-image".

  IDE1:0.allowGuestConnectionControl = "FALSE".

  ethernet0. Present = 'TRUE '.

  ethernet0.allowGuestConnectionControl = "FALSE".

  ethernet0. Features = "1".

  ethernet0.wakeOnPcktRcv = "FALSE".

  ethernet0.networkName = "Bridged".

  ethernet0. AddressType = 'generated '.

  guestOS = "rhel3.

  UUID. Location = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  UUID. BIOS = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  VC. UUID = "52 88 6f 19 b2 66 ae 20-28 5 c 6 b 8 b 96 a1 15 6 d.

  scsi0:1.present = 'TRUE '.

  scsi0:1.filename = "colossus2_2new.vmdk".

  scsi0:1.writeThrough = 'TRUE '.

  scsi0:2.present = 'TRUE '.

  scsi0:2.filename = "colossus2_3new.vmdk".

  scsi0:2.writeThrough = 'TRUE '.

  scsi0:3.present = 'TRUE '.

  scsi0:3.filename = "colossus2_4new.vmdk".

  scsi0:3.writeThrough = 'TRUE '.

  scsi0:4.present = 'TRUE '.

  scsi0:4.filename = "colossus2_5new - 000001.vmdk".

  scsi0:4.writeThrough = 'TRUE '.

  IDE1:0.startConnected = 'TRUE '.

  IDE1:0.clientDevice = "FALSE".

  ethernet0.generatedAddress = "00: 0C: 29:b1:a8:e1.

  tools.syncTime = "TRUE".

  scsi0:0. Redo = «»

  scsi0:1.redo = «»

  scsi0:2.redo = «»

  scsi0:3.redo = «»

  scsi0:4.redo = «»

  vmotion.checkpointFBSize = "16777216.

  pciBridge0.pciSlotNumber = "17".

  pciBridge4.pciSlotNumber = "21".

  pciBridge5.pciSlotNumber = "22".

  pciBridge6.pciSlotNumber = "23".

  pciBridge7.pciSlotNumber = "24".

  scsi0.pciSlotNumber = "16".

  ethernet0.pciSlotNumber = "32".

  vmci0.pciSlotNumber = "33".

  ethernet0.generatedAddressOffset = '0 '.

  vmci0.ID = "-709777183".

  sched.mem.pshare.Enable = "FALSE".

  mainMem.useNamedFile = "FALSE".

  MemTrimRate = '0 '.

  MemAllowAutoScaleDown = "FALSE".

  Could someone point me to a solution if there is? I have Saturday night here and I would not spend my Sunday to rebuild the server from scratch and have to explain Monday morning I lost 2 months of work for users little by relying on this virtual machine.

  Thank you very much in advance!

  bugjargal,

  In the past if I had a VM that is displayed as invalid when you try to add it to the inventory, I usually just created a new virtual machine based on the original settings & attached the existing VMDK.  Not sure how that will work with a virtual machine that has snapshots, but can be worth (nothing to lose)?

  Doug.

• Virtual machines do not get IP address from the DHCP server

  Hello! I just spend Xenserver to ESXi. Created a couple of virtual machines and none of them gets an IP address from our DHCP server (DHCP server is a physical PC), and instead, they get a number of internal 192.168.x.y allowing connection to the internet.

  Looks like a way to do this is to install a virtual machine that is a router, as M0n0wall, and route traffic to connect to the external network and finally to access internet. But this is not what I have to do.

  I need to have virtual machines that are server to get an IP reserved for our DHCP server, and then our local windows client should be able to access it directly.

  I searched on google and forums for this but I can't seem to find how to configure virtual machines to directly belong to our local network.

  I thought that VMware would have a simpler way to do so than XenServer, but I was stuck on this one day now and really frustrated as I get not before with this project, stuck on this little problem... sigh...

  Thanks for your help.

  GER.

  ESXi does not IP addresses to the virtual machines it host - if the virtual machines are not able to access your physical network than that of the thw two virtual machines acts as a DHCP server - now to the question of network - if you are not able to reach the virtual machines on the physical network or achieve fitness network virtual machines , then there is a problem with the physical connection to the ESXi host, possibly the configuration of the physical port that connects to the - is a way to test this theory to assign an IP address on the same network that the management port - if you are able to access the virtual machine, then you know that the problem is with the switch port.

• There is no reference of the virtual machine to the storage

  I have a virtual machine with a reference to a NFS read only the storage location.  But I can not find source of this reference.  I reviewed the parameters of the virtual machine, and there is no reference that I see.  The vmdk is not reference, nor is the SEO cd player.  To complicate matters, the nfs went offline and is no longer available.   I tried to delete the storage on the host computer in vcenter 5 (device), but could not because of the reference to the virtual machine.

  I connected the host computer in vsphere 5 and virtual machine did not have this reference.  The host had that nfs as a reference of storage, but the virtual machine is not, unlike in vcenter.  So I removed the storage on the host computer.  Back connected to vcenter and the virtual machine always has the reference for storage.

  5 Essentials ESXi

  vCenter Unit 5

  Welcome to the community,

  If I understand you correctly, you see the extra storage in addition to the correct storage for your virtual computer! This occurs if you created a snapshot, while the storage has been active for this virtual machine. Once you delete the snapshots storage displayed will be deleted also.

  André