Are other people successfully building CentOS-6.6 x86_64 appliances with vmware-studio?
I was finally able to build a CentOS-6.6 x86_64 appliance in vmware-studio after I added i686 glibc and zlib.
and now when I boot the appliance I can not use vamicli for upgrade.
Can anyone offer any suggestions for me so we can upgrade these appliances? - thanks
(we are currently using CentOS-6.6 i686 successfully)
I also attached: /opt/vmware/var/log/vami/vami-sfcb.log
{noformat}
example:
[root@localhost vami]# vamicli version --appliance
Internal error. Please make sure sfcbd is running.
[root@localhost ~]#
[root@localhost ~]# /etc/init.d/vami-sfcb restart
Shutting down vami-sfcbd: [ OK ]
Starting vami-sfcbd: /usr/bin/dirname: extra operand `-d.pid'
Try `/usr/bin/dirname --help' for more information.
[ OK ]
Checking vami-sfcbd status: [ OK ]
Testing vami-sfcbd: [ OK ]
Initializing vami-sfcbd: [ OK ]
[root@localhost ~]#
[root@localhost ~]# vamicli version --appliance
Internal error. Please make sure sfcbd is running.
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# tail -13 /opt/vmware/var/log/vami/vami-sfcb.log
22/06/2015 17:32:10 [info] [process id: 2864] Number of sfcbd processes: 7
22/06/2015 17:32:10 [info] [process id: 2864] VAMI Scheduler provider is present on the system.
22/06/2015 17:32:10 [ERROR] [process id: 2864] Failed to start Scheduler Service. Unknown error.
22/06/2015 17:32:10 [ERROR] [process id: 2864] Traceback (most recent call last):
File "/opt/vmware/share/vami/vami_sfcb_initialize", line 86, in main
rettuple = vami_cim_util.invokeNonStaticMethod('root/vami', 'VAMI_SchedulerService', 'StartService')
File "/opt/vmware/share/vami/vami_cim_util.py", line 36, in invokeNonStaticMethod
insts = cliconn.EnumerateInstanceNames(className)
File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 382, in EnumerateInstanceNames
**params)
File "/opt/vmware/lib/python/site-packages/pywbem/cim_operations.py", line 219, in imethodcall
raise CIMError(code, tt[1]['DESCRIPTION'])
CIMError: (6, u'Provider not found or not loadable')
{noformat}
