Click here to Skip to main content
15,891,777 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I considered the number of hours it takes to set up all the various Visual Studios, SDKs, tools, etc.; how I try to keep my dev machine as clean as possible; and how all of the above fill the installed programs list with all the various SQL components and runtimes.

I decided to install them all in a VM, and use that as my dev platform; at least as an experiment.

I fired up Hyper-V and created a new VM and installed everything and tried to use it yesterday. It was a bit sluggish, though that couls just be because I'm used to an SSD for my system disk, and this is on a virtual disk that is on a spinning disk.

The main issue however, is that VS2012 keeps freezing. The UI freezes, and it's doing god knows what in the background. Usually it doesn't respond at all and either needs to be left alone for 15 minutes, or force closed. Occasionally I'll get the "Waiting for a background operation to complete..." message.

Has anyone else tried this? What were your results?

My VM is using hardware virtualization on a Core i7. The host has 16GB RAM and the client has 4GB (it's using half of that).

Note: A clue may be that I sometimes get low virtual memory messages.
Posted
Updated 20-Dec-13 3:14am
v2
Comments
Ron Beyer 20-Dec-13 9:16am    
How much memory did you assign to the VM? What VM are you using? I use Oracle VirtualBox and VMWare and haven't had any issues as long as I give it enough resources.
Yvan Rodrigues 20-Dec-13 9:19am    
I'm using Hyper-V. Both the host and client are Windows 8 64-bit. The host has 16GB and the client has 4GB.

This article suggests using LARGEADDRESSAWARE to allow 32-bit applications use more that the logical limit, which I haven't heard of: http://submain.com/support/AvoidingOOM.aspx
Ron Beyer 20-Dec-13 9:25am    
I think Win8 requires more than 4gb of RAM, try assigning 8 to the VM, sounds like a lot but Win8 is a hog and so is Visual Studio. Fire up VS on a normal machine, load up a project, and see what your memory usage is.
Albert Holguin 20-Dec-13 16:29pm    
I would def give that more than 4GB... BOTH Win8 and VisualStudio are memory hogs (especially in debug mode).

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900