$ rpm - ivh acl-2.2.51-12.el7.x86_64.rpm
error: open of acl-2.2.51-12.el7.x86_64.rpm failed: No such file or directory
The file "acl-2.2.51-12.el7.x86_64.rpm" is apparently not in your working directory. If you run "ls" do you see it? If not, then you can't use that command.
$ rpm - ivh packages\acl-2.2.51-12.el7.x86_64.rpm
Again, if you run "ls packages" do you see the file "acl-2.2.51-12.el7.x86_64.rpm"? If not, you can't use that command.
You're telling rpm where it can find the rpm file it should install. If the rpm file isn't where you're telling rpm it is, it will error out saying it couldn't find it.
Also, it's "/" in Linux/Unix/OSX/etc., not "\".
And it's "rpm -ivh", not "rpm - ivh". Spaces are important.
Again, the CentOS guest does not have access to the physical CD drive in the machine
. Please re-read my earlier post. The guest OS is in a sandbox. ALL of it's "hardware" interfaces are fake, provided by the VM software. Its hard drive is not real (it's just a file on the host system), its network interface is not real, its graphics card is not real, etc. They're just pipes to various pieces of the VM software. Similarly, "/dev/cdrom" in the guest is NOT
your physical CD drive. It's a virtual interface the VM software is providing to the guest to allow you to mount ISO images, etc.
It is, by its very definition a virtual
machine. And that's GOOD! That sandbox is what allows you to experiment with different virtual machines without risking any damage to your host system. If the guest OS had physical access to your machine's hardware, it could wreak all kinds of havoc.
be able to attach the physical CD drive to the guest OS through your VM software (thus detaching it from your Windows host - you'll see the D: drive disappear), but you'll have to check the VM software for that option.
As I said before:
To push data to a VM you would typically either set up the network interface on the guest OS and then copy it over through "normal" means (scp, rsync, nfs, samba, etc.), or you'd set up a shared directory between the host and guest so they can both read/write to some directory on the host system.
Since I've never used Vcenter, I'm afraid I can't be any more specific about that.