All Posts

Hi, We are trying to implement websockets in our plugin UI and it is giving 502 error. To confirm on the support, we had taken 8.0U1 SDK sample and deployed it on Client 8.0U1 and found that same error is coming for sample plugin as well. Could you please confirm/help on fixing the sample? we were able to establish the socket connection directly without going through the plugin reverse proxied manifest/backend server(htmlClientSdk.app.getPluginBackendInfo) address. I remember the recommendation is to tunnel all interaction through proxied backend server URL . Does establishing socket connection directly to  plugin backend is acceptable or not? Any implication on plugin certification? Error: vSphere Client version 8.0.0.10000 Sample jar Server log: 2023-11-09 02:21:38.135 ERROR 7164 --- [io-8443-exec-17] c.v.s.r.w.WebSocketMessageHandler : Transport error java.io.IOException: Unable to unwrap data, invalid status [CLOSED] at org.apache.tomcat.util.net.SecureNioChannel.read(SecureNioChannel.java:632) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1257) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1230) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1200) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:72) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1468) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_392-392] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_392-392] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.lang.Thread.run(Thread.java:750) [na:1.8.0_392-392] 2023-11-09 02:21:38.135 ERROR 7164 --- [io-8443-exec-17] c.v.s.r.w.WebSocketMessageHandler : Transport error java.io.IOException: java.io.IOException: Unable to wrap data, invalid status [CLOSED] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:592) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:480) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsSession.close(WsSession.java:445) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:236) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:136) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at com.vmware.sample.remote.websocket.WebSocketMessageHandler.handleTransportError(WebSocketMessageHandler.java:66) [classes!/:na] at org.springframework.web.socket.handler.WebSocketHandlerDecorator.handleTransportError(WebSocketHandlerDecorator.java:80) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.handleTransportError(LoggingWebSocketHandlerDecorator.java:64) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.handleTransportError(ExceptionWebSocketHandlerDecorator.java:68) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onError(StandardWebSocketHandlerAdapter.java:156) [spring-websocket-5.0.7.RELEASE.jar!/:5.0.7.RELEASE] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.onError(WsHttpUpgradeHandler.java:216) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) [tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1468) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_392-392] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_392-392] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.31.jar!/:8.5.31] at java.lang.Thread.run(Thread.java:750) [na:1.8.0_392-392] Caused by: java.io.IOException: Unable to wrap data, invalid status [CLOSED] at org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:675) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:101) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:157) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint.java:1276) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBase.java:670) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.flushBlocking(SocketWrapperBase.java:607) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.util.net.SocketWrapperBase.flush(SocketWrapperBase.java:597) ~[tomcat-embed-core-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:96) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:494) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309) ~[tomcat-embed-websocket-8.5.31.jar!/:8.5.31] ... 22 common frames omitted

Hi, everyone. It's me again. Previously I learned that the vmkfstools command can get information about the mapping blocks of virtual disks on physical LUNs, and in recent days when I was using veeam to do backups, I found such a file: *****_mapping.xml, which was deleted after the backups were completed, so I found a chance to download him, which really surprised me, and in the following days, I tried to analyze the structure of the file content, and found that he was the same as the data block area obtained using vmkfstools! It just contains a bit more comprehensive information, I guess there should indeed exist some interface to get the relevant data structure. So I found the following article:API HostDiskManager Endpoint / AcquireLeaseExt - VMware Technology Network VMTN Now I have the same doubt as the author? I would like to discuss how the SOAP request in the article should be called? PS: The documentation appendix on mapping is below, so I won't post it here.

We have an internal monitoring tool for server monitoring. Similarly, we need to integrate vCenter alerts into our monitoring tool. Could you please share how to use the vCenter Alerts API to achieve this ?

I am using VCloud API version 37.1, and I'm trying to send a query to the sessions endpoint in Postman: POST https://my.vcloud.com/cloudapi/1.0.0/sessions/provider In the Header, I have Authorization="Bearer <token>" But the POST fails with the following: {     "minorErrorCode": "VCD_50086",     "message": "Invalid authorization header",     "stackTrace": null }   Not sure what I'm doing wrong. Any help is appreciated.

I am following below document to get primary IPAddress for Virtual Machines, as per the document I am expecting the primary IPAddress of the Virtual Machine,  but unexpectedly it is giving the Secondary IPAddress( Internal IPAddress ) https://vdc-download.vmware.com/vmwb-repository/dcr-public/b50dcbbf-051d-4204-a3e7-e1b618c1e384/538cf2ec-b34f-4bae-a332-3820ef9e7773/vim.vm.GuestInfo.html Note: I am using VI SDK to collect Host and VMs guest tools information, Here i am facing issues for virtual machines which have windows server operating system. Can some one please help me on how to identify the primary IPAddress of VM in this case.

Please see the call stack below due to which user process hangs. vixdisklib 6.7.1.35969 (file version) build 10362358 (product version) # Child-SP RetAddr Call Site 00 0000000f`d31fe068 00007ffe`c882d831 win32u!NtUserWaitMessage+0x14 01 0000000f`d31fe070 00007ffe`c882d5a1 user32!DialogBox2+0x261 02 0000000f`d31fe110 00007ffe`c887d22b user32!InternalDialogBox+0x12d 03 0000000f`d31fe170 00007ffe`c887bb45 user32!SoftModalMessageBox+0x85b 04 0000000f`d31fe2c0 00007ffe`c887c937 user32!MessageBoxWorker+0x341 05 0000000f`d31fe470 00007ffe`c887c9be user32!MessageBoxTimeoutW+0x1a7 06 0000000f`d31fe570 00007ffe`b1464e88 user32!MessageBoxW+0x4e 07 0000000f`d31fe5b0 00007ffe`b15020af vixDiskLib!VixDiskLib_FreeErrorText+0x4808 08 0000000f`d31fe5e0 00007ffe`b15032b1 vixDiskLib!VixDiskLib_FreeErrorText+0xa1a2f 09 0000000f`d31fe610 00007ffe`b15035e7 vixDiskLib!VixDiskLib_FreeErrorText+0xa2c31 0a 0000000f`d31fe6f0 00007ffe`b15fd49a vixDiskLib!VixDiskLib_FreeErrorText+0xa2f67 0b 0000000f`d31fe730 00007ffe`b15eafed vixDiskLib!VixDiskLib_FreeErrorText+0x19ce1a 0c 0000000f`d31feb90 00007ffe`b15053d2 vixDiskLib!VixDiskLib_FreeErrorText+0x18a96d 0d 0000000f`d31fefc0 00007ffe`b1482381 vixDiskLib!VixDiskLib_FreeErrorText+0xa4d52 0e 0000000f`d31feff0 00007ffe`b1482a3c vixDiskLib!VixDiskLib_FreeErrorText+0x21d01 0f 0000000f`d31ff050 00007ffe`b1451430 vixDiskLib!VixDiskLib_FreeErrorText+0x223bc 10 0000000f`d31ff0e0 00007ff7`80c0dc40 vixDiskLib!VixDiskLib_Write+0x140 11 0000000f`d31ff130 00007ff7`80c0b088 OUR-private-module!OUR-private-function+0x1a0 vixDiskLib!VixDiskLib_Write function is called with a valid handle, valid buffer, offset and length of 1 sector of 4096. Disk it was trying to write is 503 GB. ( a integer sized disk). @VMware, please help. please share the insight. Thanks.

Hi zusammen, wie verhält sich eine Win11 VM mit vTPM, wenn der ESXi zur Installation der VM Teil eines vCenter Clusters war und dann als Standalone Host, ohne vC Integration, in einem anderen Netz weiterläuft? Die VM startet. Aber wo ist jetzt der Haken, bzw. was sind jetzt die Risiken oder Folgen für den Betrieb der Win11 VM? Zum Hintergrund: Manche Kunden betrieben einen einzelnen ESXi (lizenziert) ohne vCenter (sämtliche Kommentare dazu jetzt bitte verkneifen  ) Für die Installation einer Win11 VM wird so ein Host per VPN temporär an den Systemhaus vC angebunden und erhält darüber seinen vTPM Key. Das sind aktuell nur Tests, noch nichts Produktives. Die Frage bleibt, ob so ein Kunde um einen eigenen vC zukünftig nicht drum herum kommt, oder ob o.g. Lösung ohne gravierende Fallstricke angewendet werden könnte. Besten Dank! VG C

Hi everybody !   We want to custum VMs depoyement using perl script file: i follow this documentation: https://kb.vmware.com/s/article/2007557 ( and so on) have to install XLM::MOD::Path and all the dependency. i can't go any further, i am stuck to the XML:Parse module installation.   here is the message error : Running make test : .................... ................................... # Failed test at t/decl.t line 86. # got: '((bar|foo|xyz+),bar)' # expected: '((bar|foo|xyz+),zebra*)' # Failed test at t/decl.t line 95. # got: 'bar' # expected: 'zebra' # Failed test at t/decl.t line 96. # got: undef # expected: '*' # Looks like you failed 3 tests of 40. .......................... .................................... make: *** [Makefile:971: test_dynamic] Error 255 TODDR/XML-Parser-2.46.tar.gz make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports TODDR/XML-Parser-2.46.tar.gz Thanks in advance   best regards

Hello, we have two connected VCenters and did an Update to 7.0.3-22357613 some das ago. Update proceeded succesful, like we did some times before. 1-2 hours after update we had some powershell tasks running which creates machines and start them in specific cluster. We use typical powercli module. This time VCenter responds to powershell that there are no active hosts in cluster and task failed. The error was also shown in VCenter Webclient in task window at the bottom. In VCenter Webclient all was looking ok as is usual. All CLusters/Hosts active and no specific warnings or errors. VCenter Health in Managementconsole is good. After some hours we tried again and this time the process was successful and never happend again.  Even if the error is vanished quickly so i think this is still remarkable notice. It should never happen that VCenter respondes different/wrong to different requests. Someone experienced in this topic? please share your opinion.   Thanks, Hajo

Hallo zusammen, ich habe eine neue Vorlage mit Win ltsc 2021 und ein neues Anpassungsskript dafür erstellt. Allerdings scheint das Skript nicht zu starten. Weder nach dem Erstellen der VM, noch wenn man es manuell ausführt. Die Datei C:\Windows\Panther\UnattendGC\setupact.txt ist die einzige Logdatei, die ich finden konnte, aber sie scheint ziemlich leer zu sein. Hat jemand eine Idee, warum die Anpassungen nicht ausgeführt werden? Der Name ist kürzer als 15 Zeichen und die Anpassungsspezifikation wurde neu erstellt.     2023-10-24 11:22:28, Info [svchost.exe] Enter WinReIsWimBootEnabled 2023-10-24 11:22:28, Info [svchost.exe] Parameters: pszWinDir: NULL 2023-10-24 11:22:28, Info [svchost.exe] Exit WinReIsWimBootEnabled returns 0 with last error: 0x0 2023-10-24 11:37:05, Info [taskhostw.exe] Enter WinReValidateRecoveryWim 2023-10-24 11:37:05, Info [taskhostw.exe] Update enhanced config info is enabled. 2023-10-24 11:37:05, Info [taskhostw.exe] WinRE is installed 2023-10-24 11:37:06, Info [taskhostw.exe] Loading boot index 1 2023-10-24 11:37:06, Info [taskhostw.exe] winreValidateWimFile took 281 ms. 2023-10-24 11:37:11, Info [taskhostw.exe] WinReValidateRecoveryWimInternal took 5734 ms. 2023-10-24 11:37:11, Info [taskhostw.exe] Exit WinReValidateRecoveryWim return value: 1, last error: 0x0 2023-10-24 11:37:11, Info [taskhostw.exe] Enter WinReConfigureTask 2023-10-24 11:37:11, Info [taskhostw.exe] Parameters: TaskFolder: \Microsoft\Windows\RecoveryEnvironment, TaskName: VerifyWinRE, WinReTaskAction, 1 2023-10-24 11:37:11, Info [taskhostw.exe] Exit WinReConfigureTask return error code: 0x0 2023-10-24 11:57:38, Info [svchost.exe] Enter WinReIsWimBootEnabled 2023-10-24 11:57:38, Info [svchost.exe] Parameters: pszWinDir: NULL 2023-10-24 11:57:38, Info [svchost.exe] Exit WinReIsWimBootEnabled returns 0 with last error: 0x0      

I found an example in the vsan-sdk examples that shows how to query the storage pool disks, but I get this error: disks = [disk for storagePool in storagePoolDisks.GetStoragePools() for disk AttributeError: 'vim.vsan.host.VsanManagedDisksInfo' object has no attribute 'GetStoragePools' Sample Code from vsanesastoragepoolsamples.py (from vsan-sdk) [code] def queryStoragePoolDisks(vdms, host):     spec = vim.vsan.host.QueryVsanDisksSpec()     spec.vsanDiskType = vim.vsan.host.VsanDiskType("storagePool")     storagePoolDisks = vdms.QueryVsanManagedDisks(host, spec)     disks = [disk for storagePool in storagePoolDisks.GetStoragePools() for disk                  in storagePool.storagePoolDisks]     return disks [/code]