ESXi (6.5.0 Build 5310538) is installed on a 500GB HDD, and when I try to upgrade it o 6.7 the progress failed with some errors messages.

esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-8169922-standard

[InstallationError]

Failed updating the bootloader: Execution of command /usr/lib/vmware/bootloader-installer/install-bootloader failed: non-zero code returned

return code: 1

output: ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored.

Traceback (most recent call last):

   File "/usr/lib/vmware/bootloader-installer/install-bootloader", line 31, in <module>

     import vmkctl

MemoryError

       vibs = VMware_bootbank_esx-base_6.7.0-0.0.8169922

Receiving a 504 error when attempting to add vcenter. I receive the following message:

Http failure response for https://sr-skyline.primed.com/api/v1/manage/endpoint?auto=false: 504 Gateway Time-out

A few days ago, I bought Atom C3758 based Mother Board.

Unfortunately, ESXi 6.5/6.7 have no inbox driver for X553 GbE.

So I build x553 only driver from ixgbe-5.3.6 linux driver.

I'm using it with following parts.

Asrock Rack C3758D4I-4L

Kingston KVR24R17D4K4/128

Intel ET Dual Port Server Adapter

(initial connection by igb inbox driver)

Transcend JetFlash 720S

SilverStone SST-CS280 / SST-ST45SF

I have tested with IPv4, MTU9000, no VLAN only. (mainly iSCSI connections)

Other setting may cause problems.

However, if you are interested in the driver, try it.

To use this driver:

# esxcli software acceptance set --level=CommunitySupported

# esxcli software vib install -v /tmp/net65-x553-5.3.6.x86_64.vib

I'm installing a new Vcenter server and it needs to be version 5.5. Will a ver 6 license work for that?

Purpose of this post is simple and obvious...  bring back development to thick client.  THANKS!

Normally I installed the ESXI OS onto a small 15 gb Datastore (Flash Drive) then create a larger Raid 5 datastore with all the disks in the server to store my VM's Folders.


It was suggested to me that I should install the ESXI OS on the Raid 5 datastore drive and not create a separate ESXi OS datastore. So both the OS and the Datastore would be on the same RAID 5 set of disks.


I looked for a best practice, and did not see one.


Have I been doing it wrong all these years?  What is the Best Practice

My esxi host is crashing during a file transfer over the network to an openmediavault share. I am on ESXI 6.7 and running the latest version of openmediavault as a nas/share drive. Has anyone experienced this, not specifically with OMV but crashes during file transfers?

I am running esxi 6.5 with the latest patches and vmware tools 10.1.5

I am having very inconsistent performance issues with both of my hosts. Basically the windows 2016/windows 10 guests are sluggish at times. nothing will load and the os is basically unresponsive when interacting with the gui. The issue seems to be stemming from disk performance but I am not 100% certain that this is the cause, it may be a side affect.

What I have noticed is that some vms show a average response time for the disk of about 2000ms. Yet if i check the performance monitor at a host level the disk and datastores are all showing sub 1ms response time. I am not able to explain the inconsistencies there.

I have a local ssd datastore on each host as well as a rather fast nvme iscsi san that is connected via 100gb mellanox connectx4 cards. I see the issue with both hosts and both datastores. The issue seems to be worse now with the most recent patches and vmware tools drivers. I am using vmxnet3 network cards and paravirtual scsi controllers on all vms.

I have run disk benchmarks on the vms and the resutls vary. I have already seen it where i run a disk benchmark on a guest, get horrible results, vmotion it to the other host, and benchmarks to the san are fine, and then i vmotion the guest back to the original host and the results are fine the second time I run it.

here is an example of a bad test, the reads are terrible:

-----------------------------------------------------------------------

CrystalDiskMark 5.2.0 x64 (C) 2007-2016 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

-----------------------------------------------------------------------

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]

* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 2) :     0.655 MB/s

  Sequential Write (Q= 32,T= 2) :  5384.173 MB/s

  Random Read 4KiB (Q= 32,T= 2) :     0.026 MB/s [     6.3 IOPS]

Random Write 4KiB (Q= 32,T= 2) :   617.822 MB/s [150835.4 IOPS]

         Sequential Read (T= 1) :     2.306 MB/s

        Sequential Write (T= 1) :  1907.004 MB/s

   Random Read 4KiB (Q= 1,T= 1) :    53.942 MB/s [ 13169.4 IOPS]

  Random Write 4KiB (Q= 1,T= 1) :    52.104 MB/s [ 12720.7 IOPS]

  Test : 50 MiB [C: 5.2% (15.6/299.5 GiB)] (x1)  [Interval=5 sec]

  Date : 2017/03/25 20:29:18

    OS : Windows 10 Enterprise [10.0 Build 14393] (x64)

a few seconds later on the same setup i get perfectly fine results:

-----------------------------------------------------------------------

CrystalDiskMark 5.2.0 x64 (C) 2007-2016 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

-----------------------------------------------------------------------

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]

* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 2) :  6655.386 MB/s

  Sequential Write (Q= 32,T= 2) :  5654.851 MB/s

  Random Read 4KiB (Q= 32,T= 2) :   695.193 MB/s [169724.9 IOPS]

Random Write 4KiB (Q= 32,T= 2) :   609.216 MB/s [148734.4 IOPS]

         Sequential Read (T= 1) :  1810.393 MB/s

        Sequential Write (T= 1) :  1626.112 MB/s

   Random Read 4KiB (Q= 1,T= 1) :    53.266 MB/s [ 13004.4 IOPS]

  Random Write 4KiB (Q= 1,T= 1) :    54.289 MB/s [ 13254.2 IOPS]

  Test : 50 MiB [C: 5.2% (15.7/299.5 GiB)] (x1)  [Interval=5 sec]

  Date : 2017/03/25 20:32:21

    OS : Windows 10 Enterprise [10.0 Build 14393] (x64)

Aloha,

We are about to jump from 5.5 to 6.5.2. We have 3 sites on island that have very solid connections

to each other. Each site has it's own clusters and vcenters which makes management a pain.

As we see it we have two options to clean things up-

1. Put all the necessary pieces and parts on the same management network and have one vcenter.

2. Used Enhanced Linked Mode at each site.

Any advice is very much appreciated..

Bill

I would like to know what is the best practice and way on upgrading 2 sites with vCenter Servers linked mode.

Our concern is that there are some applications in the infra that is dependent on vCenter.

Setup is 2 vCenter Server with different PSC.

I use VMware Workstation Player 14.1.2 build-8497320 on Windows 10. The guest is a Fedora 28.

When I want to suspend the guest, it doesn't work.

I click "Suspend Guest" from the menu, confirm with "Yes" then the WMware window disappears for some time and pops up again. The VM is still running but Fedora lost its network connection.

Here is the part of vmware.log related to this attempted suspend:

2018-06-06T10:43:25.483+02:00| vmx| I125: VMXVmdbCbVmVmxExecState: Exec state change requested to state suspended without reset, soft, softOptionTimeout: 20000000.

2018-06-06T10:43:25.483+02:00| vmx| I125: Tools: sending 'OS_Suspend' (state = 5) state change request

2018-06-06T10:43:25.483+02:00| vmx| I125: Tools: Changing running status: 1 => 2.

2018-06-06T10:43:45.485+02:00| vmx| I125: Soft power operation timed out.

2018-06-06T10:43:55.490+02:00| vmx| I125: Tools: Timed out waiting for state change status.

2018-06-06T10:43:55.490+02:00| vmx| I125: Vix: [15312 mainDispatch.c:4151]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

2018-06-06T10:43:55.490+02:00| vmx| I125: Tools: Changing running status: 2 => 1.

Does anybody else experience this issue?

What can I do to make it work again?

I think (but I'm not sure) that this behavior started after upgrading to 14.1.2

I'm creating custom Windows 7 images and part of this involves me silently installing VMWare Tools using the following command: "%WINDIR%\Setup\Files\VMWareTools.exe" /s /v "/qn reboot=r"

I have also tried "%WINDIR%\Setup\Files\VMWareTools.exe" /s /v "/qn reboot=ReallySuppress"

Both commands work in terms of installing VMWare Tools silently; however, I am still receiving a prompt saying "You must restart your computer to apply these changes."

Is it possible to completely suppress this message? It's interfering with some other tasks I want to carry out with the custom image after install is completed. I understand that it will still be necessary to restart, but since I plan to automate that at the proper time, I do not want this message to appear.

So I'm basically writing a script that will import an OVF into vCenter.  The script has worked fine in the past, but I'm making some modifications to it so people who don't know the setup like I do, or those who use it elsewhere can get it to work for them.  Here's the first part of it:

$type = Read-Host "Enter Host or Cluster"

if ($type -eq "Cluster")

{

Get-Cluster | Select Name | sort Name | Format-List #Gets a list of clusters in the vCenter#

$Cluster = Read-Host "Enter Cluster Name"

$myCluster = Get-Cluster -Name "$Cluster"

Get-VMHost -Location "$myCluster" -state "Connected" | sort Name | Select Name,ConnectionState,PowerState | Format-Table #Lists the host from the cluster specified earlier#

}

else

{

Get-VMHost | where {$_.state -eq "Connected"} | sort Name | Select Name,ConnectionState,PowerState | Format-Table

}

$vmHost = Read-Host "Enter host name"

Get-Datastore -VMHost $vmHost | where {$_.type -eq "NFS"} | Select @{N="Cluster";E={$cluster.Name}},Name,CapacityGB,FreespaceGB,@{N='UsedSpace';E={$_.FreeSpaceGB/$_.CapacityGB*100}} #Lists datastores and capacity#

$datastore = Read-Host "Enter Datastore Name"

So basically after connecting to vCenter I'm asking the user to choose Cluster or Host, depending on what they deploy to.  It will then read out the hosts that are showing as connected.  After that I want the NFS datastores attached to the host to show up so the user can choose which one.  For whatever reason this worked when I chose Cluster but not Host at the beginning.  I've been playing with it since, but now it doesn't come up for either.  It's driving me nuts and I just want to get this fixed so I can finish up the script and utilize it.  Thoughts anybody?

So here's the setup:

I use vRA 7.3.1 to build a Windows 10 x64 VM that users can build thru a blueprint.  It had RS3 initially and VM Tools 10.2.  Users could build just fine.  I then upgraded to RS4 and it still builds fine.  However when I run the following script (generic info used below for user/pass/server):

Connect-VIServer servername -User username -Password password

$vm = Read-Host "Enter VM name"

$string = 'query user /server:$vm'

Invoke-VMScript -vm $vm -ScriptText $string -ScriptType Powershell -GuestUser 'administrator' -GuestPassword 'password'

And I enter the VM I get the query response I want

vCenterserver.lab        443   VSPHERE.LOCAL\Administrator
Enter VM name: myvm

VM           : myvm
ExitCode     : 0
ScriptOutput :  USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
                user              rdp-tcp#1           2  Active          .  6/4/2018 11:32 AM

The above is on a VM that's running Win 10 RS4 x64 with Tools 10.2.5 that was upgraded via a PowerCLI script.

And that just outputs to the window.  Unfortunately I have more than one machine, so I created a batch script below:

Connect-VIServer vCenterserver.lab -User username -Password password

$GetVM = Get-VM -location VRM | sort Name

$obj = foreach ($vm in $GetVM)

{

$string = 'query user /server:$vm'

Invoke-VMScript -vm $vm -ScriptText $string -ScriptType Powershell -GuestUser 'administrator' -GuestPassword 'password' | Out-File VRM.txt -append

}

So the above script I will get a list of machines that only appear to be running Tools 10.2 as the script will continually tell me that the version of tools is out of date on the machines.  I get the output in the text file, but what's odd is the machines that have the newer version of tools, there's a line, but it's blank as shown below:

ScriptOutput
-----------------------------------------------------------------------------------------------------------------------
|   USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
|   user1                                2  Disc     10+00:16  5/25/2018 8:43 AM
| 
-----------------------------------------------------------------------------------------------------------------------

ScriptOutput
-----------------------------------------------------------------------------------------------------------------------
| 
-----------------------------------------------------------------------------------------------------------------------

ScriptOutput
-----------------------------------------------------------------------------------------------------------------------
| 
-----------------------------------------------------------------------------------------------------------------------

ScriptOutput
-----------------------------------------------------------------------------------------------------------------------
| 
-----------------------------------------------------------------------------------------------------------------------

ScriptOutput
-----------------------------------------------------------------------------------------------------------------------
|   USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
|   user2               rdp-tcp#13          2  Active         48  5/29/2018 9:08 PM
| 
-----------------------------------------------------------------------------------------------------------------------

I know those machines that are missing, if I query them I'll get a response with the first script mentioned here.  Why would an upgraded version of tools appear to break this?  Am I missing something?  Those machines that are missing did show up before the tools upgrade.  I ran a script to update the tools on the machines remotely and it didn't work for all machines, as it appears that I need to have some sort of custom attribute: https://blog.vmpros.nl/2015/05/15/vmware-vix-error-code-21009-during/ .

I have tried uninstalling VM Tools from the machine and reinstalling it, but that made no difference, even when running the script from one of the machines that's affected.  Yes I am running Anti-Virus stuff, however on the machines that are working it's running there as well, and all machines should have the same version of the software, so I don't think that's an issue.  I have now just taken my test machine and downgraded Tools to 10.2.0, re-ran the batch-script and it detected my machine.

I have also upgraded VM Tools on the template to 10.2.5 and am re-running the blueprint thru vRA to see what happens.  It fails to recognize the machine in the batch script.  So do I have a problem here with tools 10.2.5?  Something else?  Please advise.  Thanks.

Edit: I should also mention I was originally using PowerCLI 6.5.0 build 4624819.  I upgraded to 10.1.0 but I still get the same issue.

Edit 2: I took one of the machines and put VMware Tools 10.2.1 on it and re-ran the batch script.  This time it detected the VM in the script.

I have setup VPN tunnel on the Lenovo laptop and it works for selected applications.

But when the user puts the computer to sleep and then wake up tunnel goes in to state connecting and never connects.

I am attempting to configure Skyline. I am in the vCenter configuration section. I have put in the vCenter address and filled out the RO user credentials. When I click Continue I see: The certificate provided by your vCenter is not valid (Certificate Thumbprint [1c1e2085ca8fa309e5dcad61b145ec89964e3a99]).

Press "CONTINUE" if you would like to continue using an invalid certificate

I press Continue and I get: Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client. -> Couldn't login the client. -> General failure. -> org.apache.http.conn.HttpHostConnectException: Connect to 10.1.252.24:7444 [/10.1.252.24] failed: Connection refused (Connection refused) -> Connect to 10.1.252.24:7444 [/10.1.252.24] failed: Connection refused (Connection refused) -> Connection refused (Connection refused)

I have an separate VM with the  PSC/SSO. I have tried using the Custom SSO configuration both on and off with the same results.

Error received when FQDN of VC and PSC was used.

Endpoint test failed. Error message: Couldn't create PropertyCollector facade for getting the VC UUID -> java.lang.RuntimeException: Couldn't login the client.

-> Couldn't login the client. -> Error communicating to the remote server https://10.1.252.205:7444/sts/stsservice/vsphere.local ->

Error communicating to the remote server https://10.1.252.205:7444/sts/stsservice/vsphere.local -> HTTP transport

error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address 10.1.252.205 found -> java.security.cert.CertificateException:

No subject alternative names matching IP address 10.1.252.205 found -> No subject alternative names matching IP address 10.1.252.205 found.

Any assistance is greatly appreciated.

Regards,

Jim

- Recently upgraded hosts to 6.7 and vCenter to 6.7a

- Hosts are 'not responding' in vCenter Server

- Can ping

- Cannot acess web interface or login via SSH

- Can access it via console, but after you enter login information and press enter it freezes (cursor is still blinking)

- If you remove the host from the inventory and shut down a virtual machine on the host it brings everything back online and the host can be re-added to vCenter

- Four identical hosts, has happened on three of the four (twice on one)

- The host that had this issue twice now will not come back after trying the above method and is completely unresponsive at the console

I am looking into what is possible to do using the kickstart preinstall section with busybox as the shell.  I have some questions that I have not been able to find the answers to.

1) Can you access a console during the install by entering a command key combination? (you can do this with anaconda)

2) What commands are available to the busybox shell for during the preinstall.

3) What is the best way to log?

4) Can messages be sent to the console at least for debugging?

Same questions for the post install section.

The firstboot section I have no problems.

Library of virtual machines is blank despite creating a virtual machine. Happens with every OS I've tried.Any ideas?

Hi There,

Recently, a native Mac client is released, it can manage vCenter/Esx from Mac OS, download link is http://www.vclient.top