[SOLVED] VMware Workstation query

[beta1]

Hi
Can anyone confirm, through usage, that VMware Workstation (6.5) does indeed work in PCLinuxOS 2010.

It's mission critical for me and as I am only going to get a window of a few hours to set up again knowing in advance could be a handy thing methinks.
Thanks for any confirmation.

[beta1]

No it doesn't.

[pinoc]

why not? What problems are encountered? "Does not work" is not useful to debug and then fix the problem. I know for a fact that it does install and that it starts properly because I installed Linux in a VM and then inside that I could install VMWare Workstation 7.0.1 without problems. Maybe instead of using an old version you could try installing the current version 7.0.1?
-p.

[beta1]

Well yes fair comment, I could have elaborated a touch to avoid pointed comment...........

This originally was a post to find out if it worked. I got no response so after 3 weeks I decided I would risk trying it as I wanted to use 2010 and someone has to test I guess as understandably VMware is not high on the list of priorities in this forum.

It wouldn't install, couldn't find the headers and many hours of searching and trying different things got me nowhere. As it happened I was under time constraints as alluded to in this post,  I asked for help re: headers in a different post and didn't get any reply, post since deleted by me as there were no replies, it was no longer relevant, I didn't want to waste anyones time when the post had nothing useful to offer.

I then tried the vmware image in virtualbox, it worked but I hit network problems, posted a query got good help, thankyou again all,  but ended up totally reinstalling my most relevant images.

I didn't see the point is wasting more time, and money on VMware when I needed a solution soon as and there seemed little available support in these forums should it all turn to custard, and especially after having discovered Virtualbox has matured enough since I last tried it to be useful for my purposes.

pinoc it's great you got 7.0.1 to work inside another virtual machine, can you confirm this also works in a non virtualized setting, do you by chance know if vmware 7.0.1 has any advantages over Virtualbox 1.6, (latest 1.8 version doesn't seem to work so well), anyway it's certainly a step forwards from where I was, and you have now let everyone know about it, but I can't help noticing it is not 6.5.xx          sorry couldn't resist that

However my experience remains that 6.5.4 doesn't install to useabilty on kernel 2.6.33.4 in a non virtualized setting because it can't find the headers. I agree with you when you infer 6.5 is old news hence in part was the reason I didn't elaborate.

What I can add is that as a user of vmware for several years now on a daily work basis in comparison Virtual box seems to have better performance in the copy and paste department (crucial to my work), although it does however sometimes lag in the sharing folders department, but hey it works, and I get to earn a crust, still aiming for the butter and jam though.

[pinoc]

When you say it doesn't find the kernel-headers, this refers to compiling the vmware-tools, not the installation of vmware itself. I use VMWare-Fusion on a mac and the the vmware-tools do compile with PCLOS kernel 2.6.32. I have no PC and because of that can not test VMWare-Workstation, or only in a VM inside VMWare-Fusion. I assume the vmware-tools are the same in VMWare-workstation and VMWare-Fusion. The vmware-tools do not compile with 2.6.33 series, I have spent some hours already trying to figure out why, have some clues but not a solution yet. Will continue to debug when time is available, for now if you have 2.6.32 running then there should be no problem with vmware and vmware-tools.
-p.

[beta1]

Vmware installed okay for me as in no dependency problems for the initial package and the like but the first time it was started it then tried to compile a whole list of stuff that used to be done with the vmware-config.pl command (or whatever it exactly was), and of course it can't find the headers so the final part of the build sequence then stops.
Every time I have installed vmware prior to this the vmware-tools are installed in the guest after it is all up and going.

I looked for an "any-any patch" that in the past seemed to get around problems such as this but alas could not find anything let alone something I was willing to trust.
I hope that better describes what was happening.

However for me it is now a moot point really, I would rather have the more accurate and reliable copy and paste function that I am now experiencing between guest and host in Virtualbox. From what I read copy and paste  has always been somewhat flakey in Vmware for many others as well and of course no support for PCLinuxOS. I spent hours working and catching up last night and it was such a joy not having to continually check things.

So I guess that makes me an official  Virtualbox fan.

As a side note - although I have had hassles with converting over to 2010, long hours loss of work etc, it is more than worth it. The default setup provided by Tex, I feel, offers an easy path into the "new way" 

I will just ignore the aaarrrggghhhh moments        when I got the desktop/folder view/ activity/I'm going nuts/ is it salted, plain or roasted departments all mixed up................. and on dual monitors with me changing  a monitor mid performance as well....... why do I do it!!

It must be time to donate.