puppylinux
Contributor
Contributor

vmware-config.pl problems on install.

Vmware Workstation refuses to configure onto puppy linux 2.17.

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor done

Unable to stop services for VMware Workstation

Execution aborted.

once lines are removed:

line 10126:

print "would have caused error 2. \n"; # error('Unable to stop services for ' . vmware_product_name() . "\n\n");

I can now run the configuration script:

./vmware-config.pl

which now gives a good run until:

...to the fullest extent permitted by law.

SDK 4.05.07

Do you accept? (yes/no) yes

Thank you.

In which directory do you want to install the VMware VIX API binary files?

Use of uninitialized value in subtraction :smileyminus: at /tmp/vmware-vix-installer0/vmware-vix-distrib/vmware-install.pl line 4052.

There is insufficient disk space available in /usr/bin. Please make at least

an additional 152k availableor choose another directory.

In which directory do you want to install the VMware VIX API binary files?

I have checked that there is 500mb+ space on drive, so is there any way to fix this?

the file /tmp/vmware-vix-installer0/vmware-vix-distrib/vmware-install.pl

is created during config, so I dont seem to be able to correct it.

Any help welcome.

0 Kudos
24 Replies
puppylinux
Contributor
Contributor

Forgot:

Puppy-Linux 2.17

Workstation 6

0 Kudos
puppylinux
Contributor
Contributor

Sorry to bug you, Kev.

How does VMWARE go onto non standard Linuxes when the perl scripts fail to configure.

Does anyone else think this is 'shoddy'?

: (

0 Kudos
RDPetruska
Leadership
Leadership

>Does anyone else think this is 'shoddy'?

Not me. VMware clearly publishes a list of Supported host OS's. To me, this points out yet one more reason why Linux will never catch on at the consumer desktop level... there are FAR too many (mostly incompatible) combinations of kernels, versions, distributions, package managers, filesystems, etc. to ever make sense to a "Joe User" consumer.

In regards to your problem... have you tried using Petr's latest vmware-any-any-update patch, since you are running on an unSupported Linux host? http://platan.vc.cvut.cz/ftp/pub/vmware/

0 Kudos
KevinG
Immortal
Immortal

The VMware Workstation documentation lists the supported host OS's.

I don't believe that you will find Puppy-Linux as a supported host OS, so I am not sure how you can call this shoddy.

I personally have not installed Puppy-Linux so, I am not sure how it is configured.

Many of the other non supported Linux distributions like Debian, Fedora..etc don't seem to have this issue so there must be something unique to this Linux distribution.

By the way, Petr's latest vmware-any-any-update patch is most likely not going to help you since it's failing in the Perl script and not with the compile of the kernel modules. You have not even got as far as compiling the modules.

0 Kudos
puppylinux
Contributor
Contributor

Rdpesky - thanks for your response, but I'm interested in getting this working and don't want to start a discussion on whether this or that is better - if you saw beryl running on my machine you would just give up and go cryin' back to micro$haft...

Kev - Thanks for your resopnse.

1) The word 'shoddy' produces 130 hits on your site search - so yes, shoddy does seem to fit, and it appears that I am not alone in describing this part of your product as shoddy. Which it is:

http://search.vmware.com/search?site=VMware_Site&client=VMware_Site&filter=0&proxystylesheet=VMware_...

\[edit] and google seems to agree!

http://www.google.co.uk/search?hl=en&q=vmware+shoddy&btnG=Search&meta=

2) You may not have tried Puppy, fair enough, but you're missing out on one of the best distro's ever created - rush out and get it now.

\[edit] - Google agrees

http://www.google.co.uk/search?hl=en&q=puppylinuxrocks&btnG=Google+Search&meta=

It's a work in progress \[edit - scratch that - work of art] however other distros do seem to be having problems with your perl scripts - a search on your forum for the very shoddy vmware-config.pl produces too many results to be useful !

The any-any-update will not help, as I'm installed, just not configured correctly.

So - the question is -

Can you help me, or are you going to palm me off with another generic response like "get another computer / OS".

With a little messing about I managed to get player to configure, but the process of configuration / compilation seems a little different for workstation and I just cant get it to go.

Help anyone?

0 Kudos
Liz
Virtuoso
Virtuoso

Can you post a copy of the df output?

0 Kudos
puppylinux
Contributor
Contributor

Thanx Liz.

The Terminal output is at the top of the post.

You will see I have got past the EULA, however the script fails, complaining:

In which directory do you want to install the VMware VIX API binary files?

Use of uninitialized value in subtraction :smileyminus: at /tmp/vmware-vix-installer0/vmware-vix-distrib/vmware-install.pl line 4052.

There is insufficient disk space available in /usr/bin. Please make at least

an additional 152k availableor choose another directory.

In which directory do you want to install the VMware VIX API binary files?

And keeps asking the same question.

I seem to have isolated the problem in the player install, howerver the workstation install recreates this faulty code each time I run it again, from a tarball in the the vmxware-vix-distrib, and it is beyond me to straighten this out (although I have tried moding the /vmware-distrib/vmware-vix/vmware-vix.tar.gz but have not managed to get that right, so have given up and come crying for help !

0 Kudos
Liz
Virtuoso
Virtuoso

Thats not the output of df.

Thats the install script..

df is the command showing how much disk space is free for all the mount points.

0 Kudos
puppylinux
Contributor
Contributor

My mistake. Here's df -

sh-3.00# df

Filesystem 1k-blocks Used Available Use% Mounted on

/dev/root 1652 873 779 53% /initrd

/dev/hda5 30869840 29144640 1725200 94% /initrd/mnt/dev_save

/dev/loop0 77312 77312 0 100% /initrd/pup_ro2

/dev/loop1 1290112 819248 470864 64% /initrd/pup_rw

/dev/loop3 67520 67520 0 100% /initrd/pup_ro3

/dev/loop4 52352 52352 0 100% /initrd/pup_ro4

unionfs 1290112 819248 470864 64% /

sh-3.00#

As you see, unionfs has just short of 500mb, after the installation tar.gz has been placed.

I have -plenty- of disk space. REALLY.

The problem is the perl script vmware-config.pl ....

Use of uninitialized value in subtraction :smileyminus: at /tmp/vmware-vix-installer0/vmware-vix-distrib/vmware-install.pl line 4052.

At line 4052 of that script:

return ($dstSpace - $srcSpace);

On the player install / configure I was able to edit all occurrences of this to:

return (1000000); # return ($dstSpace - $srcSpace);

Which worked, and allowed me to finish the config.

On workstation, this file is created 'on the fly' and I have not been able to fix the file it comes from (I'm fairly new with Linux - less than a year).

Here's the whole subroutine from the installer:

\### Does the dstDir have enough space to hold srcDir

sub check_disk_space {

my $srcDir = shift;

my $dstDir = shift;

my $srcSpace;

my $dstSpace;

my @parser;

  1. get the src usage

open (OUTPUT, shell_string($gHelper\{'du'}) . ' -sk ' . shell_string($srcDir)

. ' 2>/dev/null|') or error("Failed to open 'du'.");

$_ = ;

@parser = split(/\s+/);

$srcSpace = $parser[0];

close OUTPUT;

  1. Before we can check the space, $dst must exist. Walk up the directory path

  1. until we find something that exists.

while (! -d $dstDir) {

$dstDir = internal_dirname($dstDir);

}

open (OUTPUT, shell_string($gHelper\{'df'}) . ' -k ' . shell_string($dstDir)

. ' 2>/dev/null|');

while () {

@parser = split(/\s+/);

if ($parser[0] ne 'Filesystem') {

$dstSpace = $parser[3];

}

}

close OUTPUT;

  1. Return the amount of space available in kbytes.

return ($dstSpace - $srcSpace); #<<<<<* line 4052

}

I must say that it looks good to me in its origional form and I can't see (even with 'use strict' ) why it is failing.

Can anyone else?

What I'm looking for is a patched config, or help patching the existing one.

Message was edited by:

puppylinux

0 Kudos
puppylinux
Contributor
Contributor

Liz -

To quote my first post:

" ... I have checked that there is 500mb+ space on drive, so is there any way to fix this? "

As you see, I checked that I had not run out of disk space.

Any ideas?

Message was edited by:

puppylinux

0 Kudos
oreeh
Immortal
Immortal

I think it is failing due to the unionfs and its behaviour (layering multiple filesystems into one filesystem).

0 Kudos
puppylinux
Contributor
Contributor

Thanks O.

All the files are in the same physical volume so, no.

I think we're looking at a shoddy perl script.

0 Kudos
oreeh
Immortal
Immortal

The physical volume has nothing to do with the file system.

Unionfs is normally used for boot CDs and ramdisks and not for hard disks (since it requires loop mounts).

The Perl script definitely is not shoddy and surprisingly works with almost every Linux distro and every "regular" file system.

0 Kudos
continuum
Immortal
Immortal

Some guys have successfully managed to get VMserver running in Puppylinux.

They had a lot of problems - most of which were the result of an uncomplete developement environment in Puppylinux.

So before you continue your rants - go visit the Puppylinux-forum and ask how to get that pieces together.

Should be no problem with the best distro on the planet


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
puppylinux
Contributor
Contributor

Fair enough - they deserve a rant too.

So - any ideas beyond 'buzz off' ?

And if the fault lies with your shoddy script, which I believe to be the case, how shall we handle it then?

Do you have a hat or a bit of humble pie to hand?

Message was edited by:

puppylinux

0 Kudos
continuum
Immortal
Immortal

Rants don't help.

Suggestion: do your homework and fix the environment.

Then try to compile and install VMserver - if that works you can very likely rule out problems with Puppylinux.

If then WS 6 install still fails even after applying the any2any patches we can look into it again.

I don't need a hat - german roofs are rain-resistant - why are you asking ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
puppylinux
Contributor
Contributor

oreeh > "The physical volume has nothing to do with the file system. Unionfs is normally used for boot CDs and ramdisks and not for hard disks (since it requires loop mounts). "

I agree.

oreeh > The Perl script definitely is not shoddy and surprisingly works with almost every Linux distro and every "regular" file system."

I disagree - your forum is full of posts from users on 'supported' platforms with different problems that have had to be patched with that any-any-old-nonsense - so cut the guff.

continuum > Rants don't help.

You used the word first - I was humouring you.

Suggestion: do your homework and fix the

environment.

My Suggestion: do your job and fix the scripts!

Then try to compile and install VMserver - if that

works you can very likely rule out problems with

Puppylinux.

I have already managed this for server and player, however Workstation 6 refuses to fix with the same approach I used to 'manage the installation' (code for fix your shoddy scripts) of server and workstation does not work with Workstation 6.

If then WS 6 install still fails even after applying

the any2any patches we can look into it again.

Well yes - lets look again!

I don't need a hat - german roofs are rain-resistant

- why are you asking ?

: )

0 Kudos
continuum
Immortal
Immortal

FYI: all answers you got to this post came from guys that DO NOT work for VMware so stop this : fix your shoddy script talk unless you want us to loose patience

FYI: as Linux kernels change like the weather you can not expect it to work with any newer custom kernel - that is why Petr maintains this "any-any-old-nonsense"

Why don't you compile on a regular complete Linux that uses the same kernel as puppy and then import modules from there manually ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
puppylinux
Contributor
Contributor

FYI: all answers you got to this post came from guys

that DO NOT work for VMware

What answers do you see in this post? The only sensible question came from Liz (a fellow brit) 'Are you out of disk space'?

Not bad for a girl, but not really an answer, I hope you will agree.

so stop this : fix your

shoddy script talk unless you want us to loose

patience

Sensorship, from Germany (or are you a yank?) what a suprise.

Are you not a bit worried that customers will work out that there are other alternatives that DO work on a wide range of distributions, almost out of the box?

FYI: as Linux kernels change like the weather you can

not expect it to work with any newer custom kernel -

that is why Petr maintains this

"any-any-old-nonsense"

That work would not be required if you lot kept the scripts as compatible as possible.

Why don't you compile on a regular complete Linux

that uses the same kernel as puppy and then import

modules from there manually ?

Would that work?

I've ditched the other distro's that we have evaluated and gone 4 puppy.

Anyhoo -

Is there a fix to this shoddy script or are we going to have to do it for you?

0 Kudos