Windows 7 problem in VMware Server.

[johnhc]

I have seen a hang problem running W7 (Ultimate x64) in VMware Server. Please see this thread on the VMware Forums. I have DLed VMware Player (free for private, noncommercial use) and will give that a try (must remove VMware Server). Enjoy, John.

[MrJinje]

What about using the newer vmtools from freeware VMware Player that might provide forward compatibility to vmware server.

I know the tools are backwards compatible, (version 6 tools works on VMware 7), but never tested using a newer tools version with an older VM product. it's worth a shot.

Edited May 11, 2010 by MrJinje

[johnhc]

What about using the newer vmtools from VMware 7 workstation (i.e. get the windows.iso from the trial version) to provide forward compatibility to vmware server.

I know the tools are backwards compatible, (version 6 tools works on VMware 7), but never tested using a newer tools version with an older VM product. it's worth a shot.

MrJinje, thanks.

I installed VMware Player (after removing VMware Server). I pointed to and started both of the VMs (XP x64 and W7 Ult x64) I had created and installed under Server and they both came up and ran under Player. It is simpler, lighter and has fewer functions than Server but I think for the testing I am doing on my builds it will be fine. I have seen no hang problem. For one thing Player DL is much smaller than Server - 90 MB vs 500 MB. Enjoy, John.

Edited May 11, 2010 by johnhc

[MrJinje]

Gotcha, I edited my post to reference using the VMTools that come with the freeware VMware player. Please delete my quote in your post before google crawls through it. Thanks.

But still, I do not think that is an issue, as many VM appliances come pre-loaded with VMTools, and they are freely distributed by third-parties with full consent and support from VMware.com

Good luck, it would still be interesting if someone found out if that solves the issue or not.

Edited May 11, 2010 by MrJinje

[CoffeeFiend]

Personally I think VMWare Server has been very much downhill for the last while. v2 seemed like a big step back (for one the interface to connect -- now it's web-only). And then the [unimpressive] support coming to an end rather quickly (ouch, 3 years only? I would expect WAY more out of a company to run my infrastructure; this is VERY bad), combined with the recent "expiry" bug we've seen (ouch), and the so-so hardware support/requirements of ESX...

It looks like they want to lose their customers to MS and Hyper-V (which is doing a LOT of progress REAL quick) and doing everything they can to accomplish that.

(I *used* to run VMWare Server too)

As for using the tools from the trial of VMWare Workstation in some of their other products I don't think it's much of a problem (but IANAL, and I haven't read the fine print either).

[johnhc]

CoffeeFiend, I think for you that are really using VMware Server in a server environment are in some hurt. So far, I really like the simple window based interface in Player, but suspect it will not do your tasks. Perhaps VMware has decided that they want more revenue. Thanks for your comments. Enjoy, John.

[cluberti]

Given VMWare server's EOL is June 2011, I doubt you'll see anything more than security releases going forward - support for Win7 is likely never going to happen there. Your best bet going forward is either the Player or ESXi, but ESXi is a bit steep for just running appliances. Given that Hyper-V server and Virtual PC are free, you could always give those a shot as well, or perhaps VirtualBox or VMLite (not sure if your requirements are having an always-on server VM host or not).

[johnhc]

Given VMWare server's EOL is June 2011, I doubt you'll see anything more than security releases going forward - support for Win7 is likely never going to happen there. Your best bet going forward is either the Player or ESXi, but ESXi is a bit steep for just running appliances. Given that Hyper-V server and Virtual PC are free, you could always give those a shot as well, or perhaps VirtualBox or VMLite (not sure if your requirements are having an always-on server VM host or not).

cluberti, thanks for your comments. As I am running 64 bit OSs, some of those (VirtualPC for sure) can ruled out. I don't know the others, but I will say again, Player seems to be a good replacement for me. When I do my first install, perhaps I'll change my mind. The link I provided in my first post leads to links that point out the Server EOL. Thanks, John.

[03GrandAmGT]

JohnHC,

Have you tried Sun's Virtualbox? I have been running several instances of Server 2008, "Vail New Home Server", and a couple of versions of W7 with no problems. I was running VMWare for awhile but had a few problems with it and then tried Virtualbox and have had no problems with it so far (1 Year). It was easy to setup and fully configurable for 32 or 64 bit OS's.

Good Luck

John (Yeah another one)

[johnhc]

JohnHC,

Have you tried Sun's Virtualbox? I have been running several instances of Server 2008, "Vail New Home Server", and a couple of versions of W7 with no problems. I was running VMWare for awhile but had a few problems with it and then tried Virtualbox and have had no problems with it so far (1 Year). It was easy to setup and fully configurable for 32 or 64 bit OS's.

Good Luck

John (Yeah another one)

03GrandAmGT, I have not tried VirtualBox. I began using VMware Server (on XP x64) before VB supported x64. It was just natural for me to continue to use it for W7. When I ran into the hangs, my research revealed that Player was also free (for my personal use), so I took advantage of my knowledge/experience with Server - also could use existing VMs. I guess mainly I am too lazy to learn a new virtual system at this time. I will probably give VB a try if I run into problems with Player. Thanks for your comments. Enjoy, John.

[cluberti]

Yeah, if you're using x64 hosts you're limited to Hyper-V from Microsoft or nothing - VMWare player is fine, and VirtualBox and VMLite are also good choices. There are others, but those are the main 3 outside of Virtual PC.