VMware Communities
jeremym
Enthusiast
Enthusiast
Jump to solution

Before I bang my head harder: Has anyone ever gotten WS12 VDI working with Hyper-V within VMW 9?

Hi Gang.

I'm trying to do a quick proof of concept of "Windows Server 2012 Hyper-V / VDI within VMW 9.0". So, if you're familiar with WS12, this screen: http://screencast.com/t/7H5eWj6X

Every time I try to perform the work, I fail at the last mile -- creating the "Virtual desktop collection"  based upon the VHD I give WS12.

(Here's a seven second video showing the moment of failure: http://screencast.com/t/c8R36ccEfR )

My *WORKING THEORY* is that Hyper V / VDI docs say that the VHD used as the prototype for the pool must have the software-based "RemoteFX 3D Video Adapter" in it. (Screenshot: http://screencast.com/t/cUE8Ee3jVCI

So, here's the two part question:

1. Has anyone here .. ever.. gotten WS12 VDI working with Hyper-V running within VMW 9 as a guest? That is, were you able to get VDI quickstart mode to complete on this screen (Creating the "Virtual Desktop collection": http://screencast.com/t/eTQZAxq3 )

2. If yes (or no) to #1.. Did you need to light up the software-based "RemoteFX 3D Video Adapter" inside the VHD prototype in order to do it? (If yes to this, how did you do that?)

For question #2, I have turned on "Accelerate 3D Graphics" in the guest definition, but it doesn't seem to make a difference to the guest either way.

Thanks in advance.

-Jeremy M

Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
jeremym
Enthusiast
Enthusiast
Jump to solution

And 40 minutes later, I have my own answers:

1. My problem was that I hadn't allocated enough memory to the prototype VHD. Apparently it requires 2GB of memory when originally set in Hyper V. That did the trick.

2. Also, I didn't need the RemoteFX 3D Video Adapter in the prototype VHD. It seems like its a nice to have, not a NEED to have.

I'm off and running now.

View solution in original post

Reply
0 Kudos
1 Reply
jeremym
Enthusiast
Enthusiast
Jump to solution

And 40 minutes later, I have my own answers:

1. My problem was that I hadn't allocated enough memory to the prototype VHD. Apparently it requires 2GB of memory when originally set in Hyper V. That did the trick.

2. Also, I didn't need the RemoteFX 3D Video Adapter in the prototype VHD. It seems like its a nice to have, not a NEED to have.

I'm off and running now.

Reply
0 Kudos