Hi All,

When you fix an issue and think all is good with the world we get a new issue story of my life.

Anyway so we just updated App Volumes to 2.13.2.13 which was installed to fix an issue with the DB multiple same machine names etc.

So after the upgrade My team and I noticed that UEM started playing up.

We currently using UEM 9.3 and when we log into a Windows 10 1607 built it powers on does svservice (AppVolumes) and gets to “Please wait for the Vmware UEM Service”

And just hangs i can see App Volumes has attached App Stacks and can see the machine i am logging into but in VMware View Agent it says i have not logged in due to waiting on UEM Service.

Any one seen this issue.

Thanks in advanced

Fusion 10 running on new iMac Pro with VM Windows 10 Pro 64 and Solidworks 2017

i have 3D acceleration enabled but I can not disable under Solidworks options,  software OpenGL

on Parallels, there is a registry patch to fix, what should I try with Fusion?

thanks!

How does the auto-suspend feature work in Workstation Pro 14?   As far as I can tell from the documentation, this feature only works for Shared and Remote vm’s. I have a few VM’s whose files are saved on different physical drives in the Windows host and if I’m not mistaken, Shared VM’s must be on the same physical drive. I prefer to have them on different physical drives for better performance. Is there a way to use auto-suspend for non-Shared VM’s?  I see a setting in the bundled Workstation Player that came with Workstation Pro, it says “When closing a virtual machine:” and there’s an option to “Suspend the virtual machine.” But even if that’s the feature I’m looking for, this option wouldn’t work because I need to run multiple VM’s at once which I don’t believe is possible in Player. This feature is described in the documentation at https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-E3CF099C-DE18-44A4-9B81-24BCD72004BE.html

Authors: VMware NSX Technical Product Management Team

This is the NSX-T Reference Design 2.0 based on NSX-T release 2.5. It is the foundational overhaul to design guidance and leading best practices.  The key changes are:

• Platform enhancements
• Enterprise to Service Provider scale routing
• Resilient, Optimized and Simplified Edge Node Functionality
• Native Load Balancer
• Performance
• Design enhancements – Small to Cloud-scale

The design chapter evaluate various deployment form factors and provides best practices. It offers guidance for a variety of factors including physical infrastructure considerations, compute node requirements, and variably-sized environments from small to enterprise scale data centers.

Finally, in this version of design guide we have a chapter on performance. This chapter has been introduced on public demand from our loyal customer base and aims at clarifying the myths vs facts on NSX-T based SDN.

Starting with this design guide, readers are encouraged to send a feedback to NSXDesignFeedback_at_groups_vmware_com  (replace at and underscores)

We will continually updating this document so please re-download this document.

–The VMware NSX Product Management

Hello all….  After updating to the latest 5.5 patches we started seeing some messages repeating at different times (no time pattern) in the vmkernel log on all of our hosts.  The message is:

cpu45:33681)NMP: nmp_ResetDeviceLogThrottling:3311: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x20 0x0 from dev “mpx.vmhba32:C0:T0:L0” occurred 2 times(of 0 commands)

These messages repeat all day every day.  We boot from a supported SD card and the message indicates the USB device is to blame.  I opened a ticket with VMware, they stated that the messages are benign and nothing to worry about and are related to an updated SCSI driver in the patches we applied.  Basically the message is indicating that vmware is sending sense data to the USB controller which it does not understand and is sending back an illegal request.  Their suggestion was to reach out to HP for a firmware update. (we are at the latest FW on all hosts and I have tried backing down the FW to see if that would help) I have done that however I’m in the midst of a pissing match between VMware and HP both blaming each other for the fix so I’m turning to the community for help.

We have a mix of HPE DL380G8 & G9, and a spattering of ML350s at remote offices.  All of the updated servers are logging this message.

While I appreciate that the messages are benign they are causing noise in the logs and I’d like to figure out a way to 1) fix the issue (ideally) or 2) suppress the messages and 3) validate that the messages are indeed benign.

Are others seeing these same messages in their logs?  Given we have seen this on multiple hosts across multiple generations of HPE servers I’m inclined to believe others are seeing this as well?

To add to it, we recently purchased several DL360 Gen10 servers running 6.5.  All of those servers boot from SD card as well and log a similar message:

cpu40:65665)NMP: nmp_resetDeviceLogThrottling:3348 last error status from device “evi.00e04c20202020” repeated 2 times

cpu43:65665_NMP: nmp_ThrottleLogForDevice:3647 Cmd 0x9e (0x439d423a9200, 0) to dev “evi.00e04c20202020” on path “vmhba32″C0:T0:Lo” Failed: H0x7 D0x0 P:0X0

Thanks in advance for any advice on resolving this.