i just installed a ubuntu 12.04 server on a 2008 R2 Hyper-V server and all is fine (networking/storage ...). There is just one thing, when i halt my linux (using "sudo halt"), i can see on the console that the system is halted but the vm status on hyper-v is still "started".
I’m having several Windows Servers 2008 R2 which I previously accessed using Hyper-V Manager from Windows 7. On upgrading to Windows 8 and enabling the feature Hyper-V, this is no longer possible.
I already looked at this thread: Hyper-V and Hyper-threading: On or off?, but the only answer is Windows specific....
I am building a VM server (using Proxmox VE if that makes a difference) and was wondering about how hyper threading can affect virtual machines...
Specifically, if I max out the number of virtual machines, would hyper threading help, or hurt performance?
Also, the largest virtua
kfl wrote:Any update on this? I'm also hitting it using Arch on Windows 8 Hyper-VI kind of gave up trying when no one posted any solutions. It is at least kind of reassuring to know that its not just me. I'll keep looking. Let me know if you figure it out.solar wrote:Hi... I was testing a bit and found hyper-v to be a pretty shite hv, so testing vmware instead.
Currently, I have a core Hyper-V Server hosting VMs for a domain controller and several domain-joined VDI infrastructure servers.
I log in to my Hyper-v host server
I open the Hyper-V manager, select my server S1 and click Connect
When I want to shut down server S1 or reboot server S1, I just click the start button and select shut down or restart (it's a server 2008 r2).
Now this is my problem.
Im lost and desperate. I have been running with a setup where i have a ubuntu server running in hyper-v. My windows server running hyper-v has two network cards. my internet is coming in to one of them and the other is hooked up with a switch. I then direct both to the ubuntu-server running in hyper-v.
Assume I installed Hyper-V Server 2012. Networking is working fine. The server is locked down, only RDP is enabled. Enabling other ports may not be an option as the server is directly connected to the internet. As I understood it, Hyper-V Server 2012 is simply Windows Server 2012 with the Hyper-V role installed. No other roles are available.
I'm setting up a test "server" on my laptop with Hyper-V. When I go to install from an MSDN ISO I have two choices for standard edition. SERVERSTANDARD or SERVERSTANDARDV.
Googling gives me lists of cracked windows keys, but one site claims that SERVERSTANDARDV is the non Hyper-V flavor. I assume that doesn't contain the Hyper-V server, but wold be safe for a Hyper-V client?