Ok loved the whs 2011 running in vm on hyper v 2012r2 core. Now thinking of moving on to 2012r2 essentials as vm on the core price has come down some. I have a 2 cpu supermicro motherboard and want more memory and cpu processors than 2011 allows. So I have set the 2012 up as a gen2 and all is running great.
Here's the problem when I add any hard drive from drive pool to the new vm server 2012er2 from whs2011 the new server won't start. Ironically I can add the drives while 2012er2 is running soon as a reboot it won't start again. It will start with a drive added that was not part of the pool from 2011. The new vm server drive is set to gpt and dedicated to that vm and not mbr as all the other drives don't know if that is an issue. Would like to move on to all gpt. Is their some reason the drivepool disc will not load to 2012er2? I'm only running one vm at a time. The disc are installed as physical drives passed thru. I have tried removing them from 2011 and that don't work either while it is shut down it really shouldn't matter anyway. Put the disc back into whs2011 and working fine. Any help appreciated hate to have to transfer all the data and reformat but that is looking like what I may have to do.
Also should I bare metal the server 2012 essentials is another question? I like the versatility of the server running in vm that is my preference. Bare metal running just the hyper-v core is so stable ever minding the ease of rebuilding server software in vm makes life simple. Now just to get 2012er2 up and running it looks promising except this disc migration problem. I could bare metal 2012er2 and run the whs2011 virtually this is not really what I want. Your suggestions please.
Question
sspell
Ok loved the whs 2011 running in vm on hyper v 2012r2 core. Now thinking of moving on to 2012r2 essentials as vm on the core price has come down some. I have a 2 cpu supermicro motherboard and want more memory and cpu processors than 2011 allows. So I have set the 2012 up as a gen2 and all is running great.
Here's the problem when I add any hard drive from drive pool to the new vm server 2012er2 from whs2011 the new server won't start. Ironically I can add the drives while 2012er2 is running soon as a reboot it won't start again. It will start with a drive added that was not part of the pool from 2011. The new vm server drive is set to gpt and dedicated to that vm and not mbr as all the other drives don't know if that is an issue. Would like to move on to all gpt. Is their some reason the drivepool disc will not load to 2012er2? I'm only running one vm at a time. The disc are installed as physical drives passed thru. I have tried removing them from 2011 and that don't work either while it is shut down it really shouldn't matter anyway. Put the disc back into whs2011 and working fine. Any help appreciated hate to have to transfer all the data and reformat but that is looking like what I may have to do.
Also should I bare metal the server 2012 essentials is another question? I like the versatility of the server running in vm that is my preference. Bare metal running just the hyper-v core is so stable ever minding the ease of rebuilding server software in vm makes life simple. Now just to get 2012er2 up and running it looks promising except this disc migration problem. I could bare metal 2012er2 and run the whs2011 virtually this is not really what I want. Your suggestions please.
Link to comment
Share on other sites
20 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.