New
#21
Hi there
@Ztruker
To prevent activation issues in future if moving / fiddling around with VM's ensure the UUID of the VM doesn't change -- kari can probably explain how to do it with VM's in HYPER-V --on VMWare you get a popup on first boot of a copied / moved VM giving you a choice of "I moved it" or "I copied it". Choose the "I moved it" option --this preserves the machine UUID so you won't get activation problems when moving / cloning a VM.
Cheers
jimbo
The VM continues to run, you can connect to it again from within Hyper-V Manager.
I'm not sure how Oracle does it, but AIUI VMWare runs the VM process as your user account. Hyper-V runs it as SYSTEM, meaning you can even sign out and the VM continues to run. You can then use RDP to connect to the VM from another machine if you wish (you'll first need to enable remote desktop in the VM to allow this).
In the settings for each VM there are options for Automatic Start Action and Automatic Stop Action. You can set a VM to always start when the host machine boots and to save it's state when the host shuts down. That way it will always be available via rdp from another machine.
I think it was mentioned already in the thread (or else elsewhere) but IMO you're really better off using Remote Desktop for manipulating the VM versus using the native display in the Hyper-V VMM.
@Kari - re: rule of thumb of CPU:vCPU ratio 2:1 - is that physical core, or physical core + HT?
On virtual machines I might run at the same time than other virtual machines, one vCPU per two host logical processors, in my case four vCPU per VM:
On virtual machines I allocate more vRAM and know I never run them with other virtual machines running at the same time, one vCPU per one host logical processor. In my case 8 vCPU.
Kari
You don't even need to open the window in the first place. Select the VM in Hyper-V Manager and click the Start button near the bottom of the Actions pane on the right (or select Start from the Action menu).
NB: you must first run the VM and enable Remote Desktop in its settings before it will accept RDP connections.
Okay, using RDT is the same as a local window, which is already a RDT as far as Hyper-V is concerned. The only difference I see so far is it's slower. Not bad though.
I like the fact that when I want to look at it I just open Network Connections, right click on the VM and select Connect with RDT and I'm there.