I have ESXi Embedded web client.

Client version:

1.33.1

Client build number:

12086396

ESXi version:

6.5.0

ESXi build number:

7388607

I tried to import a OVF and VMDK file and got the following error: "Line 25: Unsupported hardware family 'vmx-16'."

The vm i'm trying to import is from a vm created earlier this year in VMware Workstation Pro 15. Is there a resolution for this more specific than the options in the following older thread?

Import OVF Template - Unsupported hardware family 'vmx-10'

Why are VM's created in Workstation Pro 15, not compatible with ESXi 6.5?

I am running a 2018 Mac mini (i7, 16gb ram, 512gb SSD) with the latest version of MacOS and I am virtualizing Windows 10 which is on 1903 with the latest version of VMWare Fusion 11.

To start, there are no performance issues, my issue is strictly a graphical issue and it is exclusive to the Unity Mode, in Single or Full Screen Mode everything is just peachy.

In Unity Mode I am seeing some graphics issues whenever I drag a window across the screen. For example, lets say I have the calculator app open in Windows 10 using Unity Mode and I drag the window from the left side of my screen to the right side of my screen, the movement of the dragging is anything but smooth. It looks like animations and frames are dropping and moving the window looks jaggy and jerky but nothing is hanging and as soon as I stop dragging the window everything is fine. It’s strictly a graphical issue with Windows 10. I also see it in the animations when I minimize an Windows 10 program, except here I only sometimes see it. It appears to be random to me. And this only occurs with Windows 10 programs, with MacOS programs everything is smooth as one would expect.

I’ve tried reinstalling VMWare tools, changing cores to 1, 2, and 3, increasing VRAM from 1gb to 2gb, turning off 3D acceleration, and I see no changes.

Is this expected behavior? Or what would be the fix?

Hi!

I have updated Windows 10.1903 with fixed Sandbox.

Installed have VMware Workstation 15.

Hyper-V incl. hypervisor and all components are removed/disabled.

I tried to run Sandbox, but it outputs only error message "No hypervisor found".

I want to ask if it means Hyper-V hypervisor and if can VMware work together - without enabling/disabling between.

Is it possible?

Thank you for replies.

Miro

Hello guys,

I have 2-node cluster with direct connect. I was recently testing the different failure scenarios and the cluster behaves as desired, but in one specific case...

I disconnected both physical up-links from the ESXi (VM networks, management, VMotion and witness) and kept the direct connect between the host connected. The host became disconnected from the vCenter perspective....but the VM keeps running on that host? I would say if the host disconnected from the network, I would like have the VM restarted on the other host with full network connectivity.

I was a little confused why the VM was not restarted on the another host due to lack of connectivity...am I missing something? Both hosts are running 6.7u2 and all HA setting are set as recommended fin the official guide.

Thanks

Mario

Hello VM Community,

I am planning to write VCP-DCV exam, but it require training course. Couple of years ago it did training from New Horizons.

Below is the course overview and link for reference.

My question is: Does this training fulfill the VCP-DCV training requirement either for 6.5 or 6.7? If it does, what kind of document do I need to provide?

Thank you.

VMware® vSphere - Install, Configure, Manage v6.5

Course Overview

This five-day course features intensive hands-on training that focuses on installing, configuring, and managing VMware vSphere® 6.5, which includes VMware ESXi™ 6.5 and VMware vCenter Server® 6.5.

Who Should Attend

System Administrators and System Engineers

Course Objectives

By the end of the course, you should be able to meet the following objectives: Describe the software-defined data center Explain the vSphere components and their function in the infrastructure Deploy an ESXi host Deploy VMware vCenter® Server Appliance™ Use a local content library as an ISO store and deploy a virtual machine Describe vCenter Server architecture Use vCenter Server to manage an ESXi host Configure and manage vSphere infrastructure with VMware vSphere® Client™ and VMware vSphere® Web Client Describe virtual networks with vSphere standard switches Configure standard switch policies Use vCenter Server to manage various types of host storage: VMware vSphere® VMFS, NFS, virtual SAN, Fibre Channel, and VMware Virtual SAN™ Manage virtual machines, templates, clones, and snapshots Create, clone, and export a vApp Describe and use the content library Migrate virtual machines with VMware vSphere® vMotion® Use VMware vSphere® Storage vMotion® to migrate virtual machine storage Monitor resource usage and manage resource pools Use esxtop to identify and solve performance issues Discuss the VMware vSphere® High Availability cluster architecture Configure vSphere HA Manage vSphere HA and VMware vSphere® Fault Tolerance Use VMware vSphere® Replication™ and VMware vSphere® Data Protection™ to replicate virtual machines and perform data recovery Use VMware vSphere® Distributed Resource Scheduler™ clusters to improve host scalability Use VMware vSphere® Update Manager™ to apply patches and perform basic troubleshooting of ESXi hosts, virtual machines, and vCenter Server operations

Course Outline

1 - COURSE INTRODUCTION

Introductions and course logistics

Course objectives

Describe the content of this course

Gain a complete picture of the VMware certification system

Familiarize yourself with the benefits of the VMware Education Learning Zone

Identify additional resources

2 - INTRODUCTION TO VSPHERE & THE SOFTWARE-DEFINED DATA CENTER

Describe the topology of a physical data center

Explain the vSphere virtual infrastructure

Define the files and components of virtual machines

Describe the benefits of using virtual machines

Explain the similarities and differences between physical architectures and virtual architectures

Define the purpose of ESXi

Define the purpose of vCenter Server

Explain the software-defined data center

Describe private, public, and hybrid clouds

3 - CREATING VIRTUAL MACHINES

Introduce virtual machines, virtual machine hardware, and virtual machine files

Identify the files that make up a virtual machine

Discuss the latest virtual machine hardware and its features

Describe virtual machine CPU, memory, disk, and network resource usage

Explain the importance of VMware Tools™

Discuss PCI pass-through, Direct I/O, remote direct memory access, and NVMe

Deploy and configure virtual machines and templates

Identify the virtual machine disk format

4 - VCENTER SERVER

Introduce the vCenter Server architecture

Deploy and configure vCenter Server Appliance

Use vSphere Web Client

Backup and restore vCenter Server

Examine vCenter Server permissions and roles

Explain the vSphere HA architectures and features

Examine the new vSphere authentication proxy

Manage vCenter Server inventory objects and licenses

Access and navigate the new vSphere clients

5 - CONFIGURING & MANAGING VIRTUAL NETWORKS

Describe, create, and manage standard switches

Configure virtual switch security and loadbalancing policies

Contrast and compare vSphere distributed switches and standard switches

Describe the virtual switch connection types

Describe the new TCP/IP stack architecture

Use VLANs with standard switches

6 - CONFIGURING & MANAGING VIRTUAL STORAGE

Introduce storage protocols and storage device types

Discuss ESXi hosts using iSCSI, NFS, and Fibre Channel storage

Create and manage VMFS and NFS datastores

Describe the new features of VMFS 6.5

Introduce Virtual SAN

Describe guest file encryption

7 - VIRTUAL MACHINE MANAGEMENT

Use templates and cloning to deploy new virtual machines

Modify and manage virtual machines

Clone a virtual machine

Upgrade virtual machine hardware to version 12

Remove virtual machines from the vCenter Server inventory and datastore

Customize a new virtual machine using customization specification files

Perform vSphere vMotion and vSphere Storage vMotion migrations

Create and manage virtual machine snapshots

Create, clone, and export vApps

Introduce the types of content libraries and how to deploy and use them

8 - RESOURCE MANAGEMENT & MONITORING

Introduce virtual CPU and memory concepts

Explain virtual memory reclamation techniques

Describe virtual machine overcommitment and resource competition

Configure and manage resource pools

Describe methods for optimizing CPU and memory usage

Use various tools to monitor resource usage

Create and use alarms to report certain conditions or events

Describe and deploy resource pools

Set reservations, limits, and shares

Describe expandable reservations

Schedule changes to resource settings

Create, clone, and export vApps

Use vCenter Server performance charts and esxtop to analyze vSphere performance

9 - VSPHERE HA & VSPHERE FAULT TOLERANCE

Explain the vSphere HA architecture

Configure and manage a vSphere HA cluster

Use vSphere HA advanced parameters

Define clusterwide restart ordering capabilities

Enforce infrastructural or intra-app dependencies during failover

Describe vSphere HA heartbeat networks and datastore heartbeats

Introduce vSphere Fault Tolerance

Enable vSphere Fault Tolerance on virtual machines

Support vSphere Fault Tolerance interoperability with Virtual SAN

Examine enhanced consolidation of vSphere Fault Tolerance virtual machines

Introduce vSphere Replication

Use vSphere Data Protection to back up and restore data

10 - HOST SCALABILITY

Describe the functions and benefits of a vSphere DRS cluster

Configure and manage a vSphere DRS cluster

Work with affinity and anti-affinity rules

Describe the new capabilities for what-if analysis and proactive vSphere DRS

Highlight the evolution of vSphere DRS using predictive data from VMware vRealize® Operations Manager™

Perform preemptive actions to prepare for CPU or memory changes

Describe the vCenter Server embedded vSphere Update Manager, VMware vSphere® ESXi™ Image Builder CLI, and VMware vSphere® Auto Deploy capabilities

Use vSphere HA and vSphere DRS together for business continuity

11 - VSPHERE UPDATE MANAGER & HOST MAINTAINANCE

Describe the new vSphere Update Manager architecture, components, and capabilities

Use vSphere Update Manager to manage ESXi, virtual machine and vApp patching

Install vSphere Update Manager and the vSphere Update Manager plug-in

Create patch baselines

Use host profiles to manage host configuration compliance

Scan and remediate hosts

VMware® vSphere - Install, Configure, Manage v6.5 | New Horizons

Setup:

vsan Stretched cluster running esxi 6.7U1, all flash.

"Issue":

When I try to create a VM storage policy with object space reservation set to 25, 50 or 75% the vsan datastore doesn't appear as a compatible one but it does if I choose fully thin or thick. I have plenty of space available.

It doesnt matter what setting I try, (RAID1,5,6, Local, Stretched) it is always the same.

I haven't been able to find any special requirements for being able to create this type of policy.

What am I missing?

After I upgraded my 2 MBP to 10.14.6, all of the Windows VMs became extremely slow and stuck at the login screen...

The VMs are set to use TPM, I don't know if it's relevant.

Anyone came across the same situation?

Now I cannot continue my work...really frustrating...

—————20190727————-

I’m updating this for convenient reference.

Status: This issue has not been solved yet.

Many users encountered this issue which leads to completely unusable of VMs.

And we got some replies from Fusion developers, you could help developers identify issues by replying your hardware models/is disk encrypted or have the VM encrypted etc.

We have some reports that some users found out that if set the memory of VM to 2G could help.

Re: VM became extremely slow after upgraded to macOS 10.14.6

If you don’t need to use much memory and can work with it, you might try set the memory to 2G, or maybe less than 4G is also okay?

Still we are waiting for an official solution.

------------20190809--------------------------

Thanks to ksc

Re: VM became extremely slow after upgraded to macOS 10.14.6

I updated to Fusion 11.1.1, confirmed that I can login to the system, and desktop shows normally.

As ksc says, it is a workaround which I'm not quite sure if I can trust it to do my work in it....

At least, I'm able to get my works out and change to other options now.

I'll mark this issue as resolved for now, but keep the [Workaround Released] tag in the subject.

Looks like it would take quite some time for a real fix, I'll keep an eye on this.

消息编辑者为：Liam

Hi,

The current standalone VIX version 1.17 that you can download from Download VMware Workspace ONE doesn't work for VMware Workstation Player 15 vmrun.exe fails with ""Unable to connect to host" Error: the specified version was not found", vmrun.exe is version 1.17.0 build-6661328. This version of VIX does not contain a directory named "Workstation-15.0.0" and the correct entries in vixwrapper-config.txt

However VIX 1.17 taken from a Workstation Pro 15 installation works, vmrun.exe is version 1.17.0 build-10134415

Is there any downloadable VIX version that supports Player 15?

Please see the following post for details of how we found out about this problem: https://gns3.com/community/discussion/gns3-doesn-t-work-on-vmware-play

Thanks!

I'm new to VCF and am working on a deployment for a client, so I'm hoping the folks here can answer some questions. Thanks in advance for responses and I'll be sure to mark as correct for anyone that assists.

1. I've noticed in the VMware HOL that VCF management WLD deploys NSX and the first edge, but it seems I can't configure load-balancing on this edge, even though it shows load-balancing is enabled. The typical tab doesn't seem to be available. Does VCF not allow this? I've even tried deploying a second edge and the configuration option isn't there.

2. It seems that all the management workloads in the management WLD are deployed to a VLAN backed port-group, so now logical switches are used and no management workload traffic goes through edges? If this is the case, what does this first edge do then?

3. I've tried deploying a NSX-V WLD in the HOL and can't get it to work properly, it fails at configuring NSX manager backups. My question is, per the VVD two Uplink port-groups are created. I'm assuming this is to peer ESGs with upstream routers. My client wants to use NSX-V and not use dynamic routing, their use case calls for every workload to be NAT.

     a. Is there any reason or restrictions I should be aware of using NSX-V with VCF? I'm assuming when I deploy a NSX-V WLD it deploys the NSX configuration greenfield? Meaning, no logical switches, no DLRs, no ESGs? And then I can build out those constructs to my client's needs?

     b. Even if I can configure NSX-V however I like, will I still be required to have two uplink port-groups and VLANs to deploy the WLD?

4. It appears that NSX Manager backups up to the SDDC Manager? So if this is the case, does the SDDC manager host SFTP server or will I still need to provision this service somewhere else?

Cheers.

Could you  please provide me instructions on how to add more data store space to my exisitng 1 TB HDD, since I have place 2 more ,1 TB HDD in the server slots.

What would I have to do next. any documentation is good .

Thanks

Rin

I am looking to suppress few alerts for few objects/operations

currently when I am trying to disable alert it is disabling globally

Thank you,
Volga.

Hello

Is it possible with Powersehell Vmware.VimAutomation.Cloud where i can connect to a VDC and then list all the Networks (VLAN's).

Then list all each VLAN with the VM within it ?

$vcd01="https://vcd01.abc.com"

$orgPol="s01_I_a02"

$orgvdcPolSQL="s01_I_a02_SQL"

# I connect to the CIServer

Connect-CIServer -Server $vcd01 -org $orgPol -User $script:CloudUser -Password $script:password

#Gets all visible networks within an organization.

$myOrg = Get-Org -Name $orgPol

Get-OrgNetwork -Org $myOrg | FT -AutoSize

The output is

Name                             Gateway         Org       ExternalNetwork                                    NetworkType

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

External_abc-ProdIntrnlApp-2614 10.255.193.1    s01_I_a02 External_a02_abc-ProdInternalApp-10.255.193.0/24  Direct 

External_abc-ProdApp-2613       10.255.192.1    s01_I_a02 External_a02_abc-ProdApp-10.255.192.0/24          Direct

How can I list all the VM's from each VLAN ?

The reason for this is we need to move servers from one VLAN to another and set it as DHCP.  The work above will be use to check the work.

Produce the VMs from within each VLAN showing the VM,Network VLAN,IP address , Manual or static.

Once we make the move then we will re-done it so that we can see that they have been moved .

I am trying to configure SRM8.2 for windows and windows based vcenter but I am getting an error."nvocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out" Not sure what I am doing wrong, The SRM server and vcenter have dns configured with fqdn and checks out correctly. No ports are blocked by the firewall. The error is followed by what I can call a soft crash of SRM because I loose the connection the srm server. "SRM Server at srmvm04cert.xxxxx is unreachable

Failed to connect to Site Recovery Manager Server at https://srmvm04cert.xxxx:9086/vcdr/vmomi/sdk. Reason: https://srmvm04cert.xxxx:9086/vcdr/vmomi/sdk invocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out

Operation ID: 769b7972-3f9f-4411-8986-750387d176b0

Any help will be appreaciated.

I am using SRM 8.2 (VMware-srm-8.2.0-13480383) and vcenter is 67u2b

i have a VM using half of avail space on a 500GB drive. i wanted to expand it to use the remaing ~250gb. i entered the max value listed in hardware settings for VM disk. appears that was too much and now a swap partition can't load.

can i save this VM another way or is shrinking the only way? 

from another post here i saw this.

  virtualman.wordpress.com/2016/02/24/shrink-a-vmware-virtual-machine-disk-vmdk/

1. but my VM won't even boot up so i can go and shrink disk.
2. from the instructions it mentions migrate or copy...do i have to migrate or copy it to another datastore? would prefer to use the whole drive it is currently on.

tia

following are the error messages.

----------------------------------------------------------------
msg when power on attempt:   Failed to power on virtual machine [name]. Module 'MonitorLoop' power on failed. Click here for more details."

-----------------------------------------------------------------
Failed - Module 'MonitorLoop' power on failed.
Errors

    Module 'MonitorLoop' power on failed.
    Failed to extend swap file /vmfs/volumes/[name of swap vswp].vswp from 0 KB to 12582912 KB : No space left on device
    Current swap file size is 0 KB.
    Failed to extend the virtual machine swap file
    Could not power on virtual machine: No space left on device.
    Failed to power on VM.
    Failed to start the virtual machine.

msg when editing VM hardware configuration:   
    Enter a disk size which is larger than its original capacity.

-----------------------------------------------------------------
storage stat for this disk:

STORAGE  FREE: 444 MB
                       100%
USED:             465.07 GB
CAPACITY:      465.5 GB
-----------------------------------------------------------------

Hi there,

I'm new to PowerCLI and also to PowerShell, and I think I'm missing something but I can't help to find out what is going on. I'm writing a script that takes a vAPP from a catalog which has a VM inside I can manage to add it a new network to work with but when I try to remove it fails randomly. Find below the piece of code I'm using to add the network (always work like a charm) and the piece of code to remove it (that inexplicably sometimes work and sometimes doesn't)

# Adding the network correctly

$myVapp = Get-CIVApp -orgvdc $orgvdc -name $vapp_New_Name

$myOrgVdcNetwork = Get-OrgVdcNetwork -name $orgVdc_Network_Name -OrgVdc $orgVdc

New-CIVAppNetwork -VApp $myVapp -Direct -ParentOrgVdcNetwork $myOrgVdcNetwork

#Then I try to remove it

$myVapp = Get-CIVApp -orgvdc $orgvdc -name $vapp_New_Name

Get-CIVApp -Name $myVapp | Get-CIVAppNetwork | Remove-CIVAppNetwork -Confirm:$false

Bellow is the error reported randomly:

Get-CIVApp -Name $myVapp | Get-CIVAppNetwork | Remove-CIVAppNetwork -Confirm:$false

Remove-CIVAppNetwork : 6/6/2019 8:15:46 PM Remove-CIVAppNetwork The operation cannot be performed because an input object contains stale data. The object named 'Public_Tenant' contains data which no longer corresponds to the the actual state of the

server. To resolve the issue retrieve a fresh copy of the object from the server and use it to perform the operation.

At line:2 char:48

+ ... me $myVapp | Get-CIVAppNetwork | Remove-CIVAppNetwork -Confirm:$false

+                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Remove-CIVAppNetwork], CIException

    + FullyQualifiedErrorId : CloudImpl_VAppNetworkUpdateHelper_UpdateVAppNetworkUplinkSettings_CIError,VMware.VimAutomation.Cloud.Commands.Cmdlets.VApp.RemoveCiVAppNetwork

Any help would be very appreciated.

Br,

/A

Noticed during the upgrade of vCenter 6.0 to 6.7 it says specifiy the VM settings for the appliance to be deployed.

VM Name =

I want to keep it the same name as we currently use as there are external systems etc that hook into vCenter. How do i keep the same name or am i doing something wrong here?

Thanks,

Adam

Hi,

I'm trying to assign each tag assigned to a VM to a separate variable. If I run the command below it'll store all of the tags in the $allTags variable:

$allTags = Get-VM "testVM" | Get-TagAssignment | Out-String

Lets say for example the VM "testVM" has three tag categories with tags assigned to each:

1. Tag category = Application; Tag = "SQL"

2. Tag category = OS; Tag = "Windows Server 2016"

3. Tag category = Backup; Tag ="Yes"

How would I store each tag into a unique variable? I've tried using the example below but it fails and I cant for the life of me figure this one out.

e.g. $appTag = $allTags.Tag.Application

this is upgrade log:

Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

   VIBs Installed: VMW_bootbank_bnxtnet-unstable_20.6.101.7-36vmw.691.0.0.14086596, VMW_bootbank_bnxtnet_20.6.101.7-25vmw.691.0.0.14086596, VMW_bootbank_bnxtroce-unstable_20.6.101.0-28vmw.691.0.0.14086596, VMW_bootbank_bnxtroce_20.6.101.0-21vmw.691.0.0.14086596, VMW_bootbank_brcmfcoe-unstable_12.0.1230.0-1vmw.691.0.0.14086596, VMW_bootbank_brcmfcoe_11.4.1078.25-14vmw.691.0.0.14086596, VMW_bootbank_brcmnvmefc_12.4.212.0-4vmw.691.0.0.14086596, VMW_bootbank_elxiscsi_11.4.1174.0-4vmw.691.0.0.14086596, VMW_bootbank_elxnet_11.4.1097.0-5vmw.691.0.0.14086596, VMW_bootbank_i40en-unstable_1.8.1.10-2vmw.691.0.0.14086596, VMW_bootbank_i40en_1.8.1.10-2vmw.691.0.0.14086596, VMW_bootbank_i40iwn-unstable_1.1.1.1-1vmw.691.0.0.14086596, VMW_bootbank_iavmd-unstable_2.0.0.1055-1vmw.691.0.0.14086596, VMW_bootbank_iavmd_1.2.0.1011-3vmw.691.0.0.14086596, VMW_bootbank_icen-unstable_1.0.0.0-1vmw.691.0.0.14086596, VMW_bootbank_igbn_0.1.1.0-5vmw.691.0.0.14086596, VMW_bootbank_iser-unstable_1.0.0.0-1vmw.691.0.0.14086596, VMW_bootbank_iser_1.0.0.0-1vmw.691.0.0.14086596, VMW_bootbank_ixgben-unstable_1.7.1.18-2vmw.691.0.0.14086596, VMW_bootbank_ixgben_1.7.1.18-2vmw.691.0.0.14086596, VMW_bootbank_lpfc-unstable_12.4.214.0-2vmw.691.0.0.14086596, VMW_bootbank_lpfc_11.4.33.26-15vmw.691.0.0.14086596, VMW_bootbank_lpnic_11.4.62.0-1vmw.691.0.0.14086596, VMW_bootbank_lsi-mr3-unstable_7.710.05.00-1vmw.691.0.0.14086596, VMW_bootbank_lsi-mr3_7.708.07.00-3vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt2-unstable_20.00.05.00-2vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt2_20.00.06.00-2vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt3-unstable_17.00.01.00-3vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt35-unstable_11.00.00.00-2vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt35_09.00.00.00-4vmw.691.0.0.14086596, VMW_bootbank_lsi-msgpt3_17.00.02.00-1vmw.691.0.0.14086596, VMW_bootbank_mtip32xx-native_3.9.8-1vmw.691.0.0.14086596, VMW_bootbank_ne1000_0.8.4-9vmw.691.0.0.14086596, VMW_bootbank_nenic-unstable_1.0.30.0-1vmw.691.0.0.14086596, VMW_bootbank_nenic_1.0.29.0-1vmw.691.0.0.14086596, VMW_bootbank_nfnic-unstable_4.0.0.36-1vmw.691.0.0.14086596, VMW_bootbank_nfnic_4.0.0.29-1vmw.691.0.0.14086596, VMW_bootbank_nhpsa-unstable_2.0.42-2vmw.691.0.0.14086596, VMW_bootbank_nhpsa_2.0.22-10vmw.691.0.0.14086596, VMW_bootbank_nmlx4-core-unstable_3.19.16.3-1vmw.691.0.0.14086596, VMW_bootbank_nmlx4-core_3.17.13.2-1vmw.691.0.0.14086596, VMW_bootbank_nmlx4-en-unstable_3.19.16.3-1vmw.691.0.0.14086596, VMW_bootbank_nmlx4-en_3.17.13.2-1vmw.691.0.0.14086596, VMW_bootbank_nmlx4-rdma-unstable_3.19.16.3-1vmw.691.0.0.14086596, VMW_bootbank_nmlx4-rdma_3.17.13.2-1vmw.691.0.0.14086596, VMW_bootbank_nmlx5-core-unstable_4.19.16.3-1vmw.691.0.0.14086596, VMW_bootbank_nmlx5-core_4.17.13.2-1vmw.691.0.0.14086596, VMW_bootbank_nmlx5-rdma-unstable_4.19.16.3-1vmw.691.0.0.14086596, VMW_bootbank_nmlx5-rdma_4.17.13.2-1vmw.691.0.0.14086596, VMW_bootbank_ntg3_4.1.3.3-1vmw.691.0.0.14086596, VMW_bootbank_nvme-pcie_1.2.2.11-1vmw.691.0.0.14086596, VMW_bootbank_nvme_1.2.2.29-1vmw.691.0.0.14086596, VMW_bootbank_nvmerdma_1.0.0.0-1vmw.691.0.0.14086596, VMW_bootbank_nvmxnet3-ens_2.0.0.21-1vmw.691.0.0.14086596, VMW_bootbank_nvmxnet3-unstable_2.0.0.29-1vmw.691.0.0.14086596, VMW_bootbank_nvmxnet3_2.0.0.29-1vmw.691.0.0.14086596, VMW_bootbank_pvscsi_0.1-2vmw.691.0.0.14086596, VMW_bootbank_qcnic-unstable_1.0.15.0-5vmw.691.0.0.14086596, VMW_bootbank_qcnic_1.0.15.0-5vmw.691.0.0.14086596, VMW_bootbank_qedentv-unstable_3.9.18.0-16vmw.691.0.0.14086596, VMW_bootbank_qedentv_3.9.18.0-16vmw.691.0.0.14086596, VMW_bootbank_qedrntv_3.9.18.0-7vmw.691.0.0.14086596, VMW_bootbank_qfle3-unstable_1.0.65.0-16vmw.691.0.0.14086596, VMW_bootbank_qfle3_1.0.65.0-16vmw.691.0.0.14086596, VMW_bootbank_qfle3f-unstable_1.0.51.0-12vmw.691.0.0.14086596, VMW_bootbank_qfle3f_1.0.51.0-12vmw.691.0.0.14086596, VMW_bootbank_qfle3i-unstable_1.0.15.0-4vmw.691.0.0.14086596, VMW_bootbank_qfle3i_1.0.15.0-4vmw.691.0.0.14086596, VMW_bootbank_qflge_1.1.0.11-1vmw.691.0.0.14086596, VMW_bootbank_rste_2.0.2.0088-7vmw.691.0.0.14086596, VMW_bootbank_sfvmk-unstable_2.0.0.1004-2vmw.691.0.0.14086596, VMW_bootbank_sfvmk_2.0.0.1004-2vmw.691.0.0.14086596, VMW_bootbank_smartpqi_1.0.1.553-35vmw.691.0.0.14086596, VMW_bootbank_vmkata_0.1-1vmw.691.0.0.14086596, VMW_bootbank_vmkfcoe_1.0.0.2-1vmw.691.0.0.14086596, VMW_bootbank_vmkusb_0.1-1vmw.691.0.0.14086596, VMW_bootbank_vmw-ahci-unstable_1.3.3-1vmw.691.0.0.14086596, VMW_bootbank_vmw-ahci_1.3.8-1vmw.691.0.0.14086596, VMware_bootbank_cpu-microcode_6.9.1-0.0.14086596, VMware_bootbank_elx-esx-libelxima.so_11.4.1184.5-0.0.14086596, VMware_bootbank_esx-base_6.9.1-0.0.14086596, VMware_bootbank_esx-dvfilter-generic-fastpath_6.9.1-0.0.14086596, VMware_bootbank_esx-ui_1.33.4-13978685, VMware_bootbank_esx-update_6.9.1-0.0.14086596, VMware_bootbank_esx-xserver_6.9.1-0.0.14086596, VMware_bootbank_loadesx_6.9.1-0.0.14086596, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-17vmw.691.0.0.14086596, VMware_bootbank_lsu-intel-nvme-vmd-plugin_1.0.0-0vmw.691.0.0.14086596, VMware_bootbank_lsu-intel-vmd-plugin_1.0.0-2vmw.691.0.0.14086596, VMware_bootbank_lsu-lsi-drivers-plugin_1.0.0-4vmw.691.0.0.14086596, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-13vmw.691.0.0.14086596, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_2.0.0-3vmw.691.0.0.14086596, VMware_bootbank_lsu-smartpqi-plugin_1.0.0-3vmw.691.0.0.14086596, VMware_bootbank_lsuv2-intelv2-nvme-vmd-plugin_1.0.0-1vmw.691.0.0.14086596, VMware_bootbank_lsuv2-intelv2-vmd-plugin_1.0.0-1vmw.691.0.0.14086596, VMware_bootbank_lsuv2-lsiv2-drivers-plugin_1.0.0-1vmw.691.0.0.14086596, VMware_bootbank_native-misc-drivers_6.9.1-0.0.14086596, VMware_bootbank_qlnativefc-unstable_4.0.2.0-1vmw.691.0.0.14086596, VMware_bootbank_qlnativefc_4.0.1.0-1vmw.691.0.0.14086596, VMware_bootbank_vdfs_6.9.1-0.0.14086596, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_1.2.0.37-0.0.14086596, VMware_bootbank_vsan_6.9.1-0.0.14086596, VMware_bootbank_vsanhealth_6.9.1-0.0.14086596

   VIBs Removed: VMWARE_bootbank_mtip32xx-native_3.8.5-1vmw.600.0.0.2494585, VMware_bootbank_ata-pata-amd_0.3.10-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-atiixp_0.4.6-4vmw.600.0.0.2494585, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-via_0.3.3-2vmw.600.0.0.2494585, VMware_bootbank_block-cciss_3.6.14-10vmw.600.0.0.2494585, VMware_bootbank_cpu-microcode_6.0.0-0.0.2494585, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.600.0.0.2494585, VMware_bootbank_elxnet_10.2.309.6v-1vmw.600.0.0.2494585, VMware_bootbank_emulex-esx-elxnetcli_10.2.309.6v-0.0.2494585, VMware_bootbank_esx-base_6.0.0-1.17.3029758, VMware_bootbank_esx-dvfilter-generic-fastpath_6.0.0-0.0.2494585, VMware_bootbank_esx-tboot_6.0.0-0.0.2494585, VMware_bootbank_esx-xserver_6.0.0-0.0.2494585, VMware_bootbank_ima-qla4xxx_2.02.18-1vmw.600.0.0.2494585, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.600.0.0.2494585, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.600.0.0.2494585, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.600.0.0.2494585, VMware_bootbank_lpfc_10.2.309.8-2vmw.600.0.0.2494585, VMware_bootbank_lsi-mr3_6.605.08.00-7vmw.600.1.17.3029758, VMware_bootbank_lsi-msgpt3_06.255.12.00-8vmw.600.1.17.3029758, VMware_bootbank_lsu-hp-hpsa-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-2vmw.600.0.11.2809209, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-2vmw.600.0.11.2809209, VMware_bootbank_lsu-lsi-mpt2sas-plugin_1.0.0-4vmw.600.1.17.3029758, VMware_bootbank_lsu-lsi-mptsas-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.600.0.0.2494585, VMware_bootbank_misc-drivers_6.0.0-1.17.3029758, VMware_bootbank_net-bnx2_2.2.4f.v60.10-1vmw.600.0.0.2494585, VMware_bootbank_net-bnx2x_1.78.80.v60.12-1vmw.600.0.0.2494585, VMware_bootbank_net-cnic_1.78.76.v60.13-2vmw.600.0.0.2494585, VMware_bootbank_net-e1000_8.0.3.1-5vmw.600.0.0.2494585, VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585, VMware_bootbank_net-enic_2.1.2.38-2vmw.600.0.0.2494585, VMware_bootbank_net-forcedeth_0.61-2vmw.600.0.0.2494585, VMware_bootbank_net-igb_5.0.5.1.1-5vmw.600.0.0.2494585, VMware_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.600.0.0.2494585, VMware_bootbank_net-mlx4-core_1.9.7.0-1vmw.600.0.0.2494585, VMware_bootbank_net-mlx4-en_1.9.7.0-1vmw.600.0.0.2494585, VMware_bootbank_net-nx-nic_5.0.621-5vmw.600.0.0.2494585, VMware_bootbank_net-tg3_3.131d.v60.4-1vmw.600.0.0.2494585, VMware_bootbank_net-vmxnet3_1.1.3.0-3vmw.600.0.0.2494585, VMware_bootbank_nmlx4-core_3.0.0.0-1vmw.600.0.0.2494585, VMware_bootbank_nmlx4-en_3.0.0.0-1vmw.600.0.0.2494585, VMware_bootbank_nmlx4-rdma_3.0.0.0-1vmw.600.0.0.2494585, VMware_bootbank_nvme_1.0e.0.35-1vmw.600.1.17.3029758, VMware_bootbank_ohci-usb-ohci_1.0-3vmw.600.0.0.2494585, VMware_bootbank_qlnativefc_2.0.12.0-5vmw.600.0.0.2494585, VMware_bootbank_rste_2.0.2.0088-4vmw.600.0.0.2494585, VMware_bootbank_sata-ahci_3.0-22vmw.600.1.17.3029758, VMware_bootbank_sata-ata-piix_2.12-10vmw.600.0.0.2494585, VMware_bootbank_sata-sata-nv_3.5-4vmw.600.0.0.2494585, VMware_bootbank_sata-sata-promise_2.12-3vmw.600.0.0.2494585, VMware_bootbank_sata-sata-sil24_1.1-1vmw.600.0.0.2494585, VMware_bootbank_sata-sata-sil_2.3-4vmw.600.0.0.2494585, VMware_bootbank_sata-sata-svw_2.3-3vmw.600.0.0.2494585, VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.600.0.0.2494585, VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.600.0.0.2494585, VMware_bootbank_scsi-aic79xx_3.1-5vmw.600.0.0.2494585, VMware_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.600.0.0.2494585, VMware_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.600.0.11.2809209, VMware_bootbank_scsi-fnic_1.5.0.45-3vmw.600.0.0.2494585, VMware_bootbank_scsi-hpsa_6.0.0.44-4vmw.600.0.0.2494585, VMware_bootbank_scsi-ips_7.12.05-4vmw.600.0.0.2494585, VMware_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.600.0.0.2494585, VMware_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.600.0.0.2494585, VMware_bootbank_scsi-megaraid2_2.00.4-9vmw.600.0.0.2494585, VMware_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.600.0.0.2494585, VMware_bootbank_scsi-mptsas_4.23.01.00-9vmw.600.0.0.2494585, VMware_bootbank_scsi-mptspi_4.23.01.00-9vmw.600.0.0.2494585, VMware_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.600.0.0.2494585, VMware_bootbank_uhci-usb-uhci_1.0-3vmw.600.0.0.2494585, VMware_bootbank_vsanhealth_6.0.0-3000000.2.0.1.17.2972216, VMware_bootbank_xhci-xhci_1.0-2vmw.600.1.17.3029758

   VIBs Skipped: VMware_locker_tools-light_11.0.0.14076833-14086596

=======================================================================

I use command "esxcli software profile update --depot=file:///vmfs/volumes/d22e25e3-32840465/VMware-ESXi-6.9.1-14086596-depot.zip -p ESXi-6.9.1-14086596-standard --no-sig-check"

to upgrade my host.

it removes some vibs, such as scsi-adp94xx.

So there is no drives, and the storage is 0 byte.

Thanks

we are planning to create one common vcenter for some use case

My question: based on current assessment, we came to deploy it as small size, lets assume down the road, if we need to change VC size from small to large is it possible?

Thank you,
Volga.

Добрый день, у меня не отображается история нагрузки CPU больше чем за 60 минут. Как это исправить?