首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >EL 7.2未能使用open 9.10运行自定义

问EL 7.2未能使用open 9.10运行自定义
EN

Server Fault用户
提问于 2016-07-22 20:16:14
回答 1查看 917关注 0票数 1

是否有人成功地使用EL (RHEL或CentOS) 7.2个来宾运行客户自定义?

系统为VMware vCloud Director5.6.5和VMware ESXi 5.5。

v7.2附带了open 9.10.2,它应该包含所有必要的VMware工具等价物。

我尝试过将/etc/redhat-版本设置为7.0字符串。我已经安装了perl。我没有试图降级到旧的开放-vm-工具+vmware-部署like,因为我想坚持7.2包。

这是一些输出..。

代码语言:javascript
复制
[root@localhost ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.0 (Maipo)

[root@localhost ~]# which perl
/usr/bin/perl

[root@localhost ~]# vmware-toolbox-cmd -v
9.10.2.48224 (build-2822639)

[root@localhost ~]# cat /var/log/vmware-imc/toolsDeployPkg.log 
## Starting deploy pkg operation
Deploying /tmp/vmware-root/709d2d0c/cust93117962197543457.cab
Initializing deployment module. 

Cleaning old state file from tmp directory. 

EXIT STATE INPROGRESS 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.INPROGRESS (No such file or directory) 

EXIT STATE Done 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.Done (No such file or directory) 

EXIT STATE ERRORED 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.ERRORED (No such file or directory) 

Setting deploy error: Success. 

Deploying cabinet file /tmp/vmware-root/709d2d0c/cust93117962197543457.cab. 

Transitioning from state (null) to state INPROGRESS. 

ENTER STATE INPROGRESS 

Reading cabinet file /tmp/vmware-root/709d2d0c/cust93117962197543457.cab. 

Creating directory /tmp
Creating directory /tmp/.vmware
Creating directory /tmp/.vmware/linux
Creating directory /tmp/.vmware/linux/deploy
Extracting package files. 

Launching deployment /usr/bin/perl -I/tmp/.vmware/linux/deploy/scripts /tmp/.vmware/linux/deploy/scripts/Customize.pl /tmp/.vmware/linux/deploy/cust.cfg. 

Command to exec : /usr/bin/perl 

sizeof ProcessInternal is 56

## Starting deploy pkg operation
Deploying /tmp/vmware-root/709d2d0c/cust93117962197543457.cab
Initializing deployment module. 

Cleaning old state file from tmp directory. 

EXIT STATE INPROGRESS 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.INPROGRESS (No such file or directory) 

EXIT STATE Done 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.Done (No such file or directory) 

EXIT STATE ERRORED 

Setting deploy error: Error removing lock /tmp/.vmware-deploy.ERRORED (No such file or directory) 

Setting deploy error: Success. 

Deploying cabinet file /tmp/vmware-root/709d2d0c/cust93117962197543457.cab. 

Transitioning from state (null) to state INPROGRESS. 

ENTER STATE INPROGRESS 

Reading cabinet file /tmp/vmware-root/709d2d0c/cust93117962197543457.cab. 

Creating directory /tmp
Creating directory /tmp/.vmware
Creating directory /tmp/.vmware/linux
Creating directory /tmp/.vmware/linux/deploy
Extracting package files. 

Launching deployment /usr/bin/perl -I/tmp/.vmware/linux/deploy/scripts /tmp/.vmware/linux/deploy/scripts/Customize.pl /tmp/.vmware/linux/deploy/cust.cfg. 

Command to exec : /usr/bin/perl 

sizeof ProcessInternal is 56

Returning, pending output from stdout
Returning, pending output from stderr
Process exited normally after 0 seconds, returned 127
No more output from stdout
No more output from stderr
Customization command output: 

Customization process returned with error. 

Deployment result = 127 

Setting generic error status in vmx. 

Transitioning from state INPROGRESS to state ERRORED. 

ENTER STATE ERRORED 

EXIT STATE INPROGRESS 

Setting deploy error: Deployment failed. The forked off process returned error code. 

Deployment failed. The forked off process returned error code. 

No nics to enable.

Launching cleanup. 

Command to exec : /bin/rm 

sizeof ProcessInternal is 56

Returning, pending output from stdout
Returning, pending output from stderr
Process exited normally after 0 seconds, returned 0
No more output from stdout
No more output from stderr
Customization command output: 

Deploy error: Deployment failed. The forked off process returned error code. 

Package deploy failed in DeployPkg_DeployPackageFromFile
## Closing log
[root@localhost ~]#
EN

回答 1

Server Fault用户

回答已采纳

发布于 2016-07-22 20:57:44

我稍微戳了一下这个映像,注意到perl可执行文件都是0 kb。我不知道这是怎么发生的,但我愿意责怪我的几个失败的测试和重新启动。

对于将来的参考,对于那些想要从ISO中完全控制包的人来说,这应该会让你开始并运行。这还将创建一个工作模板,而不需要访问Internet (yum)。

代码语言:javascript
复制
# Run minimal install
# Reboot
# Re-insert installation ISO
mkdir -p /media/cdrom
mount /dev/cdrom /media/cdrom
cd /media/cdrom/Packages

# Install perl and all dependencies
rpm -Uvh perl-5.16.3-286.el7.x86_64.rpm perl-Carp-1.26-244.el7.noarch.rpm perl-Encode-2.51-7.el7.x86_64.rpm perl-Exporter-5.68-3.el7.noarch.rpm perl-File-Path-2.09-2.el7.noarch.rpm perl-File-Temp-0.23.01-3.el7.noarch.rpm perl-Filter-1.49-3.el7.x86_64.rpm perl-Getopt-Long-2.40-2.el7.noarch.rpm perl-HTTP-Tiny-0.033-3.el7.noarch.rpm perl-PathTools-3.40-5.el7.x86_64.rpm perl-Pod-Escapes-1.04-286.el7.noarch.rpm perl-Pod-Perldoc-3.20-4.el7.noarch.rpm perl-Pod-Simple-3.28-4.el7.noarch.rpm perl-Pod-Usage-1.63-3.el7.noarch.rpm perl-Scalar-List-Utils-1.27-248.el7.x86_64.rpm perl-Socket-2.010-3.el7.x86_64.rpm perl-Storable-2.45-3.el7.x86_64.rpm perl-Text-ParseWords-3.29-4.el7.noarch.rpm perl-Time-HiRes-1.9725-3.el7.x86_64.rpm perl-Time-Local-1.2300-2.el7.noarch.rpm perl-constant-1.27-2.el7.noarch.rpm perl-libs-5.16.3-286.el7.x86_64.rpm perl-macros-5.16.3-286.el7.x86_64.rpm perl-parent-0.225-244.el7.noarch.rpm perl-podlators-2.5.1-3.el7.noarch.rpm perl-threads-1.87-4.el7.x86_64.rpm perl-threads-shared-1.43-6.el7.x86_64.rpm

# Install open-vm-tools and dependencies
rpm -Uvh open-vm-tools-9.10.2-4.el7.x86_64.rpm libdnet-1.12-13.1.el7.x86_64.rpm libicu-50.1.2-15.el7.x86_64.rpm libmspack-0.5-0.4.alpha.el7.x86_64.rpm net-tools-2.0-0.17.20131004git.el7.x86_64.rpm

cd
umount /media/cdrom

# vmtoolsd is enabled, but you can start it to verify that vCloud picks it up
systemctl start vmtoolsd

# stop the VM
# customize via vCloud - I changed hostname and did a simple configuration script
#   that echos to a file to make sure things are working
# vApps > Virtual Machines > Power On and Force Recustomization
# log in and verify updated hostname, new file that was echoed, and possibly
#   new IP if you were set to DHCP
票数 0
EN
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://serverfault.com/questions/791508

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档