Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server Archives
Viewing all articles
Browse latest Browse all 69891

Host: winXP64; vmserver 1.0.1 and Solaris 10 u3 vmtools issue

$
0
0

I can't figure this one out.  Solaris 10 64bit virtual machine defined. Install had two issues (both resolved by alternate methods).

 

1. The download .iso image was not readable by vmserver 1.0.1.

Solution:  Burn the DVD and install from physical drive

 

2. Solaris GUI install did not work on 64-bit machine (it did on 32-bit for the same hardware). 

The analyzing hardware popup window never appeared.

Solution: Revert to the Solaris text mode install.

Solaris updates installed fine.

 

Now install vmtools:

\- virtual cdrom image tar expands fine to local filesystem

\- launch vmware-tools-distrib/vmware-install.pl

 

Only a single message appears from the script, and then it hangs for hours.

 

Tried to interrupt it:

Ctrl-C ... refuses, because the uninstall is not in place

Ctrl-Z ... does not put the process in the background

 

Eventually, I had to kill the process ... and now I'm between a rock and hardplace.

 

\- Can't launch the install script again, because "previous version of vmtools already installed".

 

\- Can't launch the bin/vmware-uninstall-tools.pl

Unable to find the answer LIBDIR in the installer database

/etc/vmware-tools/locations

 

The last entry in the locations file is:

file /etc/vmware-tools/cron.d/cron.deny ...

 

It would be more convenient if the install script had a -verbose flag so that it's actions were directly observable.

 

I can't figure out the perl ... what is the "INSTALLDB" referring to?

It appears to be putting out some progress log messages that might help.

 

I saw the post about missing 64-bit device drivers, and vmtools running in compatibility mode.  Is that part of the problem?

 

Message was edited by: dickdunbar


Viewing all articles
Browse latest Browse all 69891

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>