Sharing esata disk (Windows LAN)

This post was originally published on this site

I currently use Windows 10 running several VMs in Workstation, CPU is i7-3930K, i.e. no VT-d. It also has 24TB Raid5 external array (Areca), connected to the PC via esata, and shared as r/w folder in Windows, so that other PCs can use it as file server. I read that switching to Esxi allows better memory management and therefore – better performance for VMs. I have following questions:

1. Will performance difference be noticeable, especially if I increase number of VMs to 10+?
2. Will it be possible to share the esata disk in one of the VMs, or by means of the Esxi, so that it is visible to other Windows machines as shared folder?

3. Since the PC is pretty old (SaberTooth X79), should I use older versions of Esxi for drivers compatibility, or 7.0 will work just fine?



Horizon VMWare client on Ubuntu 20.04 not working

This post was originally published on this site



My organization recently migrated our HVD clients from citrix to horizon vmware. I have a ubuntu linux based PC at home that i use to normally access my HVD. Citrix access was working very stable. With horizon, I am not able to successfully use my HVD. I have “VMware-Horizon-Client-2006-8.0.0-16522670.x64.bundle” installed on my ubuntu 20.04 distribution. after initial install, the scan function showed 3 libraries missing. on googling around, I found this was a common issue and i ran the suggested “ln” commands to link the libraries being looked for with those that were available. that error went away after that.


Once all installed, I tried to access my HVD. Here is the behavior i see  – when i log in, the horizon client does take over my screen for about 1 second and it looks like the HVD will become available, but then that window vanishes and i land back on the “VMware Horizon Client” window with my HVD showing as an icon in that window. if I click on the HVD icon to stat it, the same behavior is now repeated.


I have attached log files if anyone wants to go over them in details. here is what I see in the VMWare Horizon Client log:

2020-08-31 19:10:58.944-04:00: vmware-view 4484| cdk_pcoip_desktop_on_connection_state_changed: RemoteMKS connection failed.


Here is what i see in the VMWare crtbora.log:

2020-08-31T19:10:57.337-04:00| crtbora| I006: CUIMKS: cui::MKS::OnConnectedChanged (55AD28011430)

2020-08-31T19:10:57.337-04:00| crtbora| I005: SetConnectionState: MKS connection state changes from -1 to 2.

2020-08-31T19:10:57.337-04:00| crtbora| I005: OnConnectionStateChanged:2295: Entry

2020-08-31T19:10:57.337-04:00| crtbora| I005: GetConnectionStateReason(): remote mks did not set a disconnect reason code, so assuming it crashed.

2020-08-31T19:10:57.337-04:00| crtbora| I005: OnConnectionStateChanged:2335: Exit


Any help will be appreciated, thanks for looking.

Upgrading from Mac OS Mojave to Catalina and VM 10.1.5 to 11.5.6 — W7 VM Not Responding to Keystrokes or Mouse Clicks

This post was originally published on this site

I moved to a new MacBook Pro and in the process upgraded from Mojave to the Catalina OS.  I initialized the new machine from my Time Machine backup.


When I tried VMWare (10.1.5) on the new machine, I ended up with a black screen when I tried to access my Windows 7 VM.  Then VMware became unresponsive and said that components were unavailable — I gather it wasn’t compatible with OS Catalina.


So I downloaded the latest VM Fusion 11.5.6 (which I’ll be happy to purchase outright or via an upgrade).  I can now see my W7 desktop and applications open (for instance, a Skype upgrade began automatically).  But I can’t seem to use my mouse or keyboard in this environment.  (However, my keyboard does work when typing in my W7 password at the logon screen).


Any thoughts?





P.S. In Fusion 10.1.5, there is a small control element at the bottom of the screen that is used to map USB devices and networking settings — I’m curious how that functionality is exposed in 11.5.6.

NIC Teaming – IP Hash – Network link drops

This post was originally published on this site


I’m trying to setup some new ESX hosts with IP Hash NIC teaming. They are HP ProLiant DL360 Gen10 servers.

The hosts have 2-port 10Gb fiber NICs in them. The NIC is connected to the same physical switch (Cisco).


I have been trying to follow the documentation for IP Hash setup and it says it requires port-channeling on the switch, which makes sense.

But every time we enable the port channeling, the management network link to the host completely drops out (no link lights on NIC) with no communication working to the server, except for ILO. When we turn off the port-channeling, the network link comes right back up.


If port-channeling is required to make IP hash work then does anyone know why the network link keeps dropping?

Are there special commands needed to make this work on the switch side?


Thanks in advance for any thoughts.

UDP Packets dropping from host to VM

This post was originally published on this site

My setup:


Workstation Pro 15.5



CPUs: 16 cores, 32 threads

RAM: 128 GB

OS: Cent OS 7.6.1810

5 NICs – 2×40 Gbps, 2x10Gbps, 1x10Gbps



CPUs: 16 threads

RAM: 64 GB

OS: Red Hat Enterprise 7.8

2 VNICs – 2×10 Gbps


I’m trying to transfer UDP packets from Host to VM using iperf command at 850 Mbps bandwidth. In the attached screen shots. I am dropping about 2-3% of my packets. I have MTU=9000 in all the ifcfg files for all the VNICs and NICs.


What configurations do I need to change to stop packet loss between Host and VM?

OS/X lost all accounts with installation of Big Sur

This post was originally published on this site

I (accidentally) installed Big Sur over a Mojave installation and seem to have lost all the accounts on the machine. I didn’t have the latest version of Workspace One. When Big Sur boots I am presented with a login screen that asks for the “Setup User”. Using my domain user id doesn’t satisfy it and even my local IT folks can’t get in using the administrator accounts that they set up on the machine originally.

What is the best practice for snapshots when updating vCenter servers in Linked mode?

This post was originally published on this site

We have five vCenter servers in linked mode running vCenter 6.7 U3g.  I’m preparing to update next week to vCenter 6.7 U3j. 


Is it best practice to shut down all five vCenter servers at once, then take snapshots of all five vCenter servers?  Or, is it ok to shut down one vCenter, take the snapshot, power up and update that vCenter server, then go on to the next?  I wasn’t sure if due to replication, it would be best to snapshot them all at about the same time, in case all five vCenter servers would need to be rolled back due to issues.

vVols: Cannot importVApp from java to deploy ovf template on vCenter on vVols datastore

This post was originally published on this site

Hi all,


I’m trying to use vVols datastore to deploy OVF template from a java application. I could do deployOvfTemplate from vCenter but when I’m doing it from java the operations is failed with error “vim.fault.CannotCreateFile Please see the server log to find more detail regarding exact cause of the failure”.


ManagedObjectReference morLease = context.getService().importVApp(morRp, ovfImportResult.getImportSpec(), dcMo.getVmFolder(), morHost);



I digged a little more on all possible logs and find the following relavant errors. But I could not find the exact issue and fix to make.

I believe importVApp method from management SDK is datastore type independant.


Can any one help me in this regard,




2020-08-05T09:53:37.187Z info hostd[2098595] [Originator@6876 sub=Default opID=78ac9244-01-01-01-29-9112 user=vpxuser:VSPHERE.LOCALAdministrator] AdapterServer caught exception: N7Hostsvc20OsfsCannotCreateFile9ExceptionE(Fault cause: vim.fault.CannotCreateFile





2020-08-05T09:53:36.268Z info vvold[2283420] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols called                                                                                      

2020-08-05T09:53:36.268Z info vvold[2283420] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols done for 0 VVols

2020-08-05T09:53:37.173Z info vvold[2283394] [Originator@6876 sub=Default] Came to SI::BindVirtualVolume: esxContainerId bac3b586-36dc-498d-ac49-7147bfd7f4c9 VVol Id 17a12f9e6eb0329b83e754762976599c bindType

2020-08-05T09:53:37.173Z info vvold[2283394] [Originator@6876 sub=Default]                                     

–> VasaOp::BindVirtualVolume [#132249]: ===> Issuing ‘bindVirtualVolume’ to VP SolidFire (#outstanding 0/10) [session state: Connected]

2020-08-05T09:53:37.181Z error vvold[2283394] [Originator@6876 sub=Default]                                    

–> VasaOp::ThrowFromSessionError [#132249]: ===> FINAL SUCCESS bindVirtualVolume VP (SolidFire) Container (bac3b586-36dc-498d-ac49-7147bfd7f4c9) timeElapsed=8 msecs (#outstanding 0)

2020-08-05T09:53:37.182Z error vvold[2283394] [Originator@6876 sub=Default] SI:BindVirtualVolume@3536 VASA bind for VVol (17a12f9e6eb0329b83e754762976599c) returned error : INVALID_ARGUMENT ()

2020-08-05T09:53:37.184Z info vvold[2283404] [Originator@6876 sub=IpcSvc] VVoldIpcConn object freed (0)                          





2020-08-05T09:53:37.170Z 5792189:Lookup:660: Got lookup request for “17a12f9e6eb0329b83e754762976599c”

2020-08-05T09:53:37.170Z 5792189:Provider_Lookup:469: Found matching driver for ID [    vvol]       

2020-08-05T09:53:37.170Z 5792189:VVolMount:2464: VVolMount@2464:Lookup was sent UUID based name 17a12f9e6eb0329b83e754762976599c

2020-08-05T09:53:37.171Z 5792189:5792189:VVOLLIB : VVolLib_Open:8955: container Id passed: bac3b586-36dc-498d-ac49-7147bfd7f4c9 Normalized: bac3b586-36dc-498d-ac49-7147bfd7f4c9

2020-08-05T09:53:37.171Z 5792189:5792189:VVOLLIB : VVolLib_Open:8995: created devFS node ’17a12f9e6eb0329b83e754762976599c’ (objType 3)

2020-08-05T09:53:37.182Z 5792189:5792189:VVOLLIB : VVolLib_IpcStorageFaultToVVolLibError:767: Storage Fault INVALID_ARGUMENT (9):

2020-08-05T09:53:37.182Z 5792189:5792189:VVOLLIB : VVolLib_BindVVol:4145: failed with error (1) Bad Parameter for Config VVol 17a12f9e6eb0329b83e754762976599c

2020-08-05T09:53:37.182Z 5792189:5792189:VVOLLIB : VVolLib_Open:9241: Could not bind VVol 17a12f9e6eb0329b83e754762976599c failed with error (Bad Parameter)                             

2020-08-05T09:53:37.183Z 5792189:VVolMount:2526: VVolMount@2526:Could not open the VVol ’17a12f9e6eb0329b83e754762976599c’ (No such file or directory)




2020-08-05T09:53:37.203Z info vpxa[5691664] [Originator@6876 sub=Default opID=78ac9244-01-01-01-29] [VpxLRO] — ERROR lro-7007 — vpxa — vpxapi.VpxaService.reserveName: vim.fault.CannotCreateFile:        

–> Result:                                                                                                                                                                                                  

–> (vim.fault.CannotCreateFile) {                                                                                                                                                                           

–>    faultCause = (vmodl.MethodFault) null,                                                                                                                                                                

–>    faultMessage = (vmodl.LocalizableMessage) [                                                                                                                                                           

–>       (vmodl.LocalizableMessage) {                                                                                                                                                                       

–>          key = “com.vmware.esx.hostctl.default”,                                                                                                                                                         

–>          arg = (vmodl.KeyAnyValue) [                                                                                                                                                                     

–>             (vmodl.KeyAnyValue) {                                                                                                                                                                        

–>                key = “reason”,                                                                                                                                                                           

–>                value = “17a12f9e6eb0329b83e754762976599c (Cannot Create File)”                                                                                                                           

–>             }                                                                                                                                                                                            

–>          ],                                                                                                                                                                                              

–>          message = “Operation failed, diagnostics report: 17a12f9e6eb0329b83e754762976599c (Cannot Create File)”                                                                                         

–>       }                                                                                                                                                                                                  

–>    ],                                                                                                                                                                                                    

–>    file = “17a12f9e6eb0329b83e754762976599c (Cannot Create File)”                                                                                                                                        

–>    msg = “Received SOAP response fault from [<cs p:0000007718306350, TCP:localhost:8307>]: CreateDirectory                                                                                               

–> Cannot complete file creation operation.”                                                                                                                                                                

–> }                                                                                                                                                                                                        

–> Args:                                                                                                                                                                                                    


–> Arg spec:                                                                                                                                                                                                

–> (vpxapi.VmLayoutSpec) {                                                                                                                                                                                  

–>    vmLocation = (vpxapi.VmLayoutSpec.Location) null,                                                                                                                                                     

–>    multipleConfigs = <unset>,                                                                                                                                                                            

–>    basename = “17a12f9e6eb0329b83e754762976599c”,                                                                                                                                                        

–>    baseStorageProfile = “<ns1:storageProfile xmlns:ns1=”” xmlns:xsi=”” xsi:type=”ns1:StorageProfile”><ns1:const

–>    disk = (vpxapi.VmLayoutSpec.Location) [                                                                                                                                                               

–>       (vpxapi.VmLayoutSpec.Location) {                                                                                                                                                                   

–>          url = “ds:///vmfs/volumes/vvol:bac3b58636dc498d-ac497147bfd7f4c9/”,                                                                                                                             

–>          key = <unset>,                                                                                                                                                                                  

–>          sourceUrl = “ds:///vmfs/volumes/vvol:bac3b58636dc498d-ac497147bfd7f4c9/”,                                                                                                                       

–>          urlType = “rootDirPath”,                                                                                                                                                                        

–>          storageProfile = “<ns1:storageProfile xmlns:ns1=”” xmlns:xsi=”” xsi:type=”ns1:StorageProfile”><ns1:con

–>       }                                                                                                                                                                                                  

–>    ],                                                                                                                                                                                                    

–>    reserveDirOnly = true                                                                                                                                                                                 

–> }       

after vmconverastion when starting vm I get can not find command

This post was originally published on this site

I have one vm(xen) converted to ESXi and this one completes 100 percent but when starting up the VM it gives the error can not find command


It is freebx distro and I believe it not the same issue as redhat that is posted


AnywayBase on that solution it’s changing the grub and I would not know how to change the grub with a shutdown Linux on esxi


Please assist thanks