Hyper-V on Windows: a guide to creating and configuring virtual machines. How to manage Microsoft Hyper-V from the command line Installing the hyperv hypervisor windows 8
Hello friends, in today’s article we will connect a Hyper-V virtual machine to our Windows 8 and install the Windows 7 and Windows 8 operating systems on it, and also answer all the questions asked by users. By the way, you can transfer your entire physical computer to Hyper-V! Several system administrators I know work only on Hyper-V and have even forgotten what a normal operating system is. At the very beginning we publish several of your letters.
Installing Hyper-V
If you have Windows 8 Pro or Windows 8 Enterprise (corporate) installed on your computer, then you can use the Hyper-V virtualization system or, in simple words, use the virtual machine built into the Windows 8 operating system. It is very easy to use and I have no doubt that you will understand it.
For Hyper-V to work, your processor must support virtualization technology. Before work, be sure to enable the following options in the computer BIOS:
"Intel Virtualization Technology" for Intel processors or "AMD Virtualization" for AMD processors.
I warn you that Hyper-V is primarily designed and intended for IT professionals and is used on servers.
When working in Hyper-V, you will not be able to use a flash drive, sound card, and WiFi, in this regard it is preferable to use VirtualBox. But I still think that those who read this article know why they need it.
For its operation, the Hyper-V virtual machine makes small requirements:
Windows 8 Pro must be 64 bit.
Availability random access memory at least 4GB.
Hyper-V connection
Opening Control Panel
and choose Programs
Programs and components. Turn Windows features on or off
Find the Hyper-V partition and mark it with a checkmark and click OK.
There will be a short search for the required files and a reboot.
After the reboot, go to the Metro interface and left-click on the arrow, then select Hyper-V Manager,
The Hyper-V Setup Wizard appears. Click on the name of our computer, then Create And Virtual machine.
Hyper-V Settings
1) Getting started. This master will help you create a virtual machine, click Next.
2) Specify a location. We assign a name to the virtual machine in Latin, for example Windows 7. We indicate the location of the files of the Hyper-V virtual machine, since I don’t have space on drive C:, I will check the Save virtual machine in another location checkbox and click browse, then specify the drive D: and Next.
3) Specify the generation. I want to install Windows 7 so I will select Generation 1.
4) Allocate memory. My computer has 8GB of RAM, which means I can safely allocate 2GB of RAM for a virtual machine. Check the box “Use dynamic memory for this virtual machine” and Next.
5) Network setup. We skip this parameter (we’ll set up an Internet connection later) and click Next.
6) Connect virtual HDD. Mark the item Create a virtual hard disk. So in the second paragraph Specify location, we indicated the location of the virtual machine files on the D: drive, then by default the virtual machine will offer us to locate the virtual hard disk on the D:\Windows 7\Virtual Hard Disks\ drive.
Friends, the item Size 127 GB does not mean that 127 GB will immediately be “squeezed out” on your D: drive.
Note: A virtual hard disk can be created at the very beginning, that is, before you create a virtual machine, and in this case you can choose which virtual hard disk to create, for example:
Dynamic(grows in volume gradually, according to accumulated data, at first it takes up several megabytes).
Fixed size(immediately requires allocation for the required space; if you create a 120 GB disk, that means you must allocate exactly that much space to it).A fixed-size hard drive is considered to have higher performance.
More detailed information see the end of the article.
7) Installation parameters. Check the box Install the operating system later. Further.
8) Done
How to set up Internet in Hyper-V
Now let's set up the network. In the main Hyper-V window, click on the Virtual Switch Manager button.
In the window that appears, select what type of virtual switch you want to create. I will select the type - External network. WITH create a virtual switch.
Choose an arbitrary name for the virtual switch. Network wifi adapter on my computer from the manufacturer "Atheros", so I will choose this name. Apply.
Choose Options
A window will open, on the left side of which you can see two sections with different parameters; if you select the parameter you need with the left mouse, then on the right side of the window you can configure it.
Network adapter. In the right part of the window, select our Virtual Switch "Atheros", Apply And OK.
Installation on Hyper-V operating system
Now the actual question is how to install the operating system in a virtual machine. To install a Hyper-V virtual machine, you need to boot it from installation disk Windows 7 located in the drive or for these purposes you need to use an ISO image with Windows.
, then on the right side of the window using the buttons Up And Down We set the virtual machine boot to what we need:CD- boot from the installation disk or ISO image.
Choose Controller 1 IDE and click on the plus sign, then DVD drive if you want to boot the virtual machine from DVD drive Check the box Physical CD and DVD drive: then insert the Windows 7 installation disk into the drive.
Also, to boot a virtual machine and install an ISO image with Windows 7, you can use Windows 7, in this case you need to check the File image item and click the Browse button, in the explorer that opens you need to select the image with Windows 7 and click Open. Apply and OK.
Click Start and the virtual machine starts. Hyper-V is loading from the Windows 7 ISO image. Double-click with the left mouse on the thumbnail of the Hyper-V virtual machine window,
A window will open in which you and I will work. Press any key, otherwise boot from installation Windows disk 7 won't happen. At the top of the window there are virtual machine settings buttons.
The usual Windows 7 installer dialog box. Next, you can install the Windows 7 operating system on the virtual machine. The whole process is described in detail in our article.
So you and I connected a Hyper-V virtual machine to our operating system and installed Windows 8 on it, the Internet is present on the virtual machine. You can install Windows 8 on it in exactly the same way.
How to create a virtual hard disk in Hyper-V
Friends, a virtual hard disk in Hyper-V can be created not only during the process of creating a virtual machine.
In the main window of the virtual machine, select Create -> HDD
Selecting the disc format. You can choose a new format hard drive, but please note that it is not supported by earlier operating systems before Windows 8
Select the disk type. You can create a fixed partition disk, which is considered higher performance
We indicate the location of the virtual hard disk if you have little free space on the C: drive, then place the virtual hard disk on the D: drive. Click on the Browse button and select drive D:
Disk setup. If we create not a dynamic expandable virtual disk, but a virtual disk of a fixed partition, then we must specify the exact size of the disk; if we specify the size of 127 GB, then this is exactly how much our virtual disk will occupy on the D: drive. Make sure you have enough free space on your D: drive.
note per parameter Copy the contents of the specified physical disk, you can use it if you want to transfer your physical computer along with all the settings to a virtual machine!
The virtual hard disk has been created. When creating a new virtual machine in step Connect a virtual hard disk we can check the box Use an existing virtual hard disk, then click Browse and specify the location of the virtual disk -D:\New virtual hard disk.vhdx
Blue screen when creatingvirtual switch V Hyper-V
Friends, several times I had to deal with the fact that in the new operating system Windows 8.1 in virtual Hyper-V machine, when creating a virtual switch, the operating system went into blue screen with error:
The problem seems to be caused by the following file: fwpkclnt.sys UNEXPECTED_KERNEL_MODE_TRAP *** STOP: 0x0000007f.
I tried to solve the problem different ways: reinstalling the virtual machine, restoring system files, removing the antivirus and firewall, updating drivers for all computer components, including network card. Unfortunately, only changing the network adapter helped.
Some time ago we wrote about autorun virtual machines VMware vSphere and Citrix XenServer, but Microsoft Hyper-V administrators also face this problem. Just like on the vSphere platform, Hyper-V has settings to control the behavior of virtual machines when the host server is turned on and off.
So, if you open the virtual machine settings in Hyper-V, you will see an item like Automatic Start Action, where the settings for the behavior of the VM when the host starts are actually set:
There are three options for how the machine behaves when starting the Hyper-V host:
- Nothing - By default, the virtual machine does not start when the host server starts.
- Automatically Start If It Was Running When The Service Stopped - This option is useful when testing various applications in the VM (which, for example, can reboot the host) and the presence of machines that do not always turn on, but as needed. If you select this item, the virtual machine will be launched only if it was running when the host was shut down or rebooted.
- Start This Virtual Machine Automatically - This option is best used for productive virtual machines. It will allow you to start the virtual machine when the host starts in any case. There is also an option to delay before starting the VM, which will allow you to configure the order in which dependent services are launched (for example, the controller Active Directory launch without delay, then the base Microsoft SQL, and after a while we launch the application server and web server). In addition, this option will prevent all machines from creating a load on the storage subsystem at the same time, distributing it over time.
In addition to autostart of virtual machines, you can also configure Automatic Stop Action- action performed when the Hyper-V host server is shut down. This is also in the properties of the virtual machine:
There are also 3 behavior options here:
- Save The Virtual Machine State- this option allows you to minimize the downtime of the virtual machine in the event of a host shutdown. If a scheduled shutdown occurs, the virtual machine's memory will be saved to disk, after which the machine will be suspended. When you turn on the virtual machine, its memory will be restored, and it will continue to function as if nothing had happened (though not in all cases). This saves the time required to load and initialize guest OS services. However, if the amount of RAM required by a VM is large, the time it takes to unload it to and from disk can also take a significant amount of time. This option is enabled by default.
- Turn Off The Virtual Machine- this option will “hard” shut down the virtual machine (analogous to a sudden power outage). In this case, nothing will be saved, plus there are no guarantees of data consistency inside the VM (and as a result, there are no guarantees that it will load at all). But this happens the fastest, so it is convenient when using a test environment, where data safety is not so important, and everything needs to be done quickly. In addition, such a shutdown is guaranteed to occur, unlike the next or previous points.
- Shutdown The Guest Operating System- in this case, a graceful shutdown procedure is initiated in the guest OS. The system state will also not be saved, but most likely the system state will be consistent, since read-write operations will be completed correctly. If this option is used, then you need to configure the boot order of systems accordingly in the previous paragraph (autostart), since it takes time to initialize the OS and services when starting virtual machines.
Here we must not forget that if you have selected the “Save The Virtual Machine State” option, then you will need significant disk space for the .BIN files in which the virtual machine memory is located (the sum of the VM memory with this setting).
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 that I wrote in 2014 and was accidentally discovered in the depths of my file dump after its general cleaning.
The script was slightly tweaked and tested again. The only thing I couldn't achieve was the command to restore color in 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 on the website ru.intel.com and, unfortunately, the link to that page no longer exists.
This cmd script configures in automatic mode hypervisor and control 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 straightforward instructions for installing and initially configuring the hypervisor are written on this page: installation and configuration of hyper - v server 2012 bare metal
We have:
Computer(hardware) with installed and updated hyper-v 2012
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
- The firewall must be enabled on the management computer
- The control computer must have Russian language installed Windows system 7x64, Windows 8x64 or Windows 8.1x64 (I haven’t tried it on x86 systems, but it might work on them)
- UAC and antivirus must be temporarily disabled on the control computer so as not to block installation scripts
- Remote server administration tools must be installed on the control computer, in particular rsat hyper-v
- The network must be running on the hypervisor and the control computer
- The hypervisor and the control computer must be in the same workgroup
- Newly created hypervisor and computer accounts, and passwords for them, must be the same
Even simpler:
On the computer: firewall enabled + script running as admin + Russian Windows 7x64, 8x64 or 8.1x64 + disable UAC and antivirus + installed rsat hyper - v
On a computer + hypervisor: one working group workgroup+ the same admin account Ivanov and password GUGlplay307
If you do not have remote server administration tools installed, 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/ru-ru/download/details.aspx?id=28972
For Windows 8.1x64: https://www.microsoft.com/ru-ru/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, you must unlock it by right-clicking on it and selecting properties.
Archive contents:
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 the total commander program, downloaded from the offsite)
Corefig folder containing powershell scripts (hypervisor management)
First, let's 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 your desktop
- to drive "C", copy the file hvremote.wsf 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, into the “share”, except 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, is copied to the “share”
If everything is copied to the “share”, then on the command line of the hypervisor we write (indicate your data):
net use R: \\192.168.1.3\E/user:control_computer\account_name 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 happens that you have the “share” somewhere there, and the flash drive is here, then we stick it into the hypervisor and write in the command line of the hypervisor:
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_rus.cmd C:\ && cd /d C:\ && firewall_hyperv_server_rus.cmd Enter your details. Go to disk "I" (our flash drive) && copy the file firewall_hyperv_server_rus.cmd to drive “C” of the hypervisor && 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 completed successfully, then execute the next one” and therefore, if something went wrong, execute them one by one.
During script execution, windows will appear asking you to specify network settings hypervisor, control computer and account details. Follow these simple instructions exactly as they are written.
A little about passwords account hypervisor. Its requirements are high, and you only need to specify it once... Don’t bother, just enter something similar: GUGLplayer307
After executing all the commands, the script will “ask” to restart the hypervisor, so reboot.
In the future, to open total commander, you need to go to the "tc" directory and run the program cd c:\tc && totalcmd.exe
To run the corefig utility, you need to go to the "corefig" directory and use cscript run the utility cd c:\corefig && cscript start_corefig.wsf
or cd c:\corefig && powershell .\corefig.ps1
Now let's configure 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.
Briefly:
The script includes hyper-v remote control tools
Temporarily activates the built-in "administrator" account (Windows 8x64 and higher) to run commands as it
Configures the hosts file
Creates another script and copies it to the path 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
Verifies an account by displaying information about it
Removes executed lines of code from its body and creates a new script to run later
Reboots the computer for subsequent login with a new account
Configures the "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 access to the hypervisor
Configures the management computer for remote management of the hypervisor
Deactivates the built-in "administrator" account (Windows 8x64 and higher), removes scripts from the computer and a link from the registry
In order to avoid errors, I note that after rebooting, do not forget to change the keyboard layout from Russian to English.
Don't forget that after reboot windows 8x64, you will need to provide a password abc in the black window that appears on the desktop after you log in and click enter. The password is not displayed 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 let's set it up network using the hyper-v manager, create virtual machines and connect them, install and configure the domain and other servers and services.
Don't install the Russian version! Not for any price. I struggled with it for a week, couldn’t understand why updates weren’t installed using the local console, why firewall rules weren’t applied, why... The list is long. Having spat 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, configure the network (step 8) and install updates (steps 5 and 6). If everything went well, then you can move on. If not, check what and how. Ghost possible problems At this stage it is impossible for you to install 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 in any conditions - starting from very low-budget solutions, limited only by the cost of the equipment, in the case of my stand in the region of 20 thousand rubles. But this imposes certain configuration features. Specifically, we must configure the firewall and add a general user.
Add a local administrator (item 3 of the server configuration, for example "hyperadmin / hyperpwd") to avoid using the default administrator). The same user (maybe not the 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 to manage the server firewall. This will save a lot of time because... I don't plan to regularly edit the rules - the server should just work. And I don’t want to keep PowerShell and CMD syntax in my head; Linux is enough for me. So I'll turn it on remote access to the firewall! Considering that the server needs to be managed properly through a dedicated network (physically, VLAN), my option will not reduce overall security. Alternatively, you can install a software and hardware firewall between the host and the network, for example, Mikrotik (without WiFi, of course). This is completely inexpensive solution with acceptable performance and reliability.
You can enable the ability to remotely manage the firewall by running the console command (after all, you can’t do without a console):
netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
After this, you can launch the mmc console on the workstation with “hyperadmin” rights and add the “Windows Firewall” snap-in (in my Windows 7 it is called “Windows Firewall with Advanced Security”) and specify the IP address of our Hyper-V server. All:)
But no matter what, the console is the most reliable means of control. I still do everything in the console, and 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, launch virtual machines, connect to them - i.e. almost everything to start with.
Launch Hyper-V Manager as the user “hyperadmin” and click “Connect to server” at the top left. Again via IP.
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, but 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, the ability to convert VHD disks to VHDX appeared, the same migration buttons that I mentioned just above. Well, great, of course, but if you decide on the terminology and know what you exactly want, then you can get by with PowerShell and good old 7 (not long ago they also talked about “good old XP”).
To make Hyper-V Manager from Windows 8 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:
cscript hvremote.wsf /show /target:name_or_ip_of_your_hyper-v_server
Don't worry about the fact that it's 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).
A lyrical digression to move on to the next section. We’re connected, we’re happy, we’re starting to install the guest virtual machine... Stop! How to choose space 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 have the opportunity to place guest systems only on the C:\ drive. And the disk is 60 GB in total. Those. all you need to do is open the manager hard drives, format to NTFS and reassign drive letters(DVD will be E:\, 500 GB disk will be D:\ - I hate it when DVDs hang between disks :)). HOW TO DO IT???
Remote disk management
To remotely manage disks (Disk Management), you must complete the following steps:
1. Start the Virtual Disk Service (VDS) on the server
View a list of services that begin with "R" using PowerShell:
Get-Service -Name r*
Starting the VDS (Virtual Disk Services) service:
If necessary, enable “Remote Volume Management” on the client computer (from which we will manage our server).
If we had not completely disabled the firewall, then we would have to follow step 2.
2.Allow Disk Management.
Netsh advfirewall firewall set rule group=“Remote Volume Management” new enable=yes
You need to launch the MMC snap-in management console as the local administrator user on our server (in our case, “hyperadmin / hyperpwd”):
In the snap-in, 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".
Back in Windows 8, Hyper-V virtualization technology appeared, previously available only in Microsoft server operating systems. This solution looks better than the Windows Virtual PC virtual machine included in Windows 7. Today I will tell you how to create a virtual machine in Windows using Hyper-V, and also set up 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 look at the virtualization technology support table on your processor manufacturer's website: Intel | AMD.
Enable Hyper-V
Hyper-V is an operating system component that is initially disabled. Advanced users can enable it with one PowerShell command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
If you prefer a GUI, press Win + R, enter OptionalFeatures and press Enter.
In the window that opens, select the Hyper-V checkbox.
One way or another, the component will become available after a system reboot. Among the problems with installation in Windows 8 RP, a cyclic reboot due to the fault of the drivers has been noticed so far USB controller 3.0, which on some systems was solved by disabling USB 3.0 in the BIOS.
Creating and configuring a virtual machine
Press Win + R, enter virtmgmt.msc and press Enter to open Hyper-V Manager. From the menu Actions select Create – Virtual machine.
The virtual machine creation wizard is extremely simple, but I will note some points for those who like detailed instructions with pictures. I will skip the network setup step now, since I will analyze this issue in more detail.
The standard 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 connect it. By the way, I did just that, using the disk I created earlier for Virtual Box.
When you specify an existing VHD, the wizard removes the step where you specify the media for installing the system.
However, you can 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
Everything here is also 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 machine’s thumbnail
When the Windows bootable ISO image is specified in the machine parameters, you will see the familiar Press any key to boot message on the screen... Then you can handle it yourself, but if you need step by step instructions for 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 to the virtual machine in the Hyper-V manager, 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 unhappy with the Default Switch introduced in Windows 10 1709, which cannot be removed or renamed. When using Default Switch, if the host is connected to a VPN, the virtual machine also uses the VPN. This is one of the main differences from an external switch, the creation of which I will describe later.
On the menu Actions select Setting up 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 a Wi-Fi adapter.
All that remains is to indicate 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 connection to the local network on the 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
As you work with a virtual machine, you regularly need to copy files from a physical one to it, 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 machine
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. Once you enter your account credentials, access to your profile will be at your disposal.
You may want to create a shared folder located on a physical machine outside of your profile. To do this, it is enough to use standard means providing shared access, but I will explain this process using the example of access to an arbitrary folder of a virtual machine.
Access from physical machine to virtual machine
Let's say there is a folder in the root of the virtual machine disk Shared. Right click on it and select General access – Individual people(or Specific users in Windows 7).
Now you can open a shared folder over the network in Explorer, including by entering the address of the form in the address bar \\computer-name\folder-name.
Connecting to a remote desktop of a virtual work machine
In Hyper-V, files cannot be exchanged between a physical and virtual machine by copying and pasting. You can only paste text copied on a physical machine using the keyboard shortcut Ctrl + V. However, once the virtual machine is running, you can connect to it via RDP instead of opening it from Hyper-V Manager. This method works in Pro editions and higher.
Actions on a virtual machine
First, you need to enable 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.
All that remains is to find out the IP address of the virtual machine with the command ipconfig
Actions on a physical machine
Press Win + R and enter mstsc and expand login options.
In the window that opens:
- Enter the IP address of the virtual machine (required).
- Enter the name of the user whose account you will be signing in to.
- Enable login credentials to be remembered.
- Save the connection settings.
You can also set the Display tab to a resolution lower than what is used on the physical machine.
Now you can exchange files between physical and virtual machines using the usual keyboard shortcuts Ctrl + C and Ctrl + V.
Finally, I would like to virtualize a few recommendations from Denis Diaghilev for working with Hyper-V.
Use RDP to connect to virtual machines.
This will not only allow you to share files between the physical and virtual machine by copying and pasting, but will also save system resources that vmconnect consumes when connecting to the virtual machine in Hyper-V Manager or from 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 cars will be saved in the transition list.
Be careful with your photos
With Hyper-V you can create snapshots of a virtual machine using differential disk technology. However, the logic of the images is almost the opposite of what a person who has never stepped on a rake would expect from it.
Alexander Kosivchenko (MVP for virtualization) described in detail, although somewhat chaotically, the principle of operation of Hyper-V snapshots on Habré.
Use virtual machine import if necessary
Import will be more interesting to IT specialists, but I happened to use this function by accident. After creating the virtual machine, I renamed the drive letter where it was stored, and then Hyper-V Manager lost it.
Looking around in the snap, I saw the import option and instantly restored the machine.
Moreover, I didn’t even suspect that the actions I performed became possible only due to the emergence of a new feature in Hyper-V :)
Hyper-V vs. VirtualBox
While understanding Hyper-V, I involuntarily compared Microsoft solution for a client operating system with Oracle VirtualBox.
From the point of view of typical tasks of home users (testing the system installation, familiarization with it, checking the operation of applications), these solutions are practically no different from each other. But VirtualBox can be used in Windows 10 Home editions, while Hyper-V is not available in them.
VirtualBox does not have such strict hardware requirements, and its graphics capabilities are even greater, since it supports 3D hardware acceleration (though I have never used it).
Concerning GUI, then this is purely a matter of taste. Probably, the hypervisor that came from server operating systems looks more ascetic, but the parameters and configuration of virtual machines are generally very similar.
The presence of Hyper-V in Windows will primarily please IT professionals accustomed to this technology. For home users, this is a good opportunity to take advantage of the system’s built-in tools and expand their horizons by becoming familiar with Microsoft server technologies.
Survey
I became acquainted with virtual machines in 2004, when I started doing Windows Auto Install. 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 would like to thank Denis Diaghilev for his assistance in preparing this material. One of the benefits of the MVP program is exposure to top Microsoft technology talent. This means that you can get competent advice on any issue privately;)
Denis also kindly offered his assistance in facilitating the discussion. Therefore, if you have any technical questions regarding this article, you can count on qualified answers.
I want to specifically emphasize that
