wbierman's Posts

Converting to OVF is a requirement of our customer deliverable.  We could add some post-processing to the OVF once it is created.  Is there any OVF setting that would allow separation of physical and... See more...
Converting to OVF is a requirement of our customer deliverable.  We could add some post-processing to the OVF once it is created.  Is there any OVF setting that would allow separation of physical and virtual CPUs?
I am required to export a VM from a .vmx file to an OVF/OVA file for distribution to our customer.  The VM is configured with two sockets and two cores per CPU, for a total of four logical cores (2x2... See more...
I am required to export a VM from a .vmx file to an OVF/OVA file for distribution to our customer.  The VM is configured with two sockets and two cores per CPU, for a total of four logical cores (2x2).  When the customer then re-imports from an OVA to a VMX, the configuration changes to four sockets with one core per CPU (4x1).  The guest OS is Windows 10 x86_64 Pro, which does not support four sockets. How can I ensure that the two socket, two core setting survives the translation to and from OVF?
Second follow-up: I found the installer we used for the previous version, called `VMware-workstation-full-15.1.0-13591040.exe`.  I uninstalled 15.5, disabling the options to remove license and... See more...
Second follow-up: I found the installer we used for the previous version, called `VMware-workstation-full-15.1.0-13591040.exe`.  I uninstalled 15.5, disabling the options to remove license and configuration information, and then re-installed using the old installer.  The VIX API is now working again.
Follow-up: I installed a trial of VMWare Workstation Pro 15.5 on a clean Windows 10 Professional machine (i.e. never had any vmware products installed).  The same exact problem happens there.
We have a similar problem, where VIX stopped working altogether after installing the 15.5 update.  15.0.0 is referenced in our vixwrapper-product-config file too and this is an excerpt from the l... See more...
We have a similar problem, where VIX stopped working altogether after installing the 15.5 update.  15.0.0 is referenced in our vixwrapper-product-config file too and this is an excerpt from the log file in %TEMP%: 2019-10-04T03:21:39.450-04:00| host-7824| I125: Log for VixWrapper pid=7820 version=1 build=build-14665864 option=Release 2019-10-04T03:21:39.450-04:00| host-7824| I125: The process is 64-bit. 2019-10-04T03:21:39.450-04:00| host-7824| I125: Host codepage=windows-1252 encoding=windows-1252 2019-10-04T03:21:39.450-04:00| host-7824| I125: Host is Windows Server 2012 Standard Edition, 64-bit  (Build 9200) 2019-10-04T03:21:39.434-04:00| host-7824| I125: DictionaryLoad: Cannot open file "C:\Users\bbierman\AppData\Roaming\VMware\config.ini": The system cannot find the file specified. 2019-10-04T03:21:39.434-04:00| host-7824| I125: [msg.dictionary.load.openFailed] Cannot open file "C:\Users\bbierman\AppData\Roaming\VMware\config.ini": The system cannot find the file specified. 2019-10-04T03:21:39.434-04:00| host-7824| I125: PREF Optional preferences file not found at C:\Users\bbierman\AppData\Roaming\VMware\config.ini. Using default values. 2019-10-04T03:21:39.434-04:00| host-7824| I125: FILE: FileLockDynaLink: Further process validation tools are: available 2019-10-04T03:21:39.448-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Users\bbierman\AppData\Local\Temp\2\vmware-bbierman", ...) failed, error: 2 2019-10-04T03:21:39.451-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("vixWrapperDiscovery.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.459-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.460-04:00| host-7824| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Program Files (x86)\VMware\VMware VIX\\Workstation-15.0.0\64bit\vmwarebase.dll", ...) failed, error: 2 2019-10-04T03:21:39.460-04:00| host-7824| I125: passed in VIX_SERVICEPROVIDER_DEFAULT, computed hostType as 3 2019-10-04T03:21:39.460-04:00| host-7824| I125: Workstation installed version is 15.5.0 2019-10-04T03:21:39.460-04:00| host-7824| I125: No implementation found for service provider 3, apiVersion -1 installedVersion 15.5.0 2019-10-04T03:21:39.460-04:00| host-7824| I125: No Vix library found for provider 1 revision -1, err 22002