Hi!

how to increase memory from esxi command line?

We have a virtual center which is virtual. We want to increase the memory. But we must take down the windows 2008 r2 (virtual center).

Hi,

I am new to VMware and just installed 4.1 ESXi update 2 on my Dell T7400. Every now and then, i am not able to connect via vSphere client with errors like "Connection closed by remote host"

If i restart the host, it will work for a while and then again vSphere client will loose connectivity.

Below is the details in log...let me know if something is wrong?

"[viclient:SoapTran:P: 3] 2012-08-22 11:40:51.278  Invoke 13 Start CreateInventoryView on ViewManager:ViewManager [132.253.77.200]. [operationID:E7CC4B39-0000000D][Caller: VmomiSupport.InventoryViewManager.Initialize]
[viclient:SrvMsg  :P: 3] 2012-08-22 11:40:51.278  RMI Request Vmomi.View.ViewManager.CreateInventoryView - 13
[viclient:QuickInf:W:25] 2012-08-22 11:40:51.279  WaitForUpdates Version =
[viclient:SoapTran:W:25] 2012-08-22 11:40:51.280  Invoke 14 Start WaitForUpdates on PropertyCollector:ha-property-collector [132.253.77.200]. [operationID:E7CC4B39-0000000E]
[viclient:SrvMsg  :W:25] 2012-08-22 11:40:51.280  RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 14
<version></version>
[        :QuickInf:P:34] 2012-08-22 11:40:51.296  Loading catalog 'C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\4.1\Catalogs\Default\vim\en\vm.vmsg' from C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\4.1\Catalogs\Default\vim\en\vm.vmsg
[viclient:Warning :P:32] 2012-08-22 11:40:51.314  Waiting Catalog Manager to load ...
[viclient:Warning :P:32] 2012-08-22 11:40:51.314  Waiting Catalog Manager to load ...
[viclient:Warning :P:32] 2012-08-22 11:40:51.314  Waiting Catalog Manager to load ...
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.345  Invoke 4 Finish CreateFilter on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.255, Server:000.157 [ERROR]
VirtualInfrastructure.Exceptions.ConnectionError: The request failed because the server '132.253.77.200' closed the connection. (The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.)
System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Server stack trace:
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
Exception rethrown at [0]:
...
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at VirtualInfrastructure.Soap.SoapWebRequest.OnGetResponse(IAsyncResult result)
System.IO.IOException: The decryption operation failed, see inner exception.
...
   at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
System.ComponentModel.Win32Exception: The message or signature supplied for verification has been altered

   --- End of inner exception stack trace ---

   --- End of inner exception stack trace ---

   --- End of inner exception stack trace ---
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodInvocationReturnHandler, MethodName, Object[])
   at Vmomi.Core.PropertyCollector.CreateFilter(FilterSpec, Boolean, MethodInvocationReturnHandler)
   at VirtualInfrastructure.Updates.PollerDispatcherImpl.CreateFilter(FilterCreationHandler, CreateFilterArgsInternal)
   at VirtualInfrastructure.Updates.ManagerImpl.CreateFilter(FilterCreationHandler, FilterSpec, Boolean, UpdatesHandler)
   at VmomiSupport.Permissions.ManagerImpl.CreateAuthorizationMgrFilter(AuthorizationManager)
   at VmomiSupport.Permissions.ManagerImpl.Initialize()
   at VmomiSupport.Permissions.ManagerImpl.VmomiSupport.PermissionsManager.set_Activated(Boolean)
   at VmomiSupport.VcServiceImpl.EnableManagers()
   at VmomiSupport.VcServiceImpl.PostLogin()
   at VmomiSupport.VcServiceImpl.Login(LoginSpec)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker, DoWorkEventArgs)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object, DoWorkEventArgs)
...
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)
[viclient:Error   :P:28] 2012-08-22 11:40:51.351  RMI Error Vmomi.Core.PropertyCollector.CreateFilter - 4
<Error type="VirtualInfrastructure.Exceptions.ConnectionError">
  <Message>The request failed because the server '132.253.77.200' closed the connection. (The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.)</Message>
  <InnerException type="System.Net.WebException">
    <Message>The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.</Message>
    <InnerException type="System.IO.IOException">
      <Message>The decryption operation failed, see inner exception.</Message>
      <InnerException type="System.ComponentModel.Win32Exception">
        <Message>The message or signature supplied for verification has been altered</Message>
        <ErrorCode>-2147467259</ErrorCode>
        <NativeErrorCode>-2146893041</NativeErrorCode>
      </InnerException>
    </InnerException>
    <Status>KeepAliveFailure</Status>
  </InnerException>
  <Title>Connection Error</Title>
  <InvocationInfo type="VirtualInfrastructure.MethodInvocationInfoImpl">
    <StackTrace type="System.Diagnostics.StackTrace">
      <FrameCount>23</FrameCount>
    </StackTrace>
    <MethodName>Vmomi.Core.PropertyCollector.CreateFilter</MethodName>
    <Target type="ManagedObject">PropertyCollector:ha-property-collector [132.253.77.200]</Target>
    <Args>
      <item type="Vmomi.Core.PropertyCollector+FilterSpec">
        <PropSet>
          <item type="Vmomi.Core.PropertyCollector+PropertySpec">
            <Type>Vmomi.AuthorizationManager</Type>
            <PathSet>
              <item>Vmomi.AuthorizationManager.roleList</item>
            </PathSet>
          </item>
        </PropSet>
        <ObjectSet>
          <item type="Vmomi.Core.PropertyCollector+ObjectSpec">
            <Obj type="ManagedObject">AuthorizationManager:ha-authmgr [132.253.77.200]</Obj>
          </item>
        </ObjectSet>
      </item>
      <item>False</item>
    </Args>
  </InvocationInfo>
  <WebExceptionStatus>KeepAliveFailure</WebExceptionStatus>
  <SocketError>Success</SocketError>
</Error>
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.418  Invoke 5 Finish CreateListView on ViewManager:ViewManager [132.253.77.200] - Serial:0.002, Server:000.253
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.425  Invoke 15 Start CreateFilter on PropertyCollector:ha-property-collector [132.253.77.200]. [operationID:E7CC4B39-0000000F][Caller: VirtualInfrastructure.Updates.PollerDispatcherImpl.CreateFilter]
[viclient:SrvMsg  :P:28] 2012-08-22 11:40:51.432  RMI Request Vmomi.Core.PropertyCollector.CreateFilter - 15
<spec type="Vmomi.Core.PropertyCollector+FilterSpec">
  <PropSet>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.Alarm.Alarm</Type>
      <PathSet>
        <item>Vmomi.Alarm.Alarm.info</item>
      </PathSet>
    </item>
  </PropSet>
  <ObjectSet>
    <item type="Vmomi.Core.PropertyCollector+ObjectSpec">
      <Obj type="ManagedObject">ListView:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52d24207-f283-c274-5d58-1ba37ea9fcf9 [132.253.77.200]</Obj>
      <SelectSet>
        <item type="Vmomi.Core.PropertyCollector+TraversalSpec">
          <Type>Vmomi.View.ListView</Type>
          <Path>Vmomi.View.ListView.view</Path>
        </item>
      </SelectSet>
    </item>
  </ObjectSet>
</spec>
<partialUpdates>False</partialUpdates>
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.464  Invoke 6 Finish CreateFilter on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.002, Server:000.271 [session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]527bf486-44a8-1ca9-d25c-177e6a438fb7]
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.467  Invoke 7 Finish CreateFilter on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.001, Server:000.270 [session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]527a49b3-914d-fd40-9f3f-4dbd9c837073]
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.479  Invoke 9 Finish Vmomi.Core.PropertyCollector.RetrieveContents(ServiceInstance:ServiceInstance [132.253.77.200]::Vmomi.ServiceInstance.capability) on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.012, Server:000.110
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.483  Invoke 11 Finish CreatePropertyCollector on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.001, Server:000.124
[viclient:SoapTran:P: 3] 2012-08-22 11:40:51.485  Invoke 13 Finish CreateInventoryView on ViewManager:ViewManager [132.253.77.200] - Serial:0.000, Server:000.011 [ERROR]
System.IO.IOException: Unable to read data from the transport connection: The connection was closed.
   at System.Net.ConnectStream.EndWrite(IAsyncResult asyncResult)
   at VirtualInfrastructure.Soap.SoapWebRequest.OnWrite(IAsyncResult result)
   --- End of exception stack trace ---
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])
   at Vmomi.View.ViewManager.CreateInventoryView()
   at VmomiSupport.InventoryViewManager.Initialize(UpdatesHandler)
   at VmomiSupport.InventoryDataImpl.Startup()
   at VmomiSupport.InventoryDataImpl.set_Activated(Boolean)
   at VmomiSupport.VcServiceImpl.InitVmomi(ErrorHandler)
   at VirtualInfrastructure.LoginMain.BeginInitializeVmomi()
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker, DoWorkEventArgs)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object, DoWorkEventArgs)
...
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)
[viclient:Error   :P: 3] 2012-08-22 11:40:51.486  RMI Error Vmomi.View.ViewManager.CreateInventoryView - 13
<Error type="System.IO.IOException">
  <Message>Unable to read data from the transport connection: The connection was closed.</Message>
</Error>
[viclient:QuickInf:P:28] 2012-08-22 11:40:51.491  PollerDispatcher for server: https://132.253.77.200/sdk enabled
[viclient:QuickInf:W:27] 2012-08-22 11:40:51.491  WaitForUpdates Version =
[viclient:SoapTran:W:27] 2012-08-22 11:40:51.491  Invoke 16 Start WaitForUpdates on PropertyCollector:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52b9ce1b-590a-6026-14a4-990f1f49a919 [132.253.77.200]. [operationID:E7CC4B39-00000010]
[viclient:SrvMsg  :W:27] 2012-08-22 11:40:51.491  RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 16
<version></version>
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.494  Invoke 8 Finish CurrentTime on ServiceInstance:ServiceInstance [132.253.77.200] - Serial:0.000, Server:000.269
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.552  Invoke 10 Finish Vmomi.Core.PropertyCollector.RetrieveContents(PerformanceManager:ha-perfmgr [132.253.77.200]::Vmomi.PerformanceManager.perfCounter) on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.027, Server:000.168
[viclient:SoapTran:W:25] 2012-08-22 11:40:51.567  Invoke 14 Finish WaitForUpdates on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.013, Server:000.063
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.568  Invoke 15 Finish CreateFilter on PropertyCollector:ha-property-collector [132.253.77.200] - Serial:0.005, Server:000.075 [session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52ae0fda-2007-3ec2-245f-48c655c859e3]
[        :Error   :P: 3] 2012-08-22 11:40:51.585  Internal Error during login
System.Reflection.TargetInvocationException: Unable to read data from the transport connection: The connection was closed.
   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
   at Vmomi.View.ViewManager.CreateInventoryView()
   at VmomiSupport.InventoryViewManager.Initialize(UpdatesHandler callback)
System.IO.IOException: Unable to read data from the transport connection: The connection was closed.
   at System.Net.ConnectStream.EndWrite(IAsyncResult asyncResult)
   at VirtualInfrastructure.Soap.SoapWebRequest.OnWrite(IAsyncResult result)

   --- End of inner exception stack trace ---
[VICnMngt:Critical:M:30] 2012-08-22 11:40:51.589  OnServiceEvent InternalError for https://132.253.77.200/sdk : Unable to read data from the transport connection: The connection was closed.
[        :ShowExcp:M:30] 2012-08-22 11:40:51.596  Error: Unable to read data from the transport connection: The connection was closed.
Exception already logged, summary: System.Reflection.TargetInvocationException:Unable to read data from the transport connection: The connection was closed.
[viclient:SoapTran:P:21] 2012-08-22 11:40:51.599  Invoke 12 Finish CreateContainerView on ViewManager:ViewManager [132.253.77.200] - Serial:0.003, Server:000.238
[viclient:SoapTran:P:21] 2012-08-22 11:40:51.607  Invoke 17 Start CreateFilter on PropertyCollector:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52b9ce1b-590a-6026-14a4-990f1f49a919 [132.253.77.200]. [operationID:E7CC4B39-00000011][Caller: VirtualInfrastructure.Updates.PollerDispatcherImpl.CreateFilter]
[viclient:SrvMsg  :P:21] 2012-08-22 11:40:51.612  RMI Request Vmomi.Core.PropertyCollector.CreateFilter - 17
<spec type="Vmomi.Core.PropertyCollector+FilterSpec">
  <PropSet>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.ManagedEntity</Type>
      <PathSet>
        <item>Vmomi.ManagedEntity.name</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.ManagedEntity</Type>
      <PathSet>
        <item>Vmomi.ManagedEntity.parent</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.VirtualMachine</Type>
      <PathSet>
        <item>Vmomi.VirtualMachine.resourcePool</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.Folder</Type>
      <PathSet>
        <item>Vmomi.Folder.childType</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.Dvs.DistributedVirtualPortgroup</Type>
      <PathSet>
        <item>Vmomi.Dvs.DistributedVirtualPortgroup.config.distributedVirtualSwitch</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.DistributedVirtualSwitch</Type>
      <PathSet>
        <item>Vmomi.DistributedVirtualSwitch.config.uplinkPortgroup</item>
      </PathSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+PropertySpec">
      <Type>Vmomi.VirtualApp</Type>
      <PathSet>
        <item>Vmomi.VirtualApp.parentFolder</item>
      </PathSet>
    </item>
  </PropSet>
  <ObjectSet>
    <item type="Vmomi.Core.PropertyCollector+ObjectSpec">
      <Obj type="ManagedObject">ContainerView:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52715b94-5967-cc7c-280b-3950bde37034 [132.253.77.200]</Obj>
      <SelectSet>
        <item type="Vmomi.Core.PropertyCollector+TraversalSpec">
          <Type>Vmomi.View.ContainerView</Type>
          <Path>Vmomi.View.ContainerView.view</Path>
        </item>
      </SelectSet>
    </item>
    <item type="Vmomi.Core.PropertyCollector+ObjectSpec">
      <Obj type="ManagedObject">Folder:ha-folder-root [132.253.77.200]</Obj>
    </item>
  </ObjectSet>
</spec>
<partialUpdates>True</partialUpdates>
[viclient:QuickInf:W:25] 2012-08-22 11:40:51.634  WaitForUpdates Version = 1
[viclient:SoapTran:W:25] 2012-08-22 11:40:51.634  Invoke 18 Start WaitForUpdates on PropertyCollector:ha-property-collector [132.253.77.200]. [operationID:E7CC4B39-00000012]
[viclient:SrvMsg  :W:25] 2012-08-22 11:40:51.634  RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 18
<version>1</version>
[viclient:SoapTran:P:28] 2012-08-22 11:40:51.642  Invoke 17 Finish CreateFilter on PropertyCollector:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52b9ce1b-590a-6026-14a4-990f1f49a919 [132.253.77.200] - Serial:0.003, Server:000.029 [session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]523b93c0-e731-88fe-b486-46b3cbaae878]
[viclient:SoapTran:W:27] 2012-08-22 11:40:51.659  Invoke 16 Finish WaitForUpdates on PropertyCollector:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52b9ce1b-590a-6026-14a4-990f1f49a919 [132.253.77.200] - Serial:0.011, Server:000.152
[viclient:QuickInf:W:27] 2012-08-22 11:40:51.659  WaitForUpdates Version = 1
[viclient:SoapTran:W:27] 2012-08-22 11:40:51.659  Invoke 19 Start WaitForUpdates on PropertyCollector:session[52c0b12b-e840-dfc1-d975-3c79e912bfb6]52b9ce1b-590a-6026-14a4-990f1f49a919 [132.253.77.200]. [operationID:E7CC4B39-00000013]
[viclient:SrvMsg  :W:27] 2012-08-22 11:40:51.659  RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 19
<version>1</version>
[VICnMngt:Critical:M:30] 2012-08-22 11:40:52.039  OnServiceEvent SessionChanged for https://132.253.77.200/sdk : No detail
[VICnMngt:Critical:M:30] 2012-08-22 11:40:52.044  ClearNotConnectedWarning"

Thanks

Hello All,

After I reset ESXi pw and it reset the server IP to 0.0.0.0 and when I login the Hypervisor or GUI, I noticed that the following item greyed out:

Configure Management Network

Restart Management Network

Test Management Network

Restart Standard Switch

And when I try to enable Management Network. I get this message "Enable Management Network error Management Network Interface cannot be found"

I checked the NIC on server has link/activity lights. And the logs show that NIC is up 1000Mbps. I looked in the BIOS and it show detect NIC card as well.

I search online and can't anything that can help me fix this.

Any helps would be appreciate!

Thanks,

Dear users,

I have a problem that I can't access our ESXi host by ILO.
There is no clue for me that I can say how this happend since it has worked but since a month or 2 we are not able to login.
Well to mention login, I can't even connect to the webpage from the ESXi host.
I have tried to find a solution on the internet, but there was not that could explain me how this could happen or how to solve this problem we are facing currently.

ESXi Model: ProLiant DL380 G7
Lockdown Mode: Disabled
Version: 4.1.0, 800380

Services Properties

I/O Redirector (Active Directory Server): Stopped
Network Login Server (Active Directory Service): Stopped
lbtd: Running
Local Tech Support: Stopped

Local Security Authentication Server (Active Directory Service): Stopped
NTP Deamon: Running
VMware vCenter Agent: Running
Remote Tech Support (SSH): Running
Direct Console UI: Running

- I can ping the ESXi host

- I can use putty to login succesfully on the host

- I have restarted the following services:
VMware vCenter Agent, Remote Tech Support (SSH) and Direct Console UI.

-I have updated the ESX host to the latest files

This didn't helped

- I have restarted the ESX host
This didn't helped

- I have checked the configuration on the machine it self, but there was no option that could give me a clue that there was something wrong.

My knowledge of VMware is not that big, so I was doubting to contact VMware or try a discussion on the forum.
So If I don't understand you correctly, my bad for that.

Kind regards,
Martijn

I have another thread running with Andre related to problems consolidating snapshots.  During the implementation of his recommendation to clone I received the error: Failed to clone disk : Input/output error (327689).  Any help would be appreciated.

Running: ESXi 4.0 Build 171294

I have over 600 gigs of free space in the datastore.

I have an old system running THEOS Corona version 5 patch level 208.  I need to keep the data available but woudl really like to get off the old hardware.  I created a VM on my ESXi 4 host.  It works, for about 30 seconds and then the network dies.  I'm using the E1000 nic.  All others do not work at all.

Has anyone seen THEOS Corona before?  Any success getting it to work in vSphere?

I'm testing vRanger and Veeam as an option to backup our VMs. I've done a backup and restore using vRanger and now I'm attempting it with Veeam. I've done the backup of my test machine and I was going in to delete the VM so I could test the restore. However, When I right-click on the VM, Delete from Disk and Remove from Inventory are greyed out. I've tried it in vSphere remotely and locally on the vSphere server. Is there something I can look for that's causing this?

One thing that's changed recently. I was testing the HA of our cluster over the weekend and when I powered one of our hosts back on and tried to power up some of the VMs, I was getting the error that's attached. I made some changes to the HA settings after searching around for a while and was then able to power on the machines. I am still getting an error in vSphere that says "Configuration Issues: HA agent on <host> in cluster <org> HA Cluster in <org> Datacenter has an error: Cannot complete the HA configuration." I have no idea if this has anything to do with not being able to delete a VM but thought I'd include it.

Thanks.

Looking to enable EVC without haaving to shut down all hosts or vm's.

I have an existing cluster with some older hosts.  I added a new host to the cluster, and tried to vMotion a vm - fails with the EVC error (CPUID or some such, the error itself is not the issue).

I've read posts about enabling EVC, but they all require no running VM's to modify EVC.

I tried to create a new cluster and disconnect/remove one host from the old and connect it to the new cluster.  If there are any running vm's when I disconnect/reconnect, it gives an EVC error and does not add the host to the new cluster.

Alternatively, can I vmotion on an HA cluster between different host types (I thought that was the whole point of HA/vMotion...the VM's are abstracted from the underlying physical hardware)...

Thanks!

Hi there.

We have used this:

http://communities.vmware.com/thread/394669?start=0&tstart=0

http://en.blog.skydriver.org/tag/bios-440-rom/

as a source.

But still after applying bios 440 rom file to VM, the VM just want start up. It throws an error: 0x0000005D.

We have copied bios into folder where VM is located.

We had add this parameters:

bios440.filename = ./bios.440.rom

mce.enable = TRUE

cpuid.hypervisor.v0 = FALSE

vmGenCounter.enable = FALSE

But an error message still appears and we are unable to boot 2012 server.

Any other hints please?

With best regards,

Is it possible to set up a remote restart of a Virtual Machine via a web? Recently I was asked to help with IT support for a business that uses ESXi v4.1 to run two windows 2008 OSs. I discovered that employees tend to hard restart the ESXi server each time something goes wrong. One of their virtual machines running Windows Server 2008 does crash time to time and requires a reboot. I'd like to set up a mechanism that will allows employes to restart the guest virtual machine without restarting ESXi server. Is it possible?

I have taken over an account running vmware esix 4.0 free version.  They are running version 4.0 no updates.  When I came in this morning, I couldn't connect the v sphere client to the server due to a .NET update.  So, I downloaded the vsphere client 4.0 update 1 and update 2.  I get passed the error now but it's telling me a bad username and password.  I have tried vsphere update 1 and update 2.  So, my questions are:

1. I know esxi has not password recovery except reinstall.  If I reinstall, will I loose my data?

2. My customer seems pretty sure of the password.  Could it be a compatibility issue not accepting my password? ie The server is running no updates, but vsphere is update 1.

3.  Can I upgrade the server to a new version without the password? (I haven't upgraded a vmware server in over 3 years).  During the upgrade, can I or reset the password?

4.  Can I upgrade to a paid version and be able to set a new password?

The issue is that there are virutal servers down and I can't see why they are down because I can't connect with vshpere. Please assist.

Where can the hpacucli utilties for an ESXi 4.1 machine be downloaded from?  Then, what is the procedure to install?  Will be running the install from the ESXi command line over an SSH terminal if that makes any difference.

Keith

I need to move some esxi hosts off a vDS to a standard vSwitch in preparation for moving the ESXi hosts to a new vCenter

I have two 10 GB NICs that handle VM ports, NAS storage, and vmotion.

Is there a documented procedure for moving from a vDS to a vSwitch, particularly for migrating the NAS storage to a vSwitch?

Thanks

Tom

Hello.

I need to change one ip address of my server. The VLAN contains all virtual machines and VM-kernel. Because of configuration error in my Network I need a new ip address here.

The management network is on another VLAN. The third network connects to an storage system, with a NFS-Share.

Can I change the ipaddress using the vsphere Client without rebooting the esxi machine or the guests?

Thanks in advance for your answers.

Best regards

Dirk Emmermacher

I just recently tried to delete a snapshot of a VM via the VM snapshot manager.  The VM was 80GB in size with a snapshot of 50GB existing, I gracefully shutdown the OS/VM prior to removing the snapshot.  Once I started the removal, all was well until we got to 95% (the 95/99% issue we all know).  After doing some research, I finally decided to cancel the process and restart the management services via the host.  This resolved the issue and the snapshot appeared to be removed.

A couple days later I was working on another task and ended up experiencing the "An internal error occurred...Details:  Object reference not set..." error, this took quite some time to fix but eventually was resolved.  This showed me that the snapshot I thought removed previously, did not actually get removed;  i have now lost trust in the VMware snapshot manager!

As I am going to have to go through the process of removing snapshots from numerous VM's, over the next couple of weeks.

I want to avoid having to experience this type of related issue again, I want to ensure that the VM snapshot is completed removed and as quick as possible.

Is there any preferred way of going through the snapshot removal process?  Maybe via the CLI or a VMware or Third-Party utility/tool?

Is there a "verification" process that can be taken to ensure that the snapshot was actually removed?  It appears that I cannot trust the GUI/vSphere Client when it comes to verifying the snapshot removal. 

A large IO from a Guest VM running Microsoft Windows Server 2008 R2 using pvscsi driver to an RDM disk, is split into 64kb IO sizes when sent to storage array.  ESXi host profile has Disk.DiskMaxIOSize set to the default (32 MB).

Using Windows perfmon, can monitor IO at the Windows "physical disk" layer, and it shows large IO being properly performed.  The pvscsi driver, along with the Disk.DiskMaxIOSize value of 32MB should allow the large IO through the IO stack.  Performance is very good, but we want to further improve the efficiency of the large IOs.  There is a non-trivial loss of efficiency and distortion of IO statistics when the large IOs are unnecessarily split.  It also stresses the lun-queue-depth –centric capabilities, and will hit queue-depth ceilings sooner. 

Storage array performance statistics show maximum IO size ever received on the front end SAN ports being 64kb.

EMC PowerPath/VE for ESXi is used for multipath management.

An HP/Emulex SAN controller is being used.  The Emulex driver module scatter/gather segment count parameter "lpfc_sg_seg_cnt" is at the default value of 64, which typically enables 512kb IO sizes.

Why is the large IO being decomposed into multiple 64kb IOs, and where would this process be documented?

What are the configuration parameters that can be changed to increase the disk IO size being sent to the storage array?

Using a Linux analogy, the ESXi system is behaving as if the "/sys/block/sd*/queue/max_sectors_kb" under Linux were set to 64.

Thanks for the help.

Dave B

Hi All,

I have a ESXi host running on 4.1 U1. It has close to 14 vms running on it. Client has complained of the application opening slowly during peak morning hours (on one of the VMs on the host) when maximum users are logged in.

Here is what it looks like

This is a Windows 2003 VM. It has 20GB of RAM and 4vcpus. Name of the VM is ABC. Couple of points I am unable to understand

When I open esxtop Window >> hit c (for cpu) >>> hit V (to view only VMs). I see the gid for the VM ABC it is 17920187. I am unable to expand it. As after hitting e (to expand it) it will accept value till 1792018 and not the last number 7. Why is this happening.

The average CPU load on the ESXi does not exceed .50; However the %lat_c counter goes till 80. Once it went to 126. I read in one of the articles that Power state of the CPU needs to be checked. As per article http://www.virtual-hike.com/high-lat_c-values-in-esxtop/ ......... Power state needs to be checked however in my case it is 0 -- which I guess means it is disabled.

Any suggestions on how do I go about it.

Thanks in advance

We are currently not using resource pools within our environment. What we are looking to do is implement resource pools with memory reservations based upon our VM sizes. For example, we'll create a 4GB resource pool for VMs with 4GB of memory, an 8GB resource pool for VMs with 8GB of memory, etc. We would then set the memory reservation to half (of the VM) for each pool. So the 4GB VM will have a 2GB reservation. Our aim in doing this is reduce the size of our swap files. We have a few VMs spread out in our environment that are independently configured. For example, a 12GB VM with a 6GB reservation has a 6GB swap file. On a global level, this could save us a lot of datastore space.

A few questions in doing this though. What will happen for VMs that already have reservations enabled? Does the resource pool override individual VM settings?

And does anyone see this as having any adverse effects for an HA event? We have had issues in the past in a different environment with reservations (large 38GB+ reservations), and when we lost a host VMs were unable to power on due to there being no more resources available.

Hi all,

We are running Lab Manager 4, so we still have ESXi 4.1 hosts in our infrastructure that we cannot upgrade to ESXi 5.x.

At one of our sites, we regularly see VMFS corruption, where some VM folders cannot be read/deleted/listed.  We are in the process of adding new storage and migrating our current VMs out of the corrupted data stores, but I'd like to find out what is causing this corruption, and how can I prevent it from happening in the future?

Hosts: HP DL360p G7

Storage: HP P2000 G3

ESXi: 4.1.0 build-260247

If we see many such errors, once we reboot all the hosts, the number goes down considerably (e.g. from 20 errors, we are left with just 3).

Have you seen such an issue at your site?

Thanks,

Khare

Examples:

/vmfs/volumes/4fc87616-2a581cdc-6b13-3cd92bee82a4/dirname # ls -l * >/dev/null

ls: 10589/timA: Invalid argument

ls: 10589/: Invalid argument

ls: 10589/

: Invalid argument

ls: 10589/: Invalid argument

ls: 10589/: Invalid argument

ls: 10589/

nvalid argument

ls: 11843/IHDR: Invalid argument

ls: 11843/e: Invalid argument

ls: 11941/n="1.0"?>

<Foundry>

<VM>

<VMId type="string">52 32 c9 78 f5 47 c6 6c-03 d9 ba 14 18 2d 42 e4</VMId>

<ClientMetaData>

<clientMeta: No such file or directory

ls: 11941/es/>

<HistoryEventList/></ClientMetaData>

<vmxPathName type="string">017695-Central1.vmx</vmxPathName></VM></Foundry>

: No such file or directory

ls: 12351/IHDR: Invalid argument

ls: 12351/e: Invalid argument

ls: 12478/012478-12478-2k8-Central.vmx.LMBackup: No such file or directory

ls: 12478/012478-12478-2k8-Central.vmx.LMBackup: No such file or directory

ls: 7600/IHDR: Invalid argument

ls: 7600/YJ)Ù|Ñ6"¢ªyc,zö!ïýS: Invalid argument

ls: 9251/009251-VirtualRouter_C2796F3338_DoNotModify.vmxf: No such file or directory

ls: 9251/009251-VirtualRouter_C2796F3338_DoNotModify.vmxf: No such file or directory

ls: 9251/009251-VirtualRouter_C2796F3338_DoNotModify.vmsd: No such file or directory

ls: 9618/IHDR: Invalid argument

Good morning, all!

I was trolling through the vCenter system logs this morning and noticed that many entries have a vm number.  The format is vm-5xx.

Does this number relate to a specific VM, and, if so, can I correlate that number with a friendly name?

Thanks!

Gregg