Raise InstallParameterException('Install-parameter %s not set' % param)Ĭis.exceptions. Os.path.join(get_install_parameter(''), "vlcm")įile "/usr/lib/vmware/site-packages/cis/tools.py", line 88, in get_install_parameter # cat /var/log/firstboot/vlcm_firstboot.py_9117_stderr.logįile "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 167, in įile "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 129, in mainįb = VlcmFirstboot(VLCM_COMP, VLCM_SOLUSERNAME)įile "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 50, in _init_ Taking a look at the log file, he noticed the error was regarding the OVF property not being set, which seems to be causing the issue. I was made aware of this issue from a colleague who was looking to setup a vSphere 8 environment using VMware Workstation. Hi there, problem: Cannot find a valid peer process to connect to Mac system 10.14.4 Fusion 10.1.6 I already set my mac as follower: However, it didnt work, the problem is still there. With vSphere 8, it looks like there has been a change to the VCSA installer that causes a failure during the Stage 2 configuration. In 2017, the Fusion/Workstation team introduced native OVF support and that made deploying the VCSA much simpler, especially with the VCSA two stage installer.Įven though this is not an officially supported method from VMware for deploying the VCSA, the process has not changed for the last several releases and it just works which was great for our users. In the early days of vSphere 6.5, the method to deploy the vCenter Server Appliance (VCSA) to Fusion/Workstation was less than ideal with a lot of manual steps. VMware Fusion and Workstation continues to be another popular way for customers to run a VMware Homelab while leveraging a users existing desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |