Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


VMware/ESXi 6- VM Slow

VMware/ESXi 6- VM Slow

VMware/ESXi 6- VM Slow

I created a Win Server 2008R2 and when it boots it gets stuck on Applying computer settings. This can take 2-5 minutes. I am using E1000 network adapter. I changed the adapter to VMXNET2 and it boots really fast but no network. I have VMware tools installed.
Not sure what to do. Not sure what VMXNET2 (Enhaned) and VMXNET3 do then.

RE: VMware/ESXi 6- VM Slow

VMXNet2 is only supported by a few operating systems, 2008 R2 is not one of them. Essentially the difference between E1000 and VMXNet3 is that the E1000 is gigabit and the VMXNet3 can do 10 gig networks. There is a VMWare KB on them. So one of my questions would be on the VM itself. Was this VM a P2V? Are there any mapped drives? How about any printers? How about domain issues? All of these could cause issues (since it sounds like a network issue) so I would start there. If you created the machine via P2V I would go through and find hidden devices in your device manager and remove them. There are "how to's," just Google it.

Here is the VMWare KB: http://kb.vmware.com/selfservice/microsites/search...


The answer is always "PEBKAC!"

RE: VMware/ESXi 6- VM Slow

Thanks for explaining this. This was not a P2V. I will Vmxnet3 and see if that works. I believe this is an issue with the NIC E1000 because when I changed it too the vmxnet2 the machine didn't get stuck on applying computer settings. There are no mapped drives or printers. I don't think there are any domain issues. The only thing I saw in the log was the gpo was taking too long. When I looked that up people pointed to the NIC as the issue. Like I said will try the VMXNet3 tonight. Again, thanks for the explanation.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close