dariusd wrote:
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
That error message is spurious and can be ignored.
Things like this are rather irksome as it has existed for the last several versions of vmware-vdiskmanager in VMware Fusion/Workstation and VMware VDDK. While you say it's "spurious" nonetheless I'm sure many Uses find it disconcerting to see any error message especially when having used a properly formatted command line with vmware-vdiskmanager. Why has VMware allow this to continue!? Additionally, have not posted a KB Article in reference to this or provided information to create the missing config file, even if a null file, so as to avoid having to see this disconcerting "spurious" message?