VMware Communities: Problem with Windows Server 2008 R2 ...

VMware

Up to Discussions in OS Compatibility

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

1 2 Previous Next 19 Replies Last post: Nov 3, 2009 10:45 AM by dramatik2

Problem with Windows Server 2008 R2 posted: Sep 4, 2009 6:41 AM

Horinius

184 posts since
Jun 20, 2006

Windows Server 2008 R2 guest might not be officially supported yet by VMWare. If that's the case, hope this post could help them improve the support.

I've tried WS2008 R2 Standard (64bits) in VMWare Server 2.0.1 and Workstation 6.5.3

From time to time, my WS2008 would freeze indefinitely. It's not even possible to shut it down. The only way is to suspend it and if a snap-shot exists, go back to previous snap-shot and hope it won't freeze again.

I have no evidence what really caused this, but I have a little idea. It's VMWare Tools.

I noticed the following error event about "side by side":

Activation context generation failed for "C:\Program Files\VMware\VMware Tools\VMControlPanel.cpl". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

When such error happens, WS2008 would freeze sooner or later.

NB: WS2008 freezes more on VMWare Server than on Workstation.

Re: Problem with Windows Server 2008 R2

1. Sep 4, 2009 8:40 AM

in response to: Horinius

TobiasKracht

508 posts since
Aug 31, 2009

Windows 7 will be supported only in the Workstation 7.

StarWind Software R&D

Re: Problem with Windows Server 2008 R2

2. Sep 4, 2009 9:18 AM

in response to: TobiasKracht

Horinius

184 posts since
Jun 20, 2006

Sure, but while waiting for this, maybe they could change a little bit in VMWare Tools. Windows Server 2008 R2 isn't that different from Windows Server 2008. And in my last WS2008R2 guest, I didn't install the VMWare Tools and it's has been running for 6 hours without any problem or freezing.

Re: Problem with Windows Server 2008 R2

3. Sep 4, 2009 11:31 AM

in response to: Horinius

jmattson

1,220 posts since
Mar 29, 2006

What kind of NIC(s) do you have installed in the working and non-working guests?

Re: Problem with Windows Server 2008 R2

4. Sep 7, 2009 1:05 AM

in response to: jmattson

Horinius

184 posts since
Jun 20, 2006

Both are the same: bridged.

The only difference, as I've written it, is that the working guest has no VMWare Tools installed.

Re: Problem with Windows Server 2008 R2

5. Sep 7, 2009 1:24 AM

in response to: Horinius

TobiasKracht

508 posts since
Aug 31, 2009

WS2k8R2 has a little difference, but no so much. My WS28R2 server works perfectly with VmWare Tools and has no problems with bridged network.

StarWind Software R&D

Re: Problem with Windows Server 2008 R2

6. Sep 7, 2009 2:02 AM

in response to: TobiasKracht

Horinius

184 posts since
Jun 20, 2006

TobiasKracht wrote:WS2k8R2 has a little difference, but no so much. My WS28R2 server works perfectly with VmWare Tools and has no problems with bridged network.

Yours is also 64bit? Your VMWare Server is also 2.0.1?

Re: Problem with Windows Server 2008 R2

7. Sep 7, 2009 2:12 AM

in response to: Horinius

TobiasKracht

508 posts since
Aug 31, 2009

Yes, WS2k8R2 is only x64 available.

StarWind Software R&D

Re: Problem with Windows Server 2008 R2

8. Sep 7, 2009 2:22 AM

in response to: TobiasKracht

Horinius

184 posts since
Jun 20, 2006

I always create my VMs in my VMWare Workstation (6.5.3) before moving them to VMWare Server. I don't know if this is the cause....

Re: Problem with Windows Server 2008 R2

9. Sep 17, 2009 2:54 PM

in response to: Horinius

bjdku

1 posts since
Dec 11, 2007

I am seeing the same problem. Here: http://bit.ly/UEdKI They are talking about how it is the e1000 network card. However, I tried changing it to VMXNET 3 and that didn't help me.

I wonder if this is the same problem that vSphere Client has on Windows 7, which is the same code base as Server 2008 R2. Some incompatibility with .NET 3.5 in the Windows 7/Server 2008 R2 Code.

This was resolved by putting a non-windows 7 System.dll (path Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher) file on the Windows 7 machine and then creating the folowing batch file:
SET DEVPATH=%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
SET PATH="%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\";%PATH%
start /B VpxClient

I know this is a shot in the dark, but maybe they are related somehow.

Re: Problem with Windows Server 2008 R2

10. Sep 18, 2009 1:17 AM

in response to: bjdku

Horinius

184 posts since
Jun 20, 2006

Now I understand why jmattson asked me "what kind of NIC" I had installed in the guests. Seems like ESX allows you to change NIC. But this isn't possible in VMWare Server, nor is it possible in WorkStation. So, all these remarks are irrelevant here.

Re: Problem with Windows Server 2008 R2

11. Sep 18, 2009 7:38 AM

in response to: Horinius

jmattson

1,220 posts since
Mar 29, 2006

Horinius wrote:
Now I understand why jmattson asked me "what kind of NIC" I had installed in the guests. Seems like ESX allows you to change NIC. But this isn't possible in VMWare Server, nor is it possible in WorkStation. So, all these remarks are irrelevant here.

To change the virtual NIC, you may have to edit the configuration file by hand and change:

ethernet0.virtualDev = "e1000"

to, say,

ethernet0.virtualDev = "vmxnet3"

Re: Problem with Windows Server 2008 R2

12. Sep 18, 2009 9:46 AM

in response to: jmattson

Horinius

184 posts since
Jun 20, 2006

Change by hand! ... OIC

Besides e1000 and vmxnet3, is there any other choice?

Re: Problem with Windows Server 2008 R2

13. Sep 18, 2009 10:16 AM

in response to: Horinius

jmattson

1,220 posts since
Mar 29, 2006

I'm no expert on virtual networking, but I believe that the other choices are "vlance," "vmxnet," and "vmxnet2." Some choices may not be available for some guests.

Re: Problem with Windows Server 2008 R2

14. Sep 27, 2009 1:14 AM

in response to: jmattson

Antman147

17 posts since
May 14, 2006

I too am having lock up issues, am using Windows Server 2008 R2 (RTM) as the Host for VMware Server v2.01.

I have the Host machine (Win2k8 R2 RTM), also a Guest machine (Win2k8 R2 RTM), however i regularly get lock ups transferring files across the network.

From my desktop PC, if i attempt to copy an ISO file from a share on the Host Machine to a share on the Guest Machine it will freeze the entire Host Server (including all virtual machines).

This lock up occurs from a clean bootup, with no remote desktop access.

I have seen in other (ESX) threads suggestions to change the Network Card Type to 'VMXNET3' however VMware Server Console states this network type is not supported (when VMX file is manually edited). If i change it to 'vmxnet' the console suggests it is not compatible with the 64Bit Guest OS.

Without the ability to change the network card type i guess my next step is to try a different Driver for the Guest OS.

1 2 Previous Next Go to original post

Go to original post

Search VMware Communities Advanced Search

Actions

View as PDF

Up to Discussions in OS Compatibility