Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels

Channel Catalog

Channel Description:

Most recent forum messages

older | 1 | .... | 6702 | 6703 | (Page 6704) | 6705 | 6706 | .... | 6709 | newer

    0 0




    Note there is also memory consumption for ESXi (already accounted for if you are running on this) and additional memory overhead per vSAN disk-group and varying depending if Hybrid or AF, this outlines these:


    Sure, you *could* likely set-up a vSAN using an onboard controller (I tried to find specs of what comes on a 5028D-TN4T but none found easily) but this would likely not function very well due to the low Queue Depth typically capable on these types of devices, pretty much nullifying the benefit of All-Flash and even vSAN at all really.

    It would likely end up being a bad bottleneck, depping covered this topic long ago:


    For a comparison of what should be expected minimum Queue Depth you can refer to even the lowest-capacity/specs ready-node require minimum >256 Queue Depth, which is the minimum requirement for vSAN:





    -o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-

    0 0

    Imitkov17: Just wanted to let you know that I just fixed the "Startup" bug (instead of creating the shortcut in a "Startup" sub folder of the (possibly redirected) Programs Menu, we'll create it in the actual "Startup" folder). This bug goes all the way back to the initial implementation of the shortcut creation feature which is now more than five years ago, so: good find :-)

    I can't make any statements regarding release dates, but you already found a functioning workaround for now. I've also filed your feature request about folder redirection for the Startup folder.


    As for brainstorming on your other questions: by all means! But indeed, please start a separate thread for that (or maybe even multiple ones?), just to keep things clear. (And, most important, to be able to score some more Correct Answer points :-)

    0 0

    A "shared folder" on a VMware host accessed from any VM guest is not exactly the same as a regular shared network folder.


    A VMware shared folder would be using the vmhgfs.sys and related drivers while a regular network share will be accessed by the Windows OS through RPC. That is why VMware shared folders will only work if VMware Tools are installed in the guest VM (as it also installs vmhgfs services).


    It is more likely DrvFs only supports the regular network shares and not the hgfs VMware shared folder.

    0 0
  • 06/22/17--17:43: Re: NSX Edge Gateway - HA

    I had the above scenario.

    The edge gateway was in Active - Standby. I have kept the OSPF timers as 30 & 120 as recommended by VMware. The HA Dead timer = 9  seconds recommended by VMWare.

    When I shutdown the active Edge Gateway , there was interruption of nearly 150 seconds for the north south traffic.

    The switch over of Edge gateway from Active - Standby was ok but there is long interruption of 150 seconds with the timers of 30/120 OSPF recommended by VMWare.

    Is this normal ?

    If it is normal what is the reason for this.


    Request any ones input at the earliest.

    0 0

    I am still seeing a noticeable difference in performance on
    host 6.0.0, 5224934
    vmtools 10.0.9

    using vmxnet3

    exchange 2016, windows 2012r2, windows 7 clients.


    messing with the ack on clients does resolve it but not something we want to engage in.

    0 0

    Hello Guys,


    I have the same issue after installing Firefox 44.0 Windows 7 or 10 and Client integration Plugin 6.0.0. After installing the fire fox 44.0 we are able to install the Client Integration Plugin on the server.


    We had to deinstall Firefox and the Client Integration Plugin and delete the complete Firefox Profile (only the places.sqlite we import to the new installation).


    After restart and complete new installation (ff 44.0 and CIP 6.0.0) it works.


    Follow the below link to fix this issue.


    1195768 - Problem with VMWare Client Integration Plugin

    0 0
  • 06/22/17--18:03: Re: NSX Monitoring
  • I understand that Log Insight can be used for Monitoring but is there any way I can monitor NSX components by inbuild features of NSX or vCenter to generate alerts or error messges.

    0 0

    Here is the error in vRealize Log Insight.


    0 0

    We managed to get the image imported by changing the glance-api.conf


    The default setting is


    default-store= vi


    We changed it to


    default-store= file


    Now the image imports but the image is stored in /var/lib/glance/images and not on the vSAN datastore.


    I think we may have to modify the glance-api.conf file so that it stores in a directory on the vSAN datastore. There is a setting in the configuration file.


    We shall give it a go and report back soon.

    0 0

    OK thanks - it's erroring out though:


    Get-View : Cannot bind parameter 'Id'. Cannot convert the

    "VMware.Vim.DatastoreHostMount" value of type "VMware.Vim.DatastoreHostMount" to

    type "VMware.Vim.ManagedObjectReference".

    At C:\scripts\vmware_remove_datastores.ps1:22 char:25

    +     $esx = Get-View -Id $[0]

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

        + CategoryInfo          : InvalidArgument: (:) [Get-View], ParameterBindingExce


        + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,VMware.VimAutomation.V



    Any ideas?  I'm sure it is getting the datastore OK and passing it down the pipe but it looks like $[0] isn't returning a result...

    0 0

    Thank you very much for the answer Warren! 

    0 0



    We got some HP ProLiant Gen9 boxes running ESXi 6.0 Update 2.


    Today I've applied ESXi-6.0.0-20170604001-standard patch and rebooted the server. There was no issues during the patching process at all.


    But after ESXi got rebooted, the local disks are not going to be shown on vSphere client. Also an alert about non-persistent syslog are shown.


    This is a totally odd situation, because apparently the RAID controller is detected during boot, but after ESXi is loaded, there are no local disks being shown, and we are unable to access it also via SSH, as it doesn't appears as a mounted device / vmfs volume.


    After rolling back the update, we got local disks showing again.


    I am thinking in reapply this update without installing the scsi-hpsa vib which I think that could be the problem as it was reported in an KB about causing controller detection issues, but it was on 6.0U1:


    VMware ESXi 6.0 host fails to detect local disk after patching or applying Update 1 on HP Proliant Gen 9 servers (212053…


    So, have someone any clue about this case?


    Thank you in advance!

    0 0



    I’m running a macOS Sierra 10.12.5 VM on ESXi 6.5 but when I change the VM resolution to the same as the native resolution of my MacBook Pro 15” w/ Retina (2880×1800) the image is too large for the screen. A VM resolution of 1440×900 creates the correct size image but it’s not very sharp; it’s somewhat blurry. Any idea on how I can correct this? Thanks in advance!




    0 0
  • 06/22/17--19:56: Re: VCSA 6.0 ISO?
  • 0 0

    VMware 12.5.7 is out, and I can confirm that this now works OK with Kernel 4.12 (tested with 4.12-rc6)




    Robert Gadsdon

    0 0

    Thanks for your help~ Sureshkumar M,


    Actually, I have a Windows 7 VM, which is the thin-provisioned VM and the used space is 75.6GB.

    Current VM spaces (Used 75.6GB):



    Current datastore used space on the VM (Have the Virtual Disk of the VM used 85,829,632.00 KB  ~around 85 GB):



    Can reclaim the space of 10 GB back???... Now, I deleted more 5GB. When can it reclaim back? Local Disk cannot reclaim??


    0 0

    Have configured alarm action to run a command, Is there a way for me to pass the Esxi host name for which the alarm has been triggered ?



    0 0

    BACKUP THE DATABASE, then connect to the database and execute the SQL command:


    alter table VPX_EXT_PRIVS drop constraint PK_VPX_EXT_PRIVS


    ...then try the upgrade again.



    vCenter Upgrade from 5.1 to 6.0 with external SQL 2008 fails during schema validation

    0 0

    How Storage vMotion Works

    1. First, vSphere copies over the nonvolatile files that make up a VM: the configuration file (VMX), VMkernel swap, log files, and snapshots.

    2. Next, vSphere starts a ghost or shadow VM on the destination datastore. Because thisghost VM does not yet have a virtual disk (that hasn’t been copied over yet), it sits idle waiting for its virtual disk.

    3. Storage vMotion fi rst creates the destination disk. Then a mirror device—a new driver that mirrors I/Os between the source and destination—is inserted into the data path between the VM and the underlying storage. SVM Mirror Device Information in the Logs If you review the vmkernel log fi les on an ESXi host during and after a Storage vMotion operation, you will see log entries prefi xed with SVM that show the creation of the mirror device and that provide information about the operation of the mirror device.

    4. With the I/O mirroring driver in place, vSphere makes a single-pass copy of the virtual disk(s) from the source to the destination. As changes are made to the source, the I/O mirror driver ensures that those changes are also reflected at the destination.

    5. When the virtual disk copy is complete, vSphere quickly suspends and resumes in order to transfer control over to the ghost VM created on the destination datastore earlier. This generally happens so quickly that there is no disruption of service, as with vMotion.

    6. The files on the source datastore are deleted.


    Book Titled "Mastering VMware vSphere 5.5" by Nick Marshall and Scott Lowe



    Note: More on I/O mirroring driver

    • fsdm

    – This is the legacy Data Mover, the most basic version. It is the slowest because the data moves all the

    way up the stack and then down again.

    • fs3dm

    (software) – This is the software Data Mover, which was introduced with vSphere 4.0 and contained

    some substantial optimizations whereby data does not travel through all stacks.

    • fs3dm

    (hardware) – This is the hardware offload Data Mover, introduced with vSphere 4.1. It still is the fs3dm,

    but VAAI hardware offload is leveraged with this version. fs3dm is used in software mode when hardware

    offload (VAAI) capabilities are not available.





    When the source filesystem uses a different  blocksize from the destination filesystem, the legacy datamover (FSDM) is used. When the blocksizes of source and destination are equal, the new datamover (FS3DM) is used. FS3DM uses VAAI or just the software component. In either case, null blocks are not reclaimed.


    Storage vMotion to thin disk does not reclaim null blocks (2004155) | VMware KB



    If you found this or any other answer helpful, please consider the use of the Helpful to award points.


    Best Regards,

    Deepak Koshal


    0 0

    Is there a way to show these relationships in vRA?  Ideally, we'd want all the networks and associated items that come along with the deployment to fall under a parent/child relationship.



older | 1 | .... | 6702 | 6703 | (Page 6704) | 6705 | 6706 | .... | 6709 | newer