Back in Windows 8, the Hyper-V virtualization technology appeared, previously available only in Microsoft server operating systems. This solution looks better than the Windows Virtual PC that was included with Windows 7. Today I will tell you how to create a virtual machine in Windows using Hyper-V, as well as configure the Internet, local network and file sharing in it.
In addition to Coreinfo, you can use a proprietary Intel utility (AMD has a similar one).
You can also look at the virtualization technology support table on your processor manufacturer's website: Intel | AMD.
Enabling the Hyper-V component
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 a system reboot. Among the problems with the installation in Windows 8 RP, a cyclic reboot was noticed so far due to the fault of the USB 3.0 controller drivers, 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 choose Create – Virtual machine.
The wizard for creating a virtual machine is extremely simple, but I will note some points for those who like detailed instructions with pictures. I will skip the network configuration step now, since I will analyze this issue in more detail.
The default location for virtual machines is 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 disc I created earlier for the Virtual Box.
When you specify an existing VHD, the wizard will skip the step that specifies the media for installing the system.
However, you can specify the ISO path later by opening the virtual machine settings in the main Hyper-V Manager window.
Launching 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 machine
When the Windows bootable ISO image is specified in the machine parameters, you will see the familiar Press any key to boot ... On the screen, you can do it yourself, but if you need step-by-step installation instructions, they are available 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 machine, 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 not satisfied with the Default Switch that appeared in Windows 10 1709, which cannot be deleted or renamed. When using the Default Switch, when the host connects to 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 choose 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. I use a wireless network at home, so I chose a Wi-Fi adapter.
It remains only to specify the created switch in the parameters of the virtual machine's network connection.
Now, with Windows installed, you will have an Internet connection and a local network between the physical and virtual machines.
In the picture above, you can see:
- on the left - 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 a local network in a virtual machine
As you can see, setting up the Internet and local network is not so much difficult 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 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 area network, we can use shared folders to exchange 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 explorer of the virtual machine (VIRTUAL-PC), from where the physical machine (VADIK-PC) is accessed. Once you enter your account credentials, you will have access to its profile.
You might want to make a shared folder located on a physical machine outside of your profile. To do this, it is enough to use standard sharing tools, but I will explain this process using the example of accessing an arbitrary folder of a virtual machine.
Access from physical machine to virtual
Let's say there is a folder at 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 an address in the address bar like \\ ComputerName \ FolderName.
Remote Desktop Connection of a Virtual Work Machine
In Hyper-V, copy-and-paste file sharing is not possible between a physical machine and a virtual machine. You can only paste the text copied on the physical machine using the Ctrl + V keyboard shortcut. However, once the virtual machine has started, you can connect to it using RDP instead of opening it from Hyper-V Manager. This method works in Pro and higher editions.
Actions on the 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 enable the connection as shown in the figure.
It remains only 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 the 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 in.
- Turn on remembering credentials.
- Save the connection parameters.
You can also set on the Display tab a resolution lower than that used by 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 of Denis Diaghilev's recommendations for working with Hyper-V.
Use RDP to connect to virtual machines.
This will not only allow you to exchange files between the physical and virtual machine by copy and paste, but 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 cars will be saved 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 the snapshots is practically the opposite of what a person expects from it, who has never stepped on a rake.
Alexander Kosivchenko (MVP for virtualization) in detail, albeit somewhat chaotic, described the principle of operation of Hyper-V snapshots on Habré.
Use virtual machine import if needed
The import will be more interesting for IT professionals, but I happened to use this function by accident. After creating the virtual machine, I renamed the drive letter on which it was stored, after which the Hyper-V manager lost it.
Looking around in the snap, I saw the import option and instantly rebuilt the machine.
Moreover, I did not even suspect that the actions I performed became possible only due to the appearance of a new feature in Hyper-V :)
Hyper-V vs. Virtualbox
As I dealt with Hyper-V, I involuntarily compared Microsoft's client operating system solution to Oracle VirtualBox.
From the point of view of typical tasks of home users (testing the installation of the system, getting to know it, checking the operation of applications), these solutions practically do not differ from each other. But VirtualBox can be used in Windows 10 home editions, while Hyper-V is not available there.
VirtualBox does not have such stringent hardware requirements, and its graphics capabilities are even broader, since there is support for 3D hardware acceleration (although I have never used it).
As for the graphical interface, this is 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 on Windows will primarily delight IT pros who are accustomed to this technology. For home users, this is a good opportunity to take advantage of the built-in system tools and expand their horizons by joining Microsoft server technologies.
Survey
I got acquainted with virtual machines in 2004 when I started doing Windows autoinstallation. Since then, they have become an integral part of my daily work, including testing system settings, programs, etc.
In comments tell us which virtualization solution you are using and for what purpose!
I would like to thank Denis Diaghilev for his help in preparing this material. One of the benefits of the MVP program is getting to know the best Microsoft technology experts. This means that privately you can get competent advice on any issue;)
Denis also kindly offered his help in conducting the discussion. Therefore, if you have any technical questions about this article, you can count on qualified answers.
I want to specifically emphasize that
The Microsoft Windows 8 operating system introduces Hyper-V virtualization technology, previously only available on Microsoft server operating systems.
System requirements for Hyper-V to run on Windows 8
1. OS
Hyper-V is only available on 64-bit versions of Windows 8 / 8.1. Supported editions of operating systems Windows 8 / 8.1 Professional and Enterprise.
2. CPU
- 64-bit processor made by Intel or AMD
- Support for virtualization technologies (Intel VT-x or AMD-V) and Second Level Address Translation (SLAT) technologies. Intel calls this technology Extended Page Tables (EPT), AMD calls it Rapid Virtualization Indexing (RVI).
Before enabling the Hiper-V component, you need to check if all these technologies are enabled in BIOS / UEFI. In some cases, enabling them may require a BIOS update.
You can check if the processor supports these virtualization technologies on the intel website http://ark.intel.com/Products/VirtualizationTechnology or amd http://products.amd.com/pages/desktopcpuresult.aspx
You can also use the utility for Intel processors IntelProcessorIdentificationUtility.
1. Download the program from the Intel site downloadcenter.intel.com
2. Install and run the program.
3. Go to the tab CPU technology, to check if the processor supports virtualization technologies.
Enabling the Hyper V component in MS Windows 8.1
1. To install - you need to open Control Panel -> Programs and components and select item Enabling or Disabling ComponentsWindows.
This window can be called by pressing Win + R (to open a window Execute) and entering OptionalFeatures.
2. In the window that opens, find the item Hyper-V
Besides the platform itself Hyper-V this includes tools for managing it - graphical snap-in Hyper-V Manager and module Hyper-V for PowerShell.
3. Set the checkboxes in the checkboxes of all necessary components and click OK, after which you will need to restart your computer.
4. After rebooting, shortcuts will appear in the Metro interface Hyper-V Manager and Connections to the Hyper-V virtual machine.
5. These labels are also available in C: \ ProgramData \ Microsoft \ Windows \ Start Menu \ Programs \ Hyper-V Management Tools
Installing a guest operating system in Hyper-V
1. Open Hyper-V Manager
2. In the main menu, select Actions -> Create -> Virtual Machine ... Similar actions are available in the right pane Actions.
3.In the opened wizard dialog box, click Further
A wizard is needed to assist in the process of configuring a virtual machine. It collects information about the location of the virtual machine, its name, information about the virtual network for connecting the virtual machine, parameters of the virtual hard disk, etc.
4. In the next dialog box, specify the name of the virtual machine, and if you want to store the virtual machine in a location that differs from the one suggested by default when installing Hyper-V, you need to specify a new location.
5. In the next step, you must specify the generation of the virtual machine
The second generation of virtual machines appeared only in the latest version of Hyper-V and has a number of features, some of them are listed below:
- only operating systems can be used as a guest operating system in a second generation virtual machine:
- Windows Server 2012 and Windows Server 2012 R2
- Windows 8 (64 bit) or Windows 8.1 (64 bit).
- no outdated devices such as floppy drive and COM ports
- there is no IDE controller, instead of it there is a SCSI controller with the ability to boot
- the standard BIOS is replaced by a firmware based on the Unified Extensible Firmware Interface (UEFI).
6. In the next dialog box, you must specify the amount of RAM for the guest system.
RAM configuration greatly affects Hyper-V performance. The option of using dynamic memory is available. When using dynamic memory, virtual machines that require more memory are allocated memory resources for virtual machines that have lower RAM requirements. For example, those that are idle.
7.In the next step, the virtual machine wizard will show the screen Network configuration.
You must specify the virtual switch to which the virtual machine will be connected. If in this window there is no choice of network adapters, you must create a virtual switch after completing the configuration of the virtual machine.
8. At the next step, when configuring a new virtual machine, you must set the radio button in paragraph Create a new virtual disk... You can specify the name of the virtual hard disk, its location and size. If the virtual machine has already been created, you can choose Use an existing virtual hard disk or Mount the virtual disk later.
9. In the dialog box Installation options you need to choose where the operating system will be installed from. It is necessary to set the radio button in the Image file (.iso) item and specify the path to the iso image of the operating system being installed.
If the distribution of the operating system is written to disk, you must select PhysicalCD orDVD disc. If you need to write the path to the ISO image of the operating system later, you can choose Install the operating system later.
10.The dialog box of the final configuration of the virtual machine. If you need to make changes to the configuration, you must press the button Back. After pressing the button Ready the entry for the new virtual machine will appear in Hyper-V Manager in the state Off.
Creating and configuring a virtual switchHyper-V
11.In the menu Actions select Virtual Switch Manager.
There are three types of virtual networks that you can connect to in Hyper-V: private, internal, and external virtual network
A private virtual network allows all virtual machines to communicate with each other. There is no physical network adapter associated with private networks. On a given network, virtual machines cannot communicate with the receiving operating system, and the receiving OS cannot communicate with virtual machines on a private virtual network.
An internal virtual network is similar to a private virtual network in that it allows all virtual machines to interact with each other, but unlike a private network, virtual machines can also interact with the host system.
External networking is used when you need to provide a virtual machine with access to a physical network. Essentially, a physical network adapter is associated with a virtual switch, and Hyper-V takes over when the virtual machine tries to access the network through that switch.
12. Select the type of virtual network External -> Create Virtual Switch
13. In the window that opens, the virtual switch properties window, you must specify the name of the switch and the type of connection.
14.When creating an external network, you can allow shared access to the network adapter from the side of the virtual switch and the host system, for this you need to select the checkbox Allow the managing operating system to share this network adapter.
15 . If the network uses logical subnetting, then for the virtual switch connected to the external network, you can enable the use of VLANs by checking the checkbox Allow VLAN identification for the managing operating system and specify the VLAN ID.
16. Press Apply-> OK
17. On the panel Virtual machines select the configured virtual machine and open the context menu with the right mouse button.
18. In the context menu, select Parameters -> Network adapter
19. Specify the created virtual switch for the selected virtual machine
20. Press Apply-> OK
21. Start the installation of the guest operating system by clicking on the icon Start on the panel Actions(you can also start the virtual machine by selecting in the main menu Action-> Start or via the context menu).
Don't put the Russian version! For no price. I suffered with her for a week, I could not understand why updates are not installed using the local console, why firewall rules are not applied, why ... The list is long. Having spat on all this, I saved the files of the virtual machines 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 (point 8) and install updates (points 5 and 6). If everything went well, then you can move on. If not, check what and how. A ghost of 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 in 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 customization features. Specifically, we have to configure the firewall and add a common user.
Add a local administrator (point 3 of the server configuration, for example "hyperadmin / hyperpwd") to not use the default administrator). The same user (maybe not an administrator) must be added on the machine with which you will connect via RDP. When creating a user on my machine, I wrote 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 hardware for managing the server firewall. This will save you a lot of time. I do not plan to do regular edits of the rules - the server should just work. And I don't want to keep the PowerShell and CMD syntax in my head, enough for me and Linux. So I will enable remote firewall access! Considering that you need to manage the server in an amicable way through a dedicated network (physically, VLAN), my option will not reduce overall security. Alternatively, you can install a software and hardware firewall, for example, Mikrotik, between the host and the network (without WiFi, of course). This is a completely inexpensive solution with acceptable performance and reliability.
You can enable the ability to remotely manage the firewall 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 launch the mmc console on the workstation with "hyperadmin" privileges 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. Everything:)
Despite everything, the console is the most reliable control tool. 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 with.
Launch Hyper-V Manager as user "hyperadmin" and click "Connect to Server" at the top left. Again by 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, not the GUI). Therefore, I decided to install Windows 8 (trial is enough, for now) to compare "how it works" through Windows 8. Nothing like that, there was a possibility of converting VHD disks to VHDX, the same migration buttons that I mentioned 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 the good old 7 (until recently, they also talked about the "good old XP-shka").
In order for 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
Don't 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 go to the next section Connected, rejoice, we are starting to install the guest virtual machine ... Stop! 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 need to do is open the hard drive manager, format to NTFS and reassign drive letters(DVD will be E: \, 500 GB drive will be D: \ - I hate it when DVDs hang between discs :)). HOW TO DO IT???
Remote disk management
To remotely manage disk (Disk Management), you need to perform the following steps:
1. Start Virtual Disk Service (VDS) on the server
View a list of services with names starting with "R" using PowerShell:
Get-Service -Name r *
Starting the VDS (Virtual Disk Services) service:
If required, enable “Remote Volume Management” on the client computer (from which we will manage our server).
If we had not turned off the firewall completely, then further step 2 would have to be completed.
2.Allow Disk Management.
Netsh advfirewall firewall set rule group = “Remote Volume Management” new enable = yes
It is necessary to run 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 a local computer, but a remote one, 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".
In our previous articles, we looked at installing the free Hyper-V hypervisor as one of the Windows Server roles. One of the disadvantages of this method is the need for a license for the server OC, which in some cases can lead to additional costs, at the same time there is a standalone product Hyper-V Server, which allows you to use the hypervisor of the same name without any restrictions, completely free of charge. However, it is more complicated in installation and initial configuration, which will become the subject of our today's article.
First of all, let's clarify the terms. Hyper-V is a free hypervisor from Microsoft that runs on the Windows platform. Initially, only server versions were supported, but starting with Windows 8 (Pro edition or higher) it can also be used on desktop operating systems. Although Microsoft does not explicitly designate hypervisor editions, newer OS generations contain new versions of Hyper-V. Since the degree of integration of Hyper-V into the OS is quite large, you cannot update the hypervisor version separately from the OS version.
If you focus on the version of the configuration of virtual machines, then we can talk about eight generations of Hyper-V, version 8.0 contains Server 2016 and Windows 10 (1607). The most common Windows Server 2012 R2 (and Windows 8.1) have the fifth generation of the hypervisor.
Thus, if we want to use the latest version of the hypervisor, then we need the latest version of the OS. And since Windows licenses do not allow for later OS releases, free Hyper-V might not be all that free. Similar difficulties arise when virtualizing existing environments covered by licenses for earlier versions of Windows or virtualizing UNIX systems. Especially for such cases, Microsoft has released a special product - Hyper-V Server.
Hyper-V Server is a special edition based on Windows Server Core with heavily trimmed features that only provide hypervisor functionality and maintenance. However, contrary to popular belief, there is no difference between Hyper-V Server and Hyper-V as a Windows Server role. They are one and the same product.
When they talk about Hyper-V Server and Windows Server Core, they first of all try to focus on saving resources due to the lack of a GUI, but this opinion is erroneous. When creating these products, the issue of saving resources was the last thing, and it’s silly to talk about any "lack of resources" on the hypervisor.
The main goal of creating Windows Server Core and Hyper-V Server is to reduce the number of running services and system components, which can reduce the attack surface (fewer services - fewer vulnerabilities) and significantly reduce system maintenance costs, for example, fewer reboots when updating the system and less time to install updates. Therefore, it is worth considering the implementation of Hyper-V Server, even if you are not experiencing difficulties with licensing.
Installing and Initial Configuration of Hyper-V Server
The installation image can be obtained from the official website, after registration, if you still did not have a Microsoft account. The installation process is no different from installing other versions of Windows and should be straightforward.
Upon completion, we are greeted by an extremely laconic interface with two open windows: a command line and a text configuration utility.
If you closed the latter, then to call this utility again, simply run the command:
But if you close all windows, including the command prompt window, you may suddenly find yourself in front of a black screen with no system controls at all. In this case, click Ctrl + Shift + Esc(this combination also works via RDP) and using the called task manager, start the process you need, for example, the command line.
Let's move on to setting up. The first step is to configure the network, specify the server name, its membership in the desired workgroup or domain, and enable Remote Desktop. Also, if you want your server to respond to the ping command, then you should go to the item 4) Setting up remote control and choosing the option 3) Configuring the server response to the ping message explicitly allow this action.
Then specify the server update options and install all currently available updates. There is one "surprise" associated with manual installation: the symbols specified in the utility do not work, and in order to download and install all available updates, you need to enter a small Russian letter when prompted T.
After completing the configuration and installing updates, the server should be rebooted. A completely natural question may arise here: what to do next? How do you manage it? To manage the Hyper-V Server, you will need another computer with the Hyper-V management tools installed, and the server itself can be configured from the MMC. To do this, we will create the necessary permissive rules in the firewall. To do this, start PowerShell and sequentially execute the following commands:
Powershell
Enable-NetFirewallRule -DisplayGroup "Windows Remote Control"
Enable-NetFirewallRule -DisplayGroup "Remote Event Log Management"
Enable-NetFirewallRule -DisplayGroup "Remote Volume Management"
Enable-NetFirewallRule -DisplayGroup "Remote Desktop Control"
At this point, the server configuration should be considered complete, you can check the connection to it using RDP and, if everything went well, proceed to the client station configuration.
Configuring the Client to Work with Hyper-V Server
To manage Hyper-V Server, you will need a PC with OS at least Windows Server 2012R2 or Windows 8.1 Pro or Enterprise edition, we will consider further configuration using the example of client OS. Home and 32-bit versions of the OS will not work, as they do not have the ability to install Hyper-V Manager.
Since network discovery and sharing of files and printers on the server is disabled, you need to add a type A record for it on the DNS server, linking the server name and its IP address, or add the corresponding line to the file hosts, in our case it looks like this:
192.168.18.145 HV-CORE-2012R2
If your server is in a workgroup, then you should add the connection parameters to it, otherwise the client will try to connect from under the current user.
Cmdkey / add: ServerName / user: UserName / pass: password
where ServerName- Hyper-V server name, UserName- the name of the Hyper-V server administrator, and password- his password.
If you are using Windows 10, then additionally run the command line (or PowerShell console) as administrator and run the commands there:
Winrm quickconfig
winrm set winrm / config / client "@ (TrustedHosts =" ServerName ")"
where ServerName is the name of the Hyper-V server.
Then run the snap dcomcnfg, via Win + R or from the command line, and expand the tree Component Services - Computers - My Computer... Then, by right-clicking the mouse, select Properties and go to the bookmark COM Security - Access Rights - Change Restrictions and in the window that opens, set for the user ANONYMOUS LOGIN rights Remote access.
After completing these settings, you can start the MMC console Computer management and by right-clicking on the root item of the same name, select Connecting to another computer and provide the name of the Hyper-V server.
Then you can manage the remote server using the familiar set of tools. For most everyday tooling tasks Computer management quite enough, especially considering that most of the settings are done only once.
To use a snap Disk management you will need to start the service first Virtual disk, it can be done right here via snap Services.
The only unavailable rig will be Device Manager, you can customize its operation, but there is no practical sense in this, since it will still work in the "read-only" mode. In addition, in fact, this does not pose a problem: the database of Windows Server drivers is quite extensive and if you have shown reasonable foresight when choosing your hardware, then you will not have to address the issue of drivers at all.
Otherwise, you should turn to the command line tools for working with drivers: 1.6. Hardware Installation and Driver Management (Local)
Finally we come to the most important thing. Let's go to the classic Control Panel - Programs and Features - Turn Windows features on or off and install Hyper-V Management Tools.
After that, you will have at your disposal the familiar Hyper-V management tool that allows you to fully manage the hypervisor. There are no peculiarities in working with Hyper-V server, so we will not dwell on this issue in more detail.
In order to transfer files to the hypervisor, for example, an image for installation, you can use standard shares, say by typing in the address bar of the explorer:
\\ ServerName \ C $
you will be taken to the C: drive of the server.
For example, we created a new virtual machine and installed a fresh version of Debian there, without experiencing any difficulties either when working with the hypervisor or with the virtual machine itself.
As you can see, despite the somewhat more complicated installation and configuration process, Hyper-V Server is a convenient and reliable tool that can also be used completely free of charge.
This article shows the steps you can take to create a virtual machine in Hyper-V Manager on Windows 10
Microsoft Hyper-V technology is an embedded hardware virtualization system that provides guest systems with direct access (without the participation of intermediate virtual drivers that slow down the work) to computer devices (disk, memory, processor).
The operating system inherited the Hyper-V component from previous versions, Windows 8 and. On Windows 10, Hyper-V is only available in 64-bit Pro and Enterprise editions. The system requirements for enabling Hyper-V are detailed in the article ➯
In Windows 10, the Hyper-V hypervisor, in addition to guest operating systems of the Windows family, now supports some Linux distributions, in particular, the popular Ubuntu.
You can install new distributions of operating systems on a virtual machine for testing, and also use it as a server.
CONTENT:1
How to start Hyper-V Manager
There are several ways to start Hyper-V Manager
➁ You can use the search, to do this, click on the search icon on the taskbar or press the key combination + S, in the window that appears, enter hyper-v in the search field. In the search results, select Hyper-V Manager, or right-click and select Home screen or Pin to taskbar(if you will be using Hyper-V Manager frequently).
➂ You can also start Hyper-V Manager, you can from the list of programs in the Start menu in the folder "Administration Tools"
➃ You can also create a shortcut to launch Hyper-V Manager, for this right-click on the desktop and in the context menu that appears, select New> Shortcut, then in the "Create shortcut" window in the field Specify the location of the object: enter virtmgmt.msc and click Next
In the next window, in the field Enter shortcut name type for example Hyper-V Manager and click Finish, which will create a shortcut on the desktop with which you can start Hyper-V Manager
How to create a virtual switch
Configuring network access in Hyper-V Manager is configured separately. To do this, in the Hyper-V manager on the left in the list, select the item with the name of your computer, and in the right part of the window, select Virtual Switch Manager ...
In the virtual switch creation wizard that opens, you need to select the type of network. Depending on what kind of access you plan to provide to virtual machines, you can choose one of three types of virtual network:
● External - This type uses the network card or Wi-Fi adapter of the physical computer and connects the virtual machine to the same network as the physical computer. Accordingly, this type of network provides for a virtual machine to access the Internet.
● Internal — This type provides a network between the physical computer and Hyper-V virtual machines, but does not allow them to access the Internet.
● Private - this type allows you to create a network between Hyper-V virtual machines, but this network will not have a physical computer, nor will there be an Internet connection.
In this case, the virtual machine needs access to the Internet, so we select the first type - external network and click Create virtual switch
In the properties window of the virtual switch, give it a name, it can be any name, in this example, Virtual Network. If your computer has both a Wi-Fi adapter and a network card, select in the External network item the one of the network adapters that is used to access the Internet. In this case, a Wi-Fi adapter is used. After making the settings, click the OK button
The virtual network adapter has been created. You can see the result of adding a virtual switch to Hyper-V on a physical machine in the "Network Connections" window. As a result, a network bridge and a virtual adapter were created.
How to create a virtual machine
in Hyper-V Manager
To create a virtual machine in Hyper-V Manager, right-click on the computer name and select New> Virtual Machine ...
In the first window of the virtual machine creation wizard, click the Next>
In the next window, we give the virtual machine a name, you can also change its location (the standard location for virtual machines is the folder C: \ ProgramData \ Microsoft \ Windows \ Hyper-V) on the disk of the physical computer, specifying the desired disk partition and the desired folder using the Browse ... button, click the Next>
The next step is to select the generation of the virtual machine. Select the required generation of the virtual machine (in this case, generation 2) and click Next>
Generation 1 are virtual machines that support 32-bit and 64-bit Windows systems. Generation 1 is backward compatible with Hyper-V
Generation 2 is a new format virtual machine with UEFI-based firmware. These virtual machines support a number of new features and can provide small performance gains. On virtual machines of generation 2, only 64-bit versions of Windows 8.1 and 10, as well as server Windows Server 2012, Server 2012 R2 and Server 2016 are installed as guest OS
Next, in the memory allocation window, we leave the preset parameters if the physical computer has no more than 4 GB of RAM. If the RAM is more than 4 GB, you can increase the amount allocated when the virtual machine starts. Select the amount of memory you want and click Next>
In the Network Settings window, in the Connection drop-down list: select the previously created virtual switch and click Next>
In the "Connect virtual hard disk" window, specify the desired location on the disk, the name of the virtual hard disk file, and set the size that will be sufficient for your purposes and click Next>. In this case, the default parameters are left.
The next step is to specify the path to the Windows distribution. Second generation virtual machines do not boot from a physical CD / DVD drive. The sources for downloading the distribution of the guest operating system can only be the network and the ISO image. In this case, it is an ISO image. Click Next>
Then, in the Completing the New Virtual Machine Wizard window, click Finish
Connecting and starting a virtual machine
After creating a virtual machine, it will appear in the list of virtual machines in Hyper-V Manager. Now the virtual machine needs to be connected. To do this, right-click on the virtual machine and select Connect from the context menu. The Connect command is also present on the right side of the Hyper-V Manager window. To connect, you can also double-click the left mouse button on the preview window of the selected virtual machine.
In the connection window that opens, click the green Start button
The normal Windows 10 installation process will then begin as it would on a physical computer.
As soon as copying the installation files starts, you can close the window for connecting to the virtual machine.
Closing the connection window will free up some of the physical computer's resources for other tasks, while the virtual machine continues to run in the background. Its performance will be displayed in Hyper-V Manager. You can connect to a virtual machine as needed to perform actions in it.
