Tag Archives: Virtualization

“Upgrading” to VMware Fusion 11.5.6 BREAKS virtual machines that worked with 11.5.5

This post was originally published on this site

Something very like this appears from prior discussions to have been a problem for multiple people under circumstances that I could not identify.

 

I am using macOS 10.14.6 on a late 2015 27-inch iMac Retina 5K  – –  also known as iMac17,1.

 

I have four virtual machines:  Windows 8.1, Windows 10, macOS 10.13, and macOS 10.14.

 

All were working with Fusion 11.5.5, all are identically broken now that I have “upgraded” to 11.5.6.

 

When I try to start the virtual machine the following error dialogs are displayed:

 

1.  Could not open /dev/vmmon:  Broken pipe. (In a free-standing box on the same external monitor as the virtual machine library window.)

 

2.  Failed to initialize monitor device.  (In a drop-down box from the title-bar of the virtual machine’s window on the iMac itself.)

 

3.  Transport (VMDB) error -14: Pipe connection has been broken.  (In a drop-down box from the title-bar of the virtual machine’s window on the iMac itself.)

 

The TeamIdentifier hack discussed in the other thread did not make a difference.

 

Re-installing from a freshly downloaded copy of the installer .dmg did not make a difference.  It did NOT require me to re-enter the license key, so obviously it did not start by removing everything.  It gave me no choices about what to install or where.

Error downloading plug-in. Make sure that the URL is reachable and the registered thumbprint is correct.

This post was originally published on this site

hi all,

 

Am getting this error in vCenter, running vCenter 7.0. Under Administration> Client Plugins its the ‘com.vmware.vrUi’ causing this issue, which seems to be for vSphere replication, which was once deployed but is now gone.

 

Also under: https://vcenter.internal.kloudit.com.au/mob/?moid=ExtensionManager , I have the following:

 

extensionList[“com.vmware.vim.sms”] Extension
extensionList[“com.vmware.vim.vsm”] Extension
extensionList[“VirtualCenter”] Extension
extensionList[“com.vmware.vim.stats.report”] Extension
extensionList[“com.vmware.vim.sps”] Extension
extensionList[“com.vmware.vim.vcha”] Extension
extensionList[“hostdiag”] Extension
extensionList[“com.vmware.vim.ls”] Extension
extensionList[“com.vmware.vsan.dp”] Extension
extensionList[“com.vmware.vcIntegrity”] Extension
extensionList[“com.vmware.vim.eam”] Extension
extensionList[“com.vmware.vsphere.client.h5vsan”] Extension
extensionList[“com.vmware.vrops.install”] Extension
extensionList[“com.vmware.vcenter.wcp”] Extension
extensionList[“com.vmware.vmcam”] Extension
extensionList[“com.vmware.lcm.client”] Extension
extensionList[“com.vmware.vcenter.iso”] Extension
extensionList[“com.vmware.vcenter.vmtx”] Extension
extensionList[“com.vmware.ovf”] Extension
extensionList[“com.vmware.vsphere.client”] Extension
extensionList[“com.vmware.vsan.health”] Extension
extensionList[“com.vmware.rbd”] Extension
extensionList[“com.vmware.registry”] Extension
extensionList[“com.vmware.cl”] Extension

 

Any ideas on how to resolve this?

Horizon client with touch screen input

This post was originally published on this site

Hello,

 

Our customer is using HP ThinClients with ThinPro7 and resistive touch screen displays, that setup proved it reliability our customer factory.

 

They have 3 remote apps and their employees need to change between than thought the day, the problem is that they need to double click the remote app to open it and employees are saying that its is difficult.

 

O couldn’t find any way to increase the delay to recognize a double-click in this OS, so my question is, there is a way to change the behavior of Horizon Client to open the remote app with a single click ?

 

Another question is, there is any way to increase the menu bar size? (without changing the OS resolution).

 

Any idea it’s welcome, I out of ideas…

NSX-T 3.0 to 3.0.1 upgrade fails on ESXi 7.0 host VIB upgrades due to “Failed to load module nsxt-vsip”

This post was originally published on this site

Problem: Cannot upgrade ESXi 7.0 hosts from NSX-T 3.0.0 VIBs to 3.0.1 VIBs.

 

Scenario: vCenter 7.0, ESXi 7.0, NSX-T 3.0.0, ESXi hosts are running N-VDS exclusively (2 pNIC, upgraded from NSX-T 2.5).

 

NSX-T Edge upgrade from 3.0.0 to 3.0.1 was successful, but none of the ESXi hosts in the 4-node cluster are able to have their VIBs upgraded from 3.0.0 to 3.0.1.  Error message in NSX-T Manager is:

 

Install of offline bundle failed on host 09e41e11-6ce5-4fd8-a4ad-3295f927e540 with error : [LiveInstallationError] Error in running [‘/etc/init.d/nsx-datapath-dl’, ‘start’, ‘upgrade’]: Return code: 1 Output: start upgrade begin Exception: Traceback (most recent call last): File “/etc/init.d/nsx-datapath-dl”, line 963, in <module> DualLoadUpgrade() File “/etc/init.d/nsx-datapath-dl”, line 835, in DualLoadUpgrade LoadKernelModules() File “/etc/init.d/nsx-datapath-dl”, line 180, in LoadKernelModules nsxesxutils.loadModule(modName, modParam) File “/usr/lib/vmware/nsx-esx-datapath/lib/python3.5/nsxesxutils.py”, line 360, in loadModule (moduleName, out.decode())) Exception: Failed to load module nsxt-vsip-16404614: vmkmod: VMKModLoad: VMKernel_LoadKernelModule(nsxt-vsip-16404614): Failure Cannot load module nsxt-vsip-16404614: Failure vmkmod: VMKModLoad: VMKernel_LoadKernelModule(nsxt-vsip-16404614): Failure Cannot load module nsxt-vsip-16404614: Failure It is not safe to continue. Please reboot the host immediately to discard the unfinished update. Please refer to the log file for more details..

 

Error in esxupdate.log:

 

[LiveInstallationError]

Error in running [‘/etc/init.d/nsx-datapath-dl’, ‘start’, ‘upgrade’]:

Return code: 1

Output: start upgrade begin

Exception:

Traceback (most recent call last):

   File “/etc/init.d/nsx-datapath-dl”, line 963, in <module>

     DualLoadUpgrade()

   File “/etc/init.d/nsx-datapath-dl”, line 835, in DualLoadUpgrade

     LoadKernelModules()

   File “/etc/init.d/nsx-datapath-dl”, line 180, in LoadKernelModules

     nsxesxutils.loadModule(modName, modParam)

   File “/usr/lib/vmware/nsx-esx-datapath/lib/python3.5/nsxesxutils.py”, line 360, in loadModule

     (moduleName, out.decode()))

Exception: Failed to load module nsxt-vsip-16404614: vmkmod: VMKModLoad: VMKernel_LoadKernelModule(nsxt-vsip-16404614): Failure

Cannot load module nsxt-vsip-16404614: Failure

vmkmod: VMKModLoad: VMKernel_LoadKernelModule(nsxt-vsip-16404614): Failure

Cannot load module nsxt-vsip-16404614: Failure

 

It is not safe to continue. Please reboot the host immediately to discard the unfinished update.

Please refer to the log file for more details.

 

Installing the VIBs manually via Lifecycle Manager (KB 78682) fails with exact same error as above in esxupdate.log.  Installing VIBs via CLI (KB 78679) results in same error.  I verified the boot banks (KB 74864) and they have plenty of free space (95% free space).  ESXi install was fresh install of ESXi 7.0 on 128 GB boot from SAN LUN (SSD).

 

I never had any problems with NSX-T VIB upgrades from 2.4.x to 2.5.x to 3.0.0, so I’m curious why the 3.0.0 -> 3.0.1 upgrade is so challenging.  Has anyone else run into this?

 

Thanks,

Bill

Windows Server 2016 August Cumulative Update Instability

This post was originally published on this site

This morning I installed KB4571694 on my host machine running Windows Server 2016 on an AMD 3950X CPU and x570 chipset.  I also installed it on a virtual machine that I use heavily.  After rebooting the host, all of virtual machines started crashing.  They would try to reboot and fail to start or crash shortly after.  I rolled back the update on the host and everything stablized including the virtual machines that were running the update.

 

Just sharing in case it isn’t just me.

 

I’m running VMWare 15.5.1 and thinking of updating to the current version before trying again.  Also, I am not using “server hardware” so I’m accepting the risks for that.  I have my reasons and its worked out very well for me so far.

API for deleting a device?

This post was originally published on this site

Trying to figure out how to formulate an API call to delete a device from our system.

 

So I know things like the below to query the device: 

 

/API/mdm/devices/{{deviceid}}/commands?command=DeviceQuery

 

But if I wanted to delete a specific device thru API how would I do that?  If possible, thinking thru a Unix shell script as would be running it thru a Mac.  Basically trying to wipe and reset a device between use and find that usually when i delete the existing record before recreating it things flow better where if I don’t sometimes apps don’t reinstall and show red x and stuff.