The same thing happens to me every time I resume my Windows 10 vm after suspending it and putting macOS to sleep.  This needs to get fixed, but my workaround for now it to completely shut down the vm before putting macOS to sleep.

This may be a stupid question, but I feel the need to ask it anyway.

I am using a Dell PowerEdge R610 with a PERC H200 and I was thinking about experimenting with an all-flash array. Does VMware's vSAN do trim or unmap or something of that sort to take care of the SSD's? I haven't been able to find any information about this. Is TRIM even needed? If not, then how long would the SSD's last realistically?

Thank you for any information anyone could provide on this subject.

what is the power management policy. some people says power management must be high . Also i am using hp server and there are power management policy in hp server. this is same policy ? if i change power management policy to high on vcenter then hp power management policy will change automaticly or i must change both ? how i make a true design

This actually sounds like some slightly different issues that could vary with apple hardware, but seems to all be related to Sierra

Mine specifically is on an iMac with an Apple Fusion 1TB drive.

After multiple ways to reproduce it in my case, there is no VM only crashes, the entire iMac becomes frozen unresponsive, fans are cranked, and it needs a power button reset.  I have reproduced this ONLY when Fusion is running active VM's AND if the iMac is set to sleep normally.  If I enable the option to NEVER allow the system to sleep....then things continue to run fine.  Also the apple logs collected and sent to Apple engineering indicate IN MY CASE that there is a failure with sleep/wake operations flagged along side fusion.

So it seems there is a few variations of this problem but they are clearly related to Sierra and VMware Fusion, but not sure if it's affecting SSD's or spindles only.  Also on my MacBook I always suspend VM's I'm not using which I cannot do on the iMac, so I have yet to see the issue on my MacBook which is also set to never sleep when on power adapter.  Not sure why I just have always had it set that way since it sleeps when you close the cover anyhow.  Different options on the iMac power settings.

HTML Client SDK Fling 6 is available!

Go to the vSphere HTML5 Web Client Fling page, click on the drop down in the left and select  html-client-sdk-6.5.0-4507438.zip

FYI, Fling 6 is at the same level as the HTML Client SDK included in the upcoming vSphere 6.5 release, i.e. the supported version.

The updated Getting Started PDF file is included in the .zip.

The release notes for Fling 6 are attached here.

I ran into the same issue recently, while trying to automate pool creation and enabling both View Accelerator & VAAI for composer linked clone pools. From what I can tell, the capabilities seems limited to GUI (Admin Console) only, and aren't exposed in the PowerShell SDK.

Have there been any findings in this area? Or an alternate approach.

Thanks!

if i attach any usb device =  The connection for the USB device was unsuccess

the net service usb is running

here the logfile

2016-10-20T14:54:15.418+02:00| usbArb| I120: Log for VMware USB Arbitration Service pid=2024 version=5.0.0 build=build-799535 option=Release
2016-10-20T14:54:15.418+02:00| usbArb| I120: The process is 64-bit.
2016-10-20T14:54:15.418+02:00| usbArb| I120: Host codepage=windows-1252 encoding=windows-1252
2016-10-20T14:54:15.418+02:00| usbArb| I120: Host is Windows 7 Ultimate, 64-bit Service Pack 1 (Build 7601)
2016-10-20T14:54:15.419+02:00| usbArb| I120: VTHREAD initialize main thread 2 "usbArb" host id 2028
2016-10-20T14:54:15.419+02:00| usbArb| I120: Msg_Reset:
2016-10-20T14:54:15.419+02:00| usbArb| I120: [msg.dictionary.load.openFailed] Cannot open file "C:\ProgramData\VMware\VMware USB Arbitration Service\settings.ini": The system cannot find the file specified.
2016-10-20T14:54:15.419+02:00| usbArb| I120: ----------------------------------------
2016-10-20T14:54:15.419+02:00| usbArb| I120: PREF Optional preferences file not found at C:\ProgramData\VMware\VMware USB Arbitration Service\settings.ini. Using default values.
2016-10-20T14:54:15.419+02:00| usbArb| I120: PREF Disabling user preferences because disableUserPreferences is set.
2016-10-20T14:54:15.419+02:00| usbArb| I120: PREF Failed to load user preferences.
2016-10-20T14:54:15.419+02:00| usbArb| I120: POLL Using the WSAPoll API Implementation for PollDefault
2016-10-20T14:54:15.420+02:00| usbArb| I120: Hostinfo_OpenProcessBits: OpenProcess access bits are 1000.
2016-10-20T14:54:15.454+02:00| usbArb| I120: DICT --- USER PREFERENCES
2016-10-20T14:54:15.454+02:00| usbArb| I120: DICT --- USER DEFAULTS C:\Windows\syswow64\config\systemprofile\AppData\Roaming\VMware\config.ini
2016-10-20T14:54:15.454+02:00| usbArb| I120: DICT --- HOST DEFAULTS C:\ProgramData\VMware\VMware USB Arbitration Service\config.ini
2016-10-20T14:54:15.454+02:00| usbArb| I120: DICT --- SITE DEFAULTS C:\ProgramData\VMware\VMware USB Arbitration Service\config.ini
2016-10-20T14:54:15.454+02:00| usbArb| I120: VMware USB Arbitration Service Version 10.1.14
2016-10-20T14:54:15.456+02:00| vthread-3| I120: VTHREAD initialize thread 3 "vthread-3" host id 900
2016-10-20T14:54:15.456+02:00| vthread-3| I120: USBArb: Starting VMUSBArbService args:'VMUSBArbService'
2016-10-20T14:54:15.460+02:00| vthread-3| I120: USBGW: Host controller #0 = "\\?\HCD0"
2016-10-20T14:54:15.460+02:00| vthread-3| I120: USBGW: Host controller #1 = "\\?\HCD1"
2016-10-20T14:54:15.460+02:00| vthread-3| I120: USBGW: Host controller #9 = "\\?\HCD9"
2016-10-20T14:54:15.460+02:00| vthread-3| I120: USBArb: Connected to HCMON version 3.16
2016-10-20T14:54:15.460+02:00| vthread-3| W110: USBArb: Failed to send HC Name:\??\HCD9 to HCMON: A device attached to the system is not functioning (31)
2016-10-20T14:54:16.626+02:00| vthread-4| I120: VTHREAD initialize thread 4 "vthread-4" host id 1116
2016-10-20T14:54:16.654+02:00| vthread-4| I120: HOSTINFO 398192885 @ 3897246Hz -> 0 @ 1000000000Hz
2016-10-20T14:54:16.654+02:00| vthread-4| I120: HOSTINFO ((x * 2152445085) >> 23) + -102172889494
2016-10-20T14:54:16.785+02:00| vthread-4| I120: USBArb: VMUSBArbService Started.
2016-10-20T14:54:16.789+02:00| vthread-3| I120: VTHREAD initialize thread 3 "vthread-3" host id 1296
2016-10-20T14:54:16.789+02:00| vthread-3| I120: USBArb-BT: Beginning inquiry thread
2016-10-20T14:54:18.655+02:00| vthread-4| W110: USBArbEnumerate: CM busy.
2016-10-20T14:54:18.746+02:00| vthread-4| W110: USBArbEnumerate exit: CM busy.
2016-10-20T15:50:29.663+02:00| vthread-4| I120: USBArb: Num instances:2, user:Phoenix
2016-10-20T15:50:29.663+02:00| vthread-4| I120: USBArb: Client 1868 connected (version: 6)
2016-10-20T15:50:35.421+02:00| vthread-4| I120: USBArb: Num instances:3, user:Phoenix
2016-10-20T15:50:35.421+02:00| vthread-4| I120: USBArb: Client 2884 connected (version: 6)
2016-10-20T15:50:35.421+02:00| vthread-4| I120: USBArb: Registered target 'vmware-vmx:C:\Users\Phoenix\Documents\Virtual Machines\Windows 7 ul vhd\Windows 7 ul vhd.vmx' for client 2884.
2016-10-20T15:53:19.699+02:00| vthread-4| I120: USBArb: Connecting device 0x1045e0291 to client 2884
2016-10-20T15:53:19.733+02:00| vthread-4| W110: USBArb: Submitting connect failed: Element not found 0x(490)
2016-10-20T15:53:19.733+02:00| vthread-4| W110: USBArb: Failed to connect device:1045e0291 to 'Windows 7 ul vhd'
2016-10-20T15:53:19.733+02:00| vthread-4| I120: USBArb: Connect failed:9
2016-10-20T15:53:19.952+02:00| vthread-4| I120: USBArb: Client 2884 trying to close id 1045e0291 it doesn't own.
2016-10-20T18:10:24.650+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:10:38.025+02:00| vthread-4| I120: USBArb: Num instances:3, user:Phoenix
2016-10-20T18:10:38.026+02:00| vthread-4| I120: USBArb: Client 4464 connected (version: 6)
2016-10-20T18:10:38.026+02:00| vthread-4| I120: USBArb: Registered target 'vmware-vmx:C:\Users\Phoenix\Documents\Virtual Machines\Windows 7 ul vhd\Windows 7 ul vhd.vmx' for client 4464.
2016-10-20T18:10:41.782+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:10:43.574+02:00| vthread-4| I120: USBArb: Num instances:3, user:Phoenix
2016-10-20T18:10:43.574+02:00| vthread-4| I120: USBArb: Client 7420 connected (version: 6)
2016-10-20T18:10:57.226+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:12:04.481+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:14:43.769+02:00| vthread-4| I120: USBArb: Num instances:2, user:Phoenix
2016-10-20T18:14:43.769+02:00| vthread-4| I120: USBArb: Client 5268 connected (version: 6)
2016-10-20T18:14:47.651+02:00| vthread-4| I120: USBArb: Num instances:3, user:Phoenix
2016-10-20T18:14:47.651+02:00| vthread-4| I120: USBArb: Client 4312 connected (version: 6)
2016-10-20T18:14:47.652+02:00| vthread-4| I120: USBArb: Registered target 'vmware-vmx:C:\Users\Phoenix\Documents\Virtual Machines\Windows 7 ul vhd\Windows 7 ul vhd.vmx' for client 4312.
2016-10-20T18:15:53.004+02:00| vthread-4| I120: USBArb: Connecting device 0x3046dc537 to client 4312
2016-10-20T18:15:53.004+02:00| vthread-4| W110: USBArb: Submitting connect failed: Element not found 0x(490)
2016-10-20T18:15:53.004+02:00| vthread-4| W110: USBArb: Failed to connect device:3046dc537 to 'Windows 7 ul vhd'
2016-10-20T18:15:53.004+02:00| vthread-4| I120: USBArb: Connect failed:9
2016-10-20T18:15:53.040+02:00| vthread-4| I120: USBArb: Client 4312 trying to close id 3046dc537 it doesn't own.
2016-10-20T18:22:05.766+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:22:30.435+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:22:32.467+02:00| vthread-4| I120: USBArb: Num instances:2, user:Phoenix
2016-10-20T18:22:32.467+02:00| vthread-4| I120: USBArb: Client 7148 connected (version: 6)
2016-10-20T18:22:39.677+02:00| vthread-4| I120: USBArb: Num instances:3, user:Phoenix
2016-10-20T18:22:39.677+02:00| vthread-4| I120: USBArb: Client 5228 connected (version: 6)
2016-10-20T18:22:39.678+02:00| vthread-4| I120: USBArb: Registered target 'vmware-vmx:C:\Users\Phoenix\Documents\Virtual Machines\Windows 7 ul vhd\Windows 7 ul vhd.vmx' for client 5228.
2016-10-20T18:37:45.721+02:00| vthread-4| I120: USBArb: Connecting device 0x5058f6387 to client 5228
2016-10-20T18:37:45.722+02:00| vthread-4| W110: USBArbRequestConnect: CM_Locate_DevNode returned 0xd
2016-10-20T18:37:45.722+02:00| vthread-4| W110: USBArb: Failed to connect device:5058f6387 to 'Windows 7 ul vhd'
2016-10-20T18:37:45.722+02:00| vthread-4| I120: USBArb: Connect failed:4
2016-10-20T18:37:45.790+02:00| vthread-4| I120: USBArb: Client 5228 trying to close id 5058f6387 it doesn't own.
2016-10-20T18:38:00.383+02:00| vthread-4| I120: USBArb: Connecting device 0x1045e0291 to client 5228
2016-10-20T18:38:00.384+02:00| vthread-4| W110: USBArb: Submitting connect failed: Element not found 0x(490)
2016-10-20T18:38:00.384+02:00| vthread-4| W110: USBArb: Failed to connect device:1045e0291 to 'Windows 7 ul vhd'
2016-10-20T18:38:00.384+02:00| vthread-4| I120: USBArb: Connect failed:9
2016-10-20T18:38:00.416+02:00| vthread-4| I120: USBArb: Client 5228 trying to close id 1045e0291 it doesn't own.
2016-10-20T18:42:00.383+02:00| vthread-4| I120: USBArb: Connecting device 0x5058f6387 to client 5228
2016-10-20T18:42:00.383+02:00| vthread-4| W110: USBArbRequestConnect: CM_Locate_DevNode returned 0xd
2016-10-20T18:42:00.384+02:00| vthread-4| W110: USBArb: Failed to connect device:5058f6387 to 'Windows 7 ul vhd'
2016-10-20T18:42:00.384+02:00| vthread-4| I120: USBArb: Connect failed:4
2016-10-20T18:42:00.455+02:00| vthread-4| I120: USBArb: Client 5228 trying to close id 5058f6387 it doesn't own.
2016-10-20T18:42:29.108+02:00| vthread-4| I120: USBArb: Client closed
2016-10-20T18:50:02.789+02:00| vthread-4| I120: USBArb: Client closed

maybe permssion problem or a file  is missing?

Hi,

I have experienced the same issue, and it has been reported, as a bug here "VMware Tools power-on script fails to run successfully (2010481)". link below:

"VMware Tools power-on script fails to run successfully (2010481) | VMware KB"

I myself have not made any changes to the script, did you resolve eventually and if so can you confirm what steps you took?, as the KB resolution, does seem to tie in, with, as I haven't made any changes to the script, and it was just a simple reboot, as I occasionally turn my Homelab (guests) infrastructure off, if I put my physical hosts into standby mode?

Cheers,

Hello,

I am trying to understand the way that the vSphere QueryPerf API works.  Comparing collections between the vCenter and the MOB, for an intervalId of 300 and a startTime of vCenter currentTime - 10 minutes, if I leave out the endTime from the PerfQuerySpec for a given VM/CPU metric, the results in the MOB lag the vCenter performance by about 5 minutes.  When I put the vCenter currentTime in the endTime property, the results are more in sync with that of the vCenter.

Judging from the documentation: "When endTime is omitted, the returned result includes up to the most recent metric value. When an endTime is specified, the returned samples include the sample at endTime", I would expect to get the same results in either case. Is there an explanation for what I am seeing?

This is more of a general question, but I can furnish more details.

Thanks in advance,

The reason host 3 shows as 10Gb is because you are using a vmxnet3 network adapter on the nested esxi host. So what I want you to show me is the actual configuration of the vswitch the nested esxi host resides in on host 2, like here

General

    Name:    DMZ

    Port binding:    Static binding

    Port allocation:    Elastic

    Number of ports:    8

    Network resource pool:    (default)

Advanced

    Configure reset at disconnect:    Enabled

Override port policies

    Block ports:    Allowed

    Traffic shaping:    Disabled

    Vendor configuration:    Disabled

    VLAN:    Disabled

    Uplink teaming:    Disabled

    Security policy:    Disabled

    NetFlow:    Disabled

    Traffic filtering and marking:    Disabled

Security

    Promiscuous mode:    Reject

    MAC address changes:    Reject

    Forged transmits:    Reject

Ingress traffic shaping

    Status:    Disabled

    Average bandwidth:    --

    Peak bandwidth:    --

    Burst size:    --

Egress traffic shaping

    Status:    Disabled

    Average bandwidth:    --

    Peak bandwidth:    --

    Burst size:    --

VLAN

    Type:    VLAN

    VLAN ID:    xx

Teaming and failover

    Load balancing:    Route based on originating virtual port

    Network failure detection:    Link status only

    Notify switches:    Yes

    Failback:    Yes

    Active uplinks:    Uplink 1

    Standby uplinks:    Uplink 2

    Unused uplinks:    Uplink 3, Uplink 4, lag1

Monitoring

    NetFlow:    Disabled

Traffic filtering and marking

    Status:    Disabled

Miscellaneous

    Block all ports:    No

Do the same with your vmk ports

Port properties

    Network label    VSAN-DPG

    TCP/IP stack    Default

    Enabled services    Virtual SAN traffic

IPv4 settings

    IPv4 address    xxxxx (static)

    Subnet mask  xxxxx

    Default gateway for IPv4    xxxxx

    DNS server addresses  xxxxx

               xxxxxxx

NIC settings

    MAC address    xxxxxxxxxx

    MTU    9000

Security

    Promiscuous mode:    Reject

    MAC address changes:    Reject

    Forged transmits:    Reject

Ingress traffic shaping

    Status:    Disabled

    Average bandwidth:    --

    Peak bandwidth:    --

    Burst size:    --

Egress traffic shaping

    Status:    Disabled

    Average bandwidth:    --

    Peak bandwidth:    --

    Burst size:    --

VLAN

    Type:    None

Teaming and failover

    Load balancing:    Route based on physical NIC load

    Network failure detection:    Link status only

    Notify switches:    Yes

    Failback:    Yes

    Active uplinks:    Uplink 1

    Standby uplinks:    Uplink 2

    Unused uplinks:   

Monitoring

    NetFlow:    Disabled

Traffic filtering and marking

    Status:    Disabled

Miscellaneous

    Block all ports:    No

I appreciate the information. I do understand the difference there between Trim and Unmap, one being ATA and the other bing SCSI/SAS. I guess the reason I had to ask is that I hear about the importance of the deletion process when concerning a SSD. I was just trying to get a little bit of solid information about the process that vSAN uses and if it is capable of deleting the data from the SSD(s) once the virtual machine has been deleted. I also wanted to make sure that I wasn't just going to throw away six SSD's to get some experimenting time.

I do appreciate you help.

Yes, this is possible with the vCenter Converter. As for as I know there is no specific requirement in which processor types are supported, it just uses the processor topology (sockets and core) and not the type.

Below are my points to your query:

1) Space reclamation usually happens automatically in VSAN datastore.

2) PERC H200 is a SAS based controller which means the drive which gets attached to it, will work on SAS specification.

3) TRIM has no role to play in your case as It is part of ATA command set. TRIM, (which is a command and not an acronym) is currently available for ATA/SATA interfaces only.

4) The SAS committee has added UNMAP, which is similar to TRIM, to the SAS/SCSI specification.

5) Finally, UNMAP is supported by ESXi. SCSI UNMAP commands were introduced as part of the vStorage APIs for Array Integration (VAAI) in vSphere 5.0 and It's supported in all the later versions.

Hope this answers your query.

_________________________

Was your question answered correctly? If so, please remember to mark your question as answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

Cheers!

-Shivam

I already tried this. No new IPAM server is listed in the 'Value' field of 'IPAMConnection' - it only shows the old IPAM connection to choose.

Doug Arcidino is right. The reason you are getting this error is because your ESXi3 VM is using vmxnet3. You need to change the network adapter type on ESXi3 VM.

Here are the steps you should follow:

1) Go to ESXi2 and power-off ESXi3 VM.

2) Go to Edit Settings on ESXi3 VM.

3) Remove vmnic0 and vmnic1 (Network adapter 1 and Network adapter 2 respectively).

4) Add two new Ethernet adapter with type as e1000e or e1000 (e1000e preferred).

5) Power-On the ESXi3

6) Add newly created vmnics (would be shown as vmnic0 and vmnic1) to vSwitch0 on ESXi3 (vSwithc0 Properties > Network Adapters > Add)

Hope this would help to resolve the issue. Let me know how it goes.

Cheers!

-Shivam

Hello all,

I was hoping someone might be able to offer some guidance regarding a particular limitation we've been facing. As most of you know, the default options within the View Client are: All Monitors, Fullscreen, Window-Large, Window-Small, or Custom (which is limited to the max resolution of one monitor on the client system). Our issue is that we wish to use only two of the monitors on the client system when there are three or four monitors connected in total. Our VDI infrastructure is being used for development within our segregated "test" domains, and they need at least one monitor to be usable for production work (email, IM, RDP to prod servers, etc.). Below are the options we've already tried, which all leave a lot to be desired still. All tests below are done using a Windows 7 client desktop with three 23" monitors. Connected to a Windows 7 VDI running View Agent 7.0.2 and using View Client version 4.2.0.

     1. Setting View Client to open virtual session using "Window-Large" display setting, and then manually stretching the window across two of the three/four monitors on the client system. At best, this is the only solution that actually allows us to use a subset of monitors and the rest still be available for other processes. However, the VDI still sees this as one giant display, meaning all the snap-features and window-resizing within Windows is virtually unusable. Also have to do this every time the session is closed and reopened.

     2. Same as above, but using something like DisplayFusion or Dell Display Manager to artificially split the display. Same problem occurs here, as every time you disconnect the display is reset back to the default "Window-Large" size and wipes all settings for DF or DDM.

     3. Limiting display settings within View Admin to allow a max of two monitors, and using the "All Monitors" display option within the View Client. Even with the pool set to a max of two monitors, selecting the "All Monitors" option within the display options of the View Client causes any monitors past the two monitor limit on the pool to just go completely black. For our usage case, this isn't any better than all monitors being consumed by the VDI.

If anyone has any other solutions they would be greatly appreciated, as this has been a large contingency point for our 600+ developers.

According to the following KB you should remove the host from vcenter and add back in. This mean you want to unprepare the host in NSX. Putting the host in maintenance mode and moving the host outside the cluster will start an uninstall of the NSX vibs via EAM.

Changing the name of an ESX or ESXi host (1010821) | VMware KB

I'm not quite sure whether I understand your question correctly.

Snapshots can be delete with the VM powered on (which will require additional free disk space on the datastore), or with the VM powered off. In case of a powered off VM with a thick provisioned virtual disk, deleting the snapshot will not consule extra disk space, with a thin provisioned virtual disk the free disk space requirements depend on the data in the snapshot file?

If the snapshot deletion is started for a powered off VM, you cannot change the power state until the deletion has finished.

André

Should be able to set this up using Group Policy.

Connecting all USB devices to the VMware Horizon View desktop on launch (2088705) | VMware KB

I too am randomly seeing this issue and do not have the stated registry key.