Installing and configuring hyper-v server for those who see it for the first time. Setting up a network in Hyper-V Setting up hyper v
Do not put the Russian version! Not for rugs. I struggled with it for a week, I couldn't figure out why updates weren't installed using the local console, why firewall rules weren't applied, why... The list is long. Having spit on all this, I saved the virtual machine files and installed the English version. Everything works great!
The server image file weighs 1.65 GB and is called
9200.16384.WIN8_RTM.120725-1247_X64FRE_SERVERHYPERCORE_EN-US-HRM_SHV_X64FRE_EN-US_DV5.ISO
Immediately after installation, set up the network (point 8) and install updates (points 5 and 6). If everything went well, then you can move on. If not, check what and how. ghostcomb possible problems at this stage for you is the inability to deliver updates.
Working with Hyper-V without a domain
Our server is not in a domain, but in a workgroup. This gives the advantages of independence and portability of the solution to any conditions - starting from very low-budget solutions, limited only by the cost of equipment, in the case of my stand in the region of 20 tr. But this imposes certain features of the setting. In particular, we must configure the firewall and add a general user.
Add local administrator(item 3 of the server configuration, for example "hyperadmin / hyperpwd"), so as not to use the default administrator). The same user (maybe not an admin) must be added on the machine with which you will connect via RDP. When creating a user on my machine, I wrote this in the "Description" field: to connect to HYPER-V 2012".
Hyper-V firewall
Since I mainly plan to use the MMC console to manage virtual machines, it will be convenient to provide additional equipment for managing the server firewall. This will save a lot of time as I don't plan to do regular rule changes - the server should just work. And I don’t want to keep the syntax of PowerShell and CMD in my head, that’s enough for me and Linux. So I will turn remote access to the firewall! Considering that it is necessary to manage the server in a good way through a network dedicated for this (physically, VLAN), my option will not reduce the overall security. Alternatively, you can install a hardware and software firewall between the host and the network, for example, Mikrotik (without WiFi, of course). This is a very inexpensive solution with acceptable performance and reliability.
Enable feature remote control firewall can be done by executing the console (after all, nowhere without a console) command:
netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
After that, you can run workstation mmc console with "hyperadmin" privileges and add snap-in " Windows Firewall" (in my Windows 7 it is called "Windows Firewall in increased security") and specify the IP address of our Hyper-V server. That's it :)
But no matter what, the console is the most reliable means of control. I still do everything in the console, but I see what's what in the GUI in the "Monitoring - Firewall" section. I'm just not going to keep everything in my head. And this article is one of the how-to options for myself with your comments and additions.
Hyper-V Manager allows you to manage virtual machines, configure virtual networks, disks, start virtual machines, connect to them - i.e. almost everything to start.
Launch Hyper-V Manager as "hyperadmin" user and click "Connect to server" in the upper left. Again, by IP.
The Hyper-V Manager in Windows 7 is designed to manage Hyper-V 2008, not 2012. Options such as Live and Storage Migrations will only be available from Windows 8 (from Windows 7 via PowerShell - please, not via the GUI). Therefore, I decided to install Windows 8 (the trial is enough for now) to compare "how it works" through Windows 8. Nothing like that, there were options for converting VHD disks to VHDX, the same migration buttons that I mentioned a little higher. Well, that's great, of course, but if you decide on the terminology and know exactly what you want, then you can get by with PowerShell and the good old 7th (just recently they also talked about the "good old XP-shku").
In order for the Hyper-V Manager from Windows 8 to show you a list of virtual machines, you need to download the wonderful hvremote script (http://archive.msdn.microsoft.com/HVRemote) and run it on a workstation with administrator rights:
cscript hvremote.wsf /mmc:enable
cscript hvremote.wsf /AnonDCOM:grant
You can also check if everything worked out:
cscript hvremote.wsf /show /target:name_or_ip_of_your_hyper-v_server
Do not worry about the fact that it is still version 0.7, which can still be buggy in Windows 8 and 2012. Everything works! Now you can see your virtual machines (when we create them, of course).
Lyrical digression to move on to the next section Connected, rejoice, start installing the guest virtual machine ... Stop! And how to choose a place for a VHD disk for a virtual machine? The 500 GB disk was not formatted during the installation process - it was not necessary. And now I can only host guest systems on the C:\ drive. And the disk is 60 GB in total. Those. all you have to do is open the controller hard drives, format to NTFS and remap drive letters(DVD will be E:\, 500 GB disk will be D:\ - I hate it when DVD hangs between disks :)). HOW TO DO IT???
Remote Disk Management
For remote disk management ( Disk Management), follow these steps:
1. Start the Virtual Disk Service (VDS) on the server
Viewing a list of services (services) whose names begin with "R" using PowerShell:
Get-Service -Name r*
Starting the VDS (Virtual Disk Services):
If required, enable "Remote Volume Management" on client computer(from which we will manage our server).
If we had not disabled the firewall completely, then point 2 would have to be followed.
2.Allow Disk Management.
Netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
Launch management console MMC snap-ins it is necessary on behalf of the local admin user on our server (in our case "hyperadmin / hyperpwd"):
In the snap add "Disk Management" (not local computer, and remote, for example, by IP address).
Well, actually, the initial routine is over. Now you can safely create virtual machines. Hyper-V Manager must also be run as "hyperadmin / hyperpwd".
Good afternoon. Thanks to my site, I constantly tinker with the operating system and, of course, over time I began to look for a way so that I could write instructions, but at the same time make fewer changes to the operating system of my work computer ... The solution came elementary - a virtual machine. This is an emulation of a fully (or almost completely) working operating system, which runs on your operating system. I tried VirtualBox, VMware Workstation and Hyper-V… VirtualBox is free and not as user-friendly as the other two. VMware Workstation - excellent in all respects, but paid. Hyper-V is a well-balanced virtual machine that migrated from server operating systems to Windows 8 and just needs to be turned on for access. Therefore, the choice fell on the latter: simple, free and tasteful. By the way, I have a licensed Windows 10 Professional, but I got it for free thanks to Windows program Insider (six months of suffering with bugs and a license in your pocket)).
I will probably immediately warn you that when you enable Hyper-V components, you will not be able to use other virtual machines. So, let's begin:
Right-click on the "Start" corner and select "Programs and Features".
In the left panel, select "Turn on or off Windows components»
Now open the Start menu → All Programs → look for the “Administrative Tools” directory and find “Hyper-V Manager” in it.
Running it, we will see the virtual machine management console, I already have one machine created, which hosts a music bot for my TeamSpeak server. But now we are creating another machine to show how this is done. But first, let's immediately create a "Virtual Network" so that our VM has the Internet. To do this, click on the computer name in the left column, and in the right column select "Virtual Switch Manager".
I add this paragraph two months after writing the article. This is because, below, I described an easier way to connect a virtual machine to the Internet, but I myself use a slightly different one. The difference between them is that in the method described here, the VM gets the main access, and the computer works after it, and this is not correct, but it is easier to configure. If you use the computer not only to run virtual machines, select "Internal" → "Create a virtual switch" and check the box "Allow identification". Internet access is configured using .
On the left, select "Create a virtual network switch", on the right "External" and click "Create a virtual switch".
Enter a name for the network, in the "External network" section, select your network adapter and click OK.
Now let's create a virtual machine. Click "Create" - "Virtual Machine".
Opens " Virtual Machine Creation Wizard“, on the first window, just click “Next”.
Specify a name for the future virtual machine. If desired, you can also change the storage location of the virtual machine, I have changed the location in the settings so as not to clog the SSD and all virtual machines are stored on one of the hard drives. Click "Next".
Everything is simple here, we read what is written, if you have motherboard without UEFI support or you are going to install a 32-bit system, then select the first item, if the conditions for using the second generation match your capabilities, select the second generation. I want to install 32bit Ubuntu, for one of the following articles, so I choose the first generation of Hyper-V. Click next.
Volume virtual memory. In the case of Windows, 2-3GB is desirable for 32-bit systems and 3-4 GB for 64-bit systems. More does not make sense for a virtual machine, and less can affect the operation of the system. You can also use "Dynamic Memory", in this case, the VM will be allocated as much memory as it needs.
Choose the volume hard drive future machine and the storage location of its file. Under needs, for Win 8-10 you need at least 25GB. I take under Ubuntu with a large margin.
When creating instructions for installation and configuration hypervisor, the hypervisor itself, installed on real hardware, was tested. I was helped to configure it and the control computer by a cmd script written by me in 2014 and accidentally discovered in the bowels of my file dump after its general cleaning.
The script has been slightly tweaked and tested again. The only thing that I could not achieve was to execute the command to restore color in the cmd console at the end of the script, which can be restored manually, in the console properties.
I got the idea for writing a script from ru.intel.com, and unfortunately, the link to that page no longer exists.
This cmd script configures in automatic mode hypervisor and host computer for remote control hyper v server 2012 using remote control tools, in particular, using hyper-v manager, on Windows 7, Windows 8 and Windows 8.1
Detailed and without "water" instructions for installing and initially configuring the hypervisor are written on this page: installing and configuring hyper - v server 2012 bare metal
We have:
Computer(hardware) with hyper - v 2012 installed and updated
Guest OS(vmware) with installed, Russian-language OS windows 7x64, windows 8x64, windows 8.1x64
The conditions are simple:
- Run the script on the control computer with administrator rights
- Firewall must be enabled on the control computer
- On the control computer must be installed with a Russian-language Windows system 7x64, Windows 8x64 or Windows 8.1x64 (didn't try it on x86 systems, but it might work on them)
- On the control computer, UAC and antivirus must be temporarily disabled so as not to block installation scripts
- Tools must be installed on the host computer remote administration servers, especially rsat hyper-v
- Both the hypervisor and the control computer must be networked
- Hypervisor and host computer must be in the same workgroup
- Newly created hypervisor and computer accounts, and passwords for them, must be the same
Even easier:
On a computer: firewall enabled + script run as admin + Russian Windows 7x64, 8x64 or 8.1x64 + disable UAC and antivirus + rsat hyper installed - v
On a computer + hypervisor: one working group work group+ same admin account Ivanov and password GUGlplay307
If you do not have remote server administration tools installed, then download them from the links below:
For Windows 7x64: https://www.microsoft.com/ru-RU/download/details.aspx?id=7887
For Windows 8x64: https://www.microsoft.com/en-us/download/details.aspx?id=28972
For Windows 8.1x64: https://www.microsoft.com/en-us/download/details.aspx?id=39296
Download the archive with the script config_server_client_hyper-v_2012.zip on the page pantry In chapter scripts and programs: script for automatic configuration of the hypervisor and control computer
Before unpacking the archive, it must be unlocked by right-clicking on it and selecting properties.
Archive content:
Windows7x64 and Windows8x64 folders for different OS versions
Each folder contains files:
- firewall_hyperv_client_rus.cmd and hvremote.wsf for configuring the control computer
Each folder contains a folder:
- shared disk containing files: firewall_hyperv_server_rus.cmd (configures the hypervisor)
hvremote.wsf (configures the hypervisor), INSTALL.CAB (contains program total commander, downloaded from offsite)
Corefig folder containing powershell scripts(hypervisor management)
First, configure the hypervisor (some examples and descriptions of settings)
If you have Windows 7x64 installed (this is also true for windows 8x64), then on the control computer:
- copy the file firewall_hyperv_client_rus.cmd from the root of the Windows7x64 folder to the desktop
- to the "C" drive, copy the hvremote.wsf file from the root of the Windows7x64 folder
In case of using "balls":
- share any folder (I shared the disk)
- copy the contents of the Shared Disk folder, which is located in the Windows7x64 folder, to the "ball", except for the text file attention.txt
If using a flash drive:
- copy the firewall_hyperv_server_rus.cmd file to the USB flash drive, located in the Shared disk folder, which is located in the Windows7x64 folder
the rest, except for the files attention.txt and firewall_hyperv_server_rus.cmd, copy to the "ball"
If everything is copied to the "ball", then in command line hypervisor we write (specify your data):
net use R: \\192.168.1.3\E/user:controlcomputer\accountname password && cd /d R C:\ && cd /d C:\ && firewall_hyperv_server_rus.cmd Here we: connect the shared drive "E" as drive "R" &&
go to drive "R" &&
&&
go to drive "C" &&
If it so happened that you have a “ball” somewhere there, and a flash drive here, then we put it into the hypervisor and write on the hypervisor command line:
diskpart
list volume We display a list of disk volumes, among which our flash drive is located (screenshot below)
cd/d I:\ && xcopy firewall_hyperv_server_eng.cmd C:\ && cd /d C:\ && firewall_hyperv_server_eng.cmd Specify your data. Go to disk "I" (our flash drive) && copy to disk "C" of the hypervisor, the file firewall_hyperv_server_rus.cmd && go to drive "C" && run the file firewall_hyperv_server_rus.cmd
Each command is separated from the other by symbols. && , saying: "if the previous command was successful, then execute the next one" and therefore, if something went wrong, execute them one by one.
During the execution of scripts, windows will appear asking you to specify network settings hypervisor, host computer, and account details. Follow these simple instructions as it is written there.
A little about passwords account hypervisor. Its requirements are high, and you only need to specify it once ... Don't bother, just type in something similar: GUGlplayer307
After executing all the commands, the script will "ask" to restart the hypervisor, reboot.
Later to open total commander, you need to go to the directory "tc" and run the program cd c:\tc && totalcmd.exe
To run the corefig utility, change to the "corefig" directory and use script run cd c:\corefig && cscript start_corefig.wsf
or cd c:\corefig && powershell .\corefig.ps1
Now let's set up the control computer (some examples and descriptions of settings)
We run the firewall_hyperv_client_rus.cmd script as an administrator, which is located on the desktop of the control computer and follow the instructions.
In short:
Script includes hyper - v remote control tools
Temporarily activates the built-in "administrator" account (windows 8x64 and higher) to run commands on its behalf
Sets up the hosts file
Creates another script and copies it to c:\users\public
Adds a key to the registry with a link to the newly created script
Creates a new administrator account to manage the hypervisor
Validates an account by displaying information about it
Removes executed lines of code from its body and creates a new script to run later
Restarts the computer for later login with a new account
Configures "component service"
Adds the hypervisor to the list of trusted hosts to allow connections to it and tests the configuration
Adds the necessary rules to the windows firewall
Tests hypervisor access
Configures the host computer for remote control of the hypervisor
Deactivates the built-in "administrator" account (windows 8x64 and above), removes scripts from the computer and the link from the registry
In order to avoid errors, I note that after performing a reboot, do not forget to change the keyboard layout from Russian to English.
Don't forget that after reboot windows 8x64, you will need to enter a password abc in the black window that will appear on the desktop after you log in and click enter. The password is not shown when you enter it.
mmc, for Windows 7x64 OS.
The two screenshots below show the hyper - v manager connected to the hypervisor and the necessary snap-ins added to the console mmc, for Windows 8x64 OS.
That's all. Next time we set up network using the hyper - v manager, create virtual machines and connect them, install and configure the domain and other servers and services.
Not everyone knows that some editions have a built-in Huper-V hypervisor. It's just that this role is disabled by default. The following will explain how to activate a Hyper-V virtual machine in Windows 8, as well as how to create a new virtual machine in this environment.
1. What you need
- Operating system Professional / Windows 8 Pro (64-bit) or Corporate / Windows 8 Enterprise (64-bit). Other versions do not have the Hyper-V role (link).
- A computer with a processor that supports hardware virtualization technology. In addition, it is necessary to support the second level address translation technology - SLAT (Second Level Address Translation). Intel calls this technology Extended Page Tables (EPT), AMD calls it Rapid Virtualization Indexing (RVI). You can check if your processor supports these technologies on the manufacturer's website. For example, for Intel processors - see , for AMD - .
- An additional network adapter on the physical computer, if you want to provide the virtual machine with network access.
2. Enabling virtualization support in the computer's BIOS
First of all, you need to enable virtualization support. To do this, go to the BIOS of a physical computer and find the corresponding item. IN different versions bios, it can be called differently. For example, on an HP Pavilion g6 laptop, this item is Virtualization Technology tab System Configuration.
3. Activate the Hyper-V role
Launch the Control Panel, go to the tab " Programs" , then press " Turn Windows features on or off» .
In the window that opens, select all the components in the " Hyper-V» and press « OK» .
After installing the role, the system will require a reboot. We restart the computer, and we see that shortcuts for launching have appeared in the Metro interface Hyper-V Manager And Connections to a Hyper-V virtual machine.
These labels are also available in
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Hyper-V Management Tools\
4. Create a virtual switch
Now that the Hyper-V hypervisor is installed, let's create a virtual switch to connect virtual machines to the network. To do this, launch the Hyper-V Manager and in the menu " Actions» choose « Virtual Switch Manager...» .
In the launched dispatcher, click on " Create a virtual network switch” and get into the window where you need to select the type of future virtual network. There are 3 options:
- External- Select if you want to give the virtual machine access to the network to which the current computer is connected. In this case, this computer should be free LAN card, which we will rename for the virtual machine.
- Internal— To create a network between all virtual machines and the current computer. The physical network in this case will be inaccessible to virtual machines.
- Private- In this case, a network is created between all available virtual machines. The current computer, as well as the physical network, will be unavailable.
After selecting the type of future network, click " Create virtual switch» .
The properties window for the virtual switch opens. Here you must specify the name of the switch, and you can also set additional parameters. For example, my computer has 2 network cards: for a wired connection via an RJ-45 connector and wifi adapter. The last one I override for the current switch. Thus, my future virtual machine will go online through this Wi-Fi adapter.
Well, in the network connections you can see that now this Wi-Fi network card is connected to the virtual switch that appeared there.
5. Create a virtual machine
Finally, you can go directly to the creation of the virtual machine itself. To do this, in the Hyper-V Manager in the menu " Actions» choose « Create» — « Virtual machine…» .
The Virtual Machine Creation Wizard will start. Here we set the name of the created virtual machine, and also select the directory for its storage. Make sure you have enough free space on the selected hard drive. Since in the case of using snapshots, the virtual machine as a whole can have a fairly significant amount. After specifying the required parameters, click " Further» .
Then set the volume random access memory, which will be used by the virtual machine during operation, and click " Further» .
Now you need to specify a virtual switch to connect the virtual machine to the network. Select the connection created in step 2 and click " Further» .
At this step, you need to create and connect a virtual HDD, for this virtual machine, or specify an existing virtual hard disk. In the case of creating a new one, enter the name of the hard disk, location and size (remembering that when using snapshots, the volume of the virtual machine as a whole can be significantly increased), then click again " Further» .
Now let's select the device from which the operating system will be installed in the created virtual machine. Possible options:
- Do not install an operating system.
- Use the DVD drive of a physical computer.
- Use a disk image file from a physical computer.
- Use virtual disk.
- Network installation.
Check everything again set parameters and complete the creation of the virtual machine by clicking " Ready» .
After successful installation, the newly created virtual machine should appear in the Hyper-V Manager in the list of virtual machines, with the status " Off» . In order to connect to it, right-click on this line and in context menu choose " To plug…» .
After that, a connection to this virtual machine will be made. In order to launch it, click on the button " Start' in the upper left corner of the window.
The virtual machine will start, and we will observe this process in the connection window, as if we were behind physical computer. If the source for installing the operating system is selected, then, accordingly, the this installation. Further management of the virtual machine is also performed using the menu at the top of the connection window.
Did this article help you?
Back in Windows 8, Hyper-V virtualization technology appeared, previously available only in Microsoft server operating systems. This solution looks better than the virtual one that came with Windows 7. windows machine Virtual PC. Today I will tell you how in Windows with using Hyper-V create a virtual machine, as well as configure the Internet, local network and file sharing in it.
In addition to Coreinfo, you can use Intel's proprietary utility (AMD has a similar one).
You can also check the virtualization technology support matrix on your processor manufacturer's website: Intel | AMD.
Enabling the Hyper-V Feature
Hyper-V is an operating system component that is initially disabled. Advanced users can enable it with a single PowerShell command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
If you prefer a graphical interface, press Win + R , type OptionalFeatures and press Enter .
In the window that opens, check the Hyper-V box.
One way or another, the component will become available after the system is rebooted. Of the installation problems in Windows 8 RP, it has been noticed so far cyclic reboot through the fault of the USB 3.0 controller drivers, which on some systems was solved disabling USB 3.0 in BIOS.
Create and configure a virtual machine
Press Win + R , type virtmgmt.msc and press Enter to open Hyper-V Manager. From the menu Actions select Create – Virtual machine.
The wizard for creating a virtual machine is extremely simple, however, I will note some points for those who like detailed instructions with pictures. I will skip the network setup step for now, as I will analyze this issue in more detail.
The default location for virtual machines is a folder ProgramData, but it can be changed.
If you already have a virtual disk in VHD format, you can mount it. By the way, I did just that, using the disk created earlier for Virtual Box.
When you specify an existing VHD, the wizard skips the step that specifies the installation media.
However, you can also specify the path to the ISO later by opening the virtual machine settings in the main Hyper-V Manager window.
Starting a virtual machine and installing Windows on it
Here, too, everything is simple, but a little unusual for those who have not previously encountered Hyper-V.
In Hyper-V Manager:
- to start the virtual machine, click "Start"
- to interact with it, click "Connect" or double-click the thumbnail of the car
When the bootable Windows ISO image is specified in the machine parameters, you will see the familiar Press any key to boot on the screen ... Then you can handle it yourself, but if you need step by step instructions by installation, they are on OSZone for Windows 7 and Windows 8.
If the operating system on the physical machine is newer than the one installed on the virtual one, it is recommended to update the integration components (thanks, Artem). To do this, connect in the Hyper-V manager to the virtual machine, press Ctrl + I and run setup.exe.
Setting up Internet access and local network
The instructions in this section are only necessary if you are not satisfied with the Default Switch that was introduced in Windows 10 1709, which cannot be deleted or renamed. When using the Default Switch, if the host is connected to the VPN, the virtual machine also uses the VPN. This is one of the main differences from the external switch, the creation of which I will describe next.
On the menu Actions select Configuring Virtual Switches. A window will open in which you can create a switch of one of three types. To enable your virtual machine to access the Internet, create external switch.
Now you need to set the name of the switch and select the network adapter if you have more than one. At home I use wireless network, so I chose the Wi-Fi adapter.
It remains only to specify the created switch in the parameters network connection virtual machine.
Now in installed Windows you will have an internet connection and the local network between physical and virtual machines.
In the picture above you see:
- on the left is the result of adding a virtual switch to Hyper-V on a physical machine, i.e. network bridge and virtual adapter
- on the right - Internet access and LAN connection on a virtual machine
As you can see, setting up the Internet and local network is not so much complicated as it is unusual for users of Microsoft client operating systems.
Sharing files between physical and virtual machines
In the course of working with a virtual machine, it regularly becomes necessary to copy files to it from a physical one, or vice versa. I will describe several ways to solve this problem.
Shared network folders
This method works in all editions of Windows 10. Since we have a local network at our disposal, we can use shared folders to share files. In fact, the instructions below boil down to the basics of creating shared folders.
Access from virtual machine to physical
A picture is worth a thousand words, as the Americans say.
The figure shows the virtual machine explorer (VIRTUAL-PC) from where the physical machine (VADIK-PC) is accessed. As soon as you enter the account credentials, access to his profile will be at your disposal.
You may want to share a folder located on a physical machine outside of your profile. To do this, it is enough to use standard means sharing, but I will explain this process using the example of accessing an arbitrary folder of a virtual machine.
Access from a physical machine to a virtual one
Let's say there is a folder in the root of the virtual machine's disk shared. Right click on it and select General access – individual people(or Specific Users in Windows 7).
Now you can open shared folder over the network in Explorer, including by entering an address of the form \\computername\foldername.
Remote Desktop Connection of a Virtual Work Machine
In Hyper-V, files cannot be exchanged between a physical machine and a virtual machine by copy and paste. You can only paste the text copied on the physical machine with the combination Ctrl keys+ V . However, once the virtual machine has started, you can connect to it via RDP instead of opening it from Hyper-V Manager. This method works in Pro editions and above.
Actions on the virtual machine
First you need to allow remote desktop connections on the virtual machine in the system properties. Press Win + R and run:
RUNDLL32.EXE shell32.dll,Control_RunDLL sysdm.cpl,5
Then allow the connection as shown in the picture.
It remains only to find out the IP address of the virtual machine with the command ipconfig
Actions on the physical machine
Press Win + R and type mstsc and expand login options.
In the window that opens:
- Enter the IP address of the virtual machine (required).
- Specify the name of the user whose account will be logged into.
- Turn on remember credentials.
- Save your connection settings.
You can also set the Display tab to a resolution lower than what is used on the physical machine.
Now you can share files between physical and virtual machines with the familiar keyboard shortcuts Ctrl + C and Ctrl + V .
Finally, I would like to virtualize some of Denis Diaghilev's recommendations for working with Hyper-V.
Use RDP to connect to virtual machines.
This will not only allow you to share files between a physical and virtual machine by copying and pasting, but will also save system resources that vmconnect consumes when connecting to a virtual machine in Hyper-V Manager or from the command line.
If you plan to regularly use RDP to connect to various virtual machines, pin the program to the taskbar. Then the list of machines will be stored in the jump list.
Be careful with pictures
With Hyper-V, you can take snapshots of a virtual machine using differential disk technology. However, the logic of how the images work is practically the opposite of what a person who has never stepped on a rake expects from her.
Alexander Kosivchenko (Virtualization MVP) described in detail, albeit somewhat chaotically, the principle of Hyper-V snapshots on Habré.
Use virtual machine import if needed
Import will be of more interest to IT professionals, but I happened to use this feature by accident. After creating the virtual machine, I renamed the drive letter where it was stored, after which the Hyper-V Manager lost it.
Looking around in the snap, I saw the import option and instantly restored the machine.
And I didn’t even suspect that the actions I performed became possible only due to the appearance of a new feature in Hyper-V :)
Hyper-V vs. virtual box
Dealing with Hyper-V, I involuntarily compared Microsoft solution for client operating system with Oracle VirtualBox.
From the point of view of typical tasks of home users (testing the installation of the system, getting acquainted with it, checking the operation of applications), these solutions practically do not differ from each other. But VirtualBox can be used on home editions of Windows 10, while Hyper-V is not available on them.
VirtualBox does not have such stringent hardware requirements, and its graphics capabilities even wider, since there is support for 3D hardware acceleration (although I never used it).
Concerning GUI Well, it's purely a matter of taste. Probably, the hypervisor that came from the server OS looks more ascetic, but the parameters and settings of virtual machines are generally very similar.
The presence of Hyper-V in Windows will primarily please IT professionals who are accustomed to this technology. For home users, this is good opportunity take advantage of the system's built-in tools and expand your horizons by joining Microsoft server technologies.
Survey
I was introduced to virtual machines in 2004 when I started autoinstalling Windows. Since then, they have become an integral part of my daily work, including testing system settings, programs, etc.
In comments tell us what virtualization solution you use and for what purpose!
I want to thank Denis Diaghilev for his help in preparing this material. One of the benefits of an MVP program is familiarity with the best specialists by Microsoft technologies. This means that in private you can get competent advice on any issue;)
Denis also kindly offered his help in leading the discussion. So if you have any technical questions about this article, you can count on qualified answers.
I want to specifically emphasize that
