A story about how to run an android emulator or save on an intel processor. Story on how to run android emulator or save on intel cpu Can't start virtual machine because low level
Cause. The hypervisor (hypervisor) is not running. You receive the following error message in the system error log: "Unable to start virtual machine because the hypervisor is not running."
Elimination. To run the hypervisor, the physical computer must meet certain hardware requirements. For more information, see Requirements for Hyper-V installations. If the computer does not meet the requirements, you will not be able to use it to run virtual machines. If your computer meets the requirements and the hypervisor is not running, you may need to enable the options for hardware virtualization and hardware data execution prevention (DEP) in the BIOS. After changing these settings, you must turn off and then turn on the power of the computer. Restarting the computer does not take effect.
Cause. Virtual Disk, which is used as the system drive, is attached to the SCSI controller.
Elimination. Connect system disk to IDE controller. For instructions, see Set up disks and storage devices.
Cause. The virtual machine is configured to use physical CDs and DVDs as installation media, using a physical drive.
Elimination. Only one virtual machine can access a physical CD/DVD drive at a time. Disconnect the CD/DVD drive from the other virtual machine and try again.
Unable to install an operating system on a virtual machine over the network.
Cause. The virtual machine is using network adapter instead of the legacy network adapter, or the legacy network adapter is not connected to the appropriate external network.
Elimination. Make sure the virtual machine is configured to use a legacy network adapter that is connected to an external network that provides installation services. For instructions on configuring network adapters, see Configuring your network.
The virtual machine is automatically suspended.
Cause. The virtual machine will be automatically suspended if the volume where snapshots or virtuals are stored hard drives, not enough free space. The status of the virtual machine in Hyper-V Manager will be listed as Critical Suspend.
Elimination. Create additional disk space using Hyper-V Manager to apply or remove snapshots individually. Or, to remove all snapshots, export the VM without its data, and then import the VM.
When trying to create or start a virtual machine, error messages appear: "The mapped partition has been opened by the user", "The network resource or device is no longer available", or "The I/O operation was aborted due to the completion of the command stream or at the request of the application".
Cause.
Elimination.
The virtual machines have disappeared from the Hyper-V Manager console.
Cause. The reason may be antivirus program, which runs on the host operating system when monitoring of virtual machine files in Hyper-V is configured using the Real-time Inspection component.
Elimination. Exclude virtual machine files from real-time scanning. For information about specific files, see Microsoft Knowledge Base article 961804 (http://go.microsoft.com/fwlink/?LinkId=143978).
When using a virtual machine connection, the mouse pointer becomes a dot or gets stuck in the virtual machine window.
Cause. The operating system on the virtual machine does not have integration services installed.
Elimination. If the operating system on the virtual machine is supported, integration services will be available for that operating system. To improve mouse integration, install Integration Services. For instructions, see Installing an Operating System in a Virtual Machine. If the operating system on the virtual machine is not supported, then you can use a keyboard shortcut to move the mouse outside the virtual machine window. The default keyboard shortcut is CTRL+ALT+LEFT ARROW.
Unable to use the mouse to control the virtual machine. Remote Desktop Connection is used to connect to a server that has Hyper-V installed.
Cause. When using Hyper-V Manager to connect to a virtual machine, this connection is provided by the Virtual Machine Connection feature. However, using a virtual machine connection in a Remote Desktop Connection session is not supported unless integration services are installed. Therefore, the expected result is loss of mouse functionality.
Elimination. Do not use Virtual Machine Connection in a Remote Desktop Connection session until integration services are installed. There are several ways to solve this problem.
- Install Integration Services. For instructions, see Installing an Operating System in a Virtual Machine.
- Establish a Remote Desktop Connection session directly on the virtual machine.
- Log in to the console of the server running Hyper-V and use the Virtual Machine Connection component to connect to the virtual machine.
- On a supported client computer install the Hyper-V management tools to install the Virtual Machine Connection feature and create a virtual machine connection session. For more information, see the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=143558).
When you open Device Manager in the operating system on a virtual machine, some devices are marked as unknown.
Cause. Device Manager does not recognize devices that are optimized for use on virtual machines and start at Hyper-V help if integration services are not installed. Unknown Devices The ones identified in Device Manager vary depending on the operating system on the virtual machine and may include: VMBus, Microsoft VMBus HID Miniport, Microsoft VMBus Network Adapter, and storvsc miniport.
Elimination. If the operating system on the virtual machine is supported, integration services will be available for that operating system. Once Integration Services is installed, Device Manager will recognize the devices available for that operating system on the virtual machine. For instructions, see Installing an Operating System in a Virtual Machine.
The performance of the virtual machine needs to be monitored, but the CPU information in Task Manager does not show what CPU resources are being used by the virtual machine.
Cause. Task Manager does not show CPU information for virtual machines.
Elimination. To view CPU usage information for virtual machines running on a server running Hyper-V, use System Performance and Reliability Monitor. It shows data obtained from Hyper-V performance counters. To open System Performance and Reliability Monitor, click the button Start, select a command Run and type perfmon.
The data from the performance counters listed below can be viewed on the managing operating system (running the Hyper-V role).
- Hyper-V Hypervisor Logical Processor - % Guest Time: Determines the amount of physical processor resources used to run virtual machines. This counter does not identify individual virtual machines or the amount of resources consumed by each virtual machine.
- Hyper-V Hypervisor Virtual Processor - Guest Time %: Specifies the amount of virtual processor resources consumed by the virtual machine.
Hyper-V
, native to Windows systems- in its server editions, as well as in some desktop versions and editions - an environment for working with virtual machines and their guests OS does not always work without problems. One of these problems may be a notification that pops up when starting a virtual machine, saying that, Hyper-V it cannot be started because some hypervisor is not running.
What is this error and how to fix it.
A window with such an error is a universal interpretation, the reason may lie in several things.
System requirements
If Windows itself does not meet the requirements to work with Hyper-V, and not all desktop editions allow you to work with this component, it simply does not activate in the system. But there are also hardware requirements. Their mismatch may not affect the activation of the hypervisor, but in the future it may cause such an error.
For work Hyper-V necessary:
At least 4 GB RAM;
64-bit processor with support for SLAT and virtualization technology.
BCD storage
The error in question may indicate an incorrect storage data configuration BCD. Component Hyper-V is deeply integrated into Windows and starts before the system kernel starts. If in storage BCD changes were made to modify the launch of the hypervisor, they may not be correct. Or launch Hyper-V and was previously deliberately disabled in order to temporarily optimize the use of computer resources. In this case, the configuration BCD in terms of launching the hypervisor, you must either correct it or return the default value by setting autorun Hyper-V. To install autorun, open cmd on behalf of the administrator (necessarily) , enter:
bcdedit /set hypervisorlaunchtype auto
After that, we reboot.
AMD Bulldozer
Hyper-V does not work with company processors AMD with architecture Bulldozer.
Virtualization Technologies
To ensure the life of the virtualization environment through any hypervisor, the processor must be equipped with a technology that provides virtualization - Intel Virtualization, or else AMD-V. Support for these technologies can be found on the processor specifications page on the websites, respectively, Intel and AMD. And virtualization technology, of course, should be included in BIOS .
Another important nuance: for processors Intel in BIOS specific technologies must be disabled Intel VT-d and Trusted Execution. The hypervisor built into Windows is not friendly with them. This is what the settings should look like BIOS to work with Hyper-V: Virtualization technology is enabled and specific technologies are disabled.
Hyper-V is an example of a server virtualization technology. This means that Hyper-V allows you to virtualize an entire computer by running several operating systems(usually server) on one physical computer(usually with server-class hardware). Each guest operating system thinks (if operating systems can think) that it owns the computer and has the exclusive right to use its hardware resources (or any other set of computer resources that the virtual machine has access to). Thus, each operating system runs in a separate virtual machine, with all virtual machines running on the same physical machine. In a standard non-virtualized environment, only one operating system can run on a computer. Hyper-V technology provides the computer with this capability. Before considering how Hyper-V technology works, we need to understand general principles work of virtual machines.
General information about virtual machines
A virtual machine is a computing environment implemented in software that allocates the hardware resources of a physical computer in such a way as to provide the ability to run multiple operating systems on a single computer. Each operating system runs in its own virtual machine and has dedicated logical processor instances, hard drives, network cards and other computer hardware resources. The operating system running on the virtual machine has no knowledge that it is running in virtual environment, and behaves as if it has complete control over the computer's hardware. Implementing virtual machines in the manner described above means that server virtualization must be implemented in accordance with the following requirements:
- Management interfaces
Server virtualization requires management interfaces that allow administrators to create, configure, and control virtual machines running on a computer. These interfaces must also support software administration and work over the network, providing remote control virtual machines. - Memory management
Server virtualization requires a memory manager to ensure that all virtual machines receive dedicated and isolated memory resources. - planning tool
Server virtualization requires a scheduling tool to manage virtual machine access to physical resources. The scheduling tool should be configurable by the administrator and be able to assign different levels of priority to equipment. - state machine
Server virtualization requires a state machine that keeps track of the current state of all virtual machines on a computer. Virtual machine state information includes information about CPU, memory, devices, and the state of the virtual machine (started or stopped). The state machine must also support the management of transitions between different states. - Storage and networking
Server virtualization requires the ability to provision storage and network resources on a machine, allowing each virtual machine to have separate access to hard drives and network interfaces. In addition, when virtualizing computers, you also need the ability to simultaneously access multiple machines to physical devices while maintaining consistency, isolation and security. - Virtualized Devices
Server virtualization requires virtualized devices that provide operating systems running on virtual machines with logical representations of devices that behave the same as their physical counterparts. In other words, when an OS from a virtual machine accesses a physical device on the computer, the corresponding virtualized device is accessed, which is identical to the process of accessing a physical device. - Virtual device drivers
Server virtualization requires that virtual device drivers be installed on operating systems running on virtual machines. Virtual device drivers provide applications with access to virtual representations of hardware and I/O connections in the same way that they access physical hardware.
Overview of the hypervisor
The hypervisor is a virtualization platform that allows you to run multiple operating systems on a single physical computer - the host computer. The hypervisor's main function is to create isolated runtime environments for all virtual machines, and to manage the interaction between the guest operating system in the virtual machine and the underlying hardware resources of the physical machine. The term "low-level shell" (hypervisor) was coined in 1972 when IBM updated the System/370 computing platform management software to support virtualization. The creation of the hypervisor was a new milestone in evolution computer science, as it allowed us to overcome architectural limitations and reduce the cost of using mainframes. Low-level shells are different. For example, they differ in type - i.e. by whether they run on physical hardware or are hosted in an operating system environment. Shells can also be divided by design: monolithic or micronuclear.
Type 1 hypervisor
Type 1 low-level shells run directly on the underlying physical hardware of host computers and act as daemons. In other words, they run "on the hardware". In this case, the guest operating systems run on multiple virtual machines hosted above the hypervisor layer (see Figure 1).
Because Type 1 hypervisors run directly on the hardware and not in the OS environment, they typically provide optimal performance, availability, and security when compared to other types. Type 1 hypervisors are also implemented in the following server virtualization products:
- Microsoft Hyper-V
- Citrix XenServer
- VMware ESX Server
Type 2 hypervisor
Type 2 hypervisors run in the OS environment running on the host computer. In this case, the guest operating systems run in virtual machines above the hypervisor (see Figure 2). This type of virtualization is commonly referred to as hosted virtualization. Comparing Figure 2 and Figure 1 makes it clear that guest operating systems running in Hypervisor Type 2 platform virtual machines are separated from the underlying hardware by another layer. Having an extra layer between VMs and hardware causes performance degradation on Type 2 Shell platforms and limits the number of VMs that can be run in practice. Low-level shells of type 2 are also implemented in the following server virtualization products:
- Microsoft Virtual Server
- VMware Server
Monolithic hypervisors
The monolithic architecture of the hypervisor assumes that there are device drivers that support, host, and manage the shell (see Figure 3).
Monolithic architecture has both advantages and some disadvantages. For example, monolithic hypervisors do not require a host (parent) operating system, since all guest systems interact directly with the computer's underlying hardware using device drivers. This is one of the advantages of a monolithic architecture. On the other hand, the fact that drivers must be designed specifically for the hypervisor presents significant challenges, as there are many different types of motherboards, storage controllers, network adapters, and other hardware on the market. As a result, manufacturers of monolithic hypervisor platforms need to work closely with hardware manufacturers to ensure that the drivers for these devices support the hypervisor. It also makes shell manufacturers dependent on hardware manufacturers to supply the necessary drivers for their products. Thus, the range of devices that can be used in virtualized operating systems on monolithic hypervisor platforms is significantly narrower compared to the situation of running the same operating systems on physical computers. An important feature of this architecture is that it ignores one of the most important security principles - the need for defense in depth. In layered defense, several lines of defense are created. In this model, there is no defense in depth, since everything is done in the most privileged part of the system. An example of a server virtualization product that uses a monolithic hypervisor architecture is VMware ESX Server.
Micronuclear hypervisors
Microkernel hypervisors do not require special drivers, since the main (parent) partition is the operating system. Such a partition provides the runtime required for device drivers to access the underlying physical hardware of the host computer. Partitions will be discussed later, but for now imagine that the term "partition" is equivalent to a virtual machine. On microkernel hypervisor platforms, installation of device drivers is required only for physical devices running on the parent partition. Installing these drivers on guest operating systems is not required, as guest operating systems need only access the parent partition to access the physical hardware of the host computer. In other words, the microkernel architecture does not allow guest operating systems to directly access the underlying hardware. Physical devices are accessed only by interacting with the parent partition. Figure 4 shows the microkernel hypervisor architecture in more detail.
A microkernel architecture has several advantages over a monolithic one. First, the absence of the need for special drivers allows the use of a wide range of existing drivers provided by the manufacturer. Secondly, device drivers are not included in the shell, so it creates less load, has smaller size and greater stability. Third, and most importantly, the potential attack surface is kept to a minimum, as no extraneous code is loaded into the shell (device drivers are created by third parties, so they are considered foreign code from the point of view of the shell developer). Agree that the penetration of malicious software into the shell and taking control of all the virtual operating systems of the computer is the last thing you want to experience. The only downside to the microkernel design is the need for a separate parent partition. This increases the load on the system (although it is usually minimal), since the access of child partitions to the hardware requires them to interact with the parent partition. A significant benefit of Hyper-V's microkernel architecture is defense in depth. large quantity functions up the stack (for example, the state machine and control interfaces that execute higher in the stack in user mode). What can be cited as an example of a server virtualization platform with a microkernel architecture? Undoubtedly, this is Microsoft Hyper-V running Windows Server 2008 or later on its parent partition.
Key features of Hyper-V
The following are some of the key features of the original version of the Microsoft Hyper-V platform:
- Support for various OS
Hyper-V supports concurrent execution various types OS, including 32-bit and 64-bit OS on various server platforms(for example, Windows, Linux, etc.). - Expandability
Hyper-V technology has standard instrumentation interfaces Windows controls(WMI) and software interfaces APIs that enable ISVs and developers to quickly create custom tools and extensions for the virtualization platform. - Network load balancing
Hyper-V provides virtual switching capabilities that allow you to use the Windows Network Load Balancing service to load balance virtual machines from different servers. - Micronuclear architecture
Hyper-V has a 64-bit, microkernel hypervisor architecture that allows the platform to provide various device support methods, additional performance, and security. - Hardware virtualization
Hyper-V requires the use of Intel-VT or AMD-V hardware virtualization technologies. - Architecture sharing equipment
Hyper-V uses a provider (VSP) and virtualization service client (VSC) architecture to provide enhanced access and use of hardware resources (such as disk, network, and video). - Quick Migration
Hyper-V allows you to move a running virtual machine from one physical host to another with minimal delay. This is done through highly available Windows Server 2008 and System Center management tools. - Scalability
Hyper-V supports multiple processors and cores at the host level, as well as extended memory access at the virtual machine level. This support provides scalability for virtualization environments to host a large number virtual machines on the same host. However, the fast migration capabilities also allow you to scale across multiple nodes. - Support for symmetrical multiprocessor architecture (SMP)
Hyper-V supports up to four processors in a virtual machine environment for running multi-threaded applications in a virtual machine.
Hyper-V provides the ability to take snapshots of running virtual machines to quickly roll back to a previous state, which streamlines backup and recovery solutions.
What's New in Hyper-V R2
AT Windows versions Server 2008 R2 added new features to the Hyper-V role. They improve the flexibility, performance, and scalability of Hyper-V. Let's consider them in more detail.
Increased Flexibility
Hyper-V R2 contains the following new features that increase the flexibility to deploy and maintain a server virtualization infrastructure:
- Live migration
Hyper-V R2 includes a live migration feature that allows you to move a virtual machine from one Hyper-V server to another without interrupting the network connection, without interrupting the user experience, and without interrupting service. Moving is accompanied by only a decrease in performance for a few seconds. Live migration provides high availability for servers and applications running on clustered Hyper-V servers in a virtualized data center environment. Live migration also simplifies the process of updating and maintaining host hardware, and provides new features such as the ability to balance network load for maximum power efficiency or optimal processor usage. Live migration is described in detail below in the Working with Live Migration section. - Cluster Shared Volumes
Cluster Shared Volumes are new feature Windows Server 2008 R2 failover cluster systems. It provides a single and consistent file namespace that allows all cluster nodes to access the same storage device. The use of Cluster Shared Volumes is highly recommended for live migration and is described below in the "Working with Live Migration" section. - Support for hot adding and removing storage media
The R2 version of Hyper-V allows you to add or remove virtual hard disks and passthrough disks on a running virtual machine without shutting it down and restarting it. This allows you to adjust all of the storage used by the VM with no downtime as the workload changes. In addition, it provides new opportunities Reserve copy at Microsoft SQL Server, Microsoft Exchange Server and data centers. To use this feature, virtual and passthrough disks must be connected to the virtual machine using a virtual SCSI controller. For more information about adding SCSI controllers to virtual machines, see the Managing Virtual Machines section below. - Processor Compatibility Mode
The new processor compatibility mode, available in Hyper-V R2, allows you to move a virtual machine from one host to another when their processor architectures (AMD or Intel) match. This makes it easier to update the Hyper-V host infrastructure by making it easy to migrate virtual machines from computers with older hardware to computers with newer hardware. In addition, it also provides the flexibility to migrate virtual machines between cluster nodes. For example, processor compatibility mode can be used to migrate virtual machines from an Intel Core 2 host to an Intel Pentium 4 host, or from an AMD Opteron host to a AMD Athlon. Note that processor compatibility mode only allows virtual machine migrations if the host processor architectures match. In other words, AMD-AMD and Intel-Intel migration is supported. Migration of virtual machines from a host of one architecture to a host of another architecture is not supported. In other words, AMD-Intel and Intel-AMD migration is not supported. For more information about the processor compatibility mode and its settings, see the sidebar “How it works. processor compatibility mode.
Enhanced performance
Hyper-V R2 contains the following new features that can improve the performance of your server virtualization infrastructure:
- Support for up to 384 simultaneously running virtual machines and up to 512 virtual processors per server
With the right hardware, Hyper-V R2 servers can be used to reach levels of server consolidation that were never before possible. For example, a single Hyper-V host can host:- 384 virtual machines with a single processor (significantly less than the limit of 512 virtual processors)
- 256 virtual machines with two processors (total 512 virtual processors)
- 128 virtual machines with four processors (total 512 virtual processors)
You can also work with any combination of single-core, dual-core, and quad-core processors, as long as the total number of virtual machines does not exceed 384, and the total number of virtual processors allocated to virtual machines does not exceed 512. These capabilities allow Hyper-V R2 to provide the highest density values on the market virtual machines on this moment. For comparison: previous version Hyper-V in Windows Server 2008 SP2 supported a total of up to 24 logical processors and up to 192 virtual machines. Note that when using failover clusters, Hyper-V R2 supports up to 64 virtual machines per cluster node.
- Second Level Address Translation (SLAT) support
In Hyper-V R2, the processor handles address translations in the virtual machines rather than in the Hyper-V code that programmatically performs table mappings. Thus, SLAT technology creates a second layer of pages under the x86/x64 page tables of the x86/x64 processors through an indirection layer from virtual machine memory access to physical memory access. - VM Chimney
This feature allows TCP/IP traffic for the virtual machine to be forwarded to the host's physical network adapter. To do this, the physical NIC and OS must support the TCP Chimney Offload feature, which will improve the performance of the virtual machine by reducing the CPU load on the logical processors. TCP Chimney offload support Microsoft Windows appeared in versions - Support for virtual machine queue (VMQ)
Hyper-V R2 provides support for Virtual Machine Device Queues (VMDq) - Intel technologies Virtualization Technology For Connectivity. VMQ passes the task of sorting virtual machine data traffic from the Virtual Machine Manager to the network controller. This allows a single physical NIC to appear as multiple NICs (queues) to the guest, which optimizes CPU usage, improves network throughput, and provides better VM traffic control. The host then does not store device-side direct memory access (DMA) data in its own buffer, because the network adapter can use this access to direct packets to the virtual machine's memory. Shortening the I/O path improves performance. For more information about the VMDq queue, see the Intel website at http://www.intel.com/network/connectivity/vtc_vmdq.htm . - Support for jumbo frames
Jumbo frames are Ethernet frames containing more than 1500 bytes of payload. Jumbo frames were previously available in non-virtual environments. Hyper-V R2 provides the ability to work with them in virtual machines and supports frames up to 9014 bytes in size (if supported by the underlying physical network).
With appropriate processors (such as Intel processors with extended EPTs since the i7 generation, or the latest AMD processors with nested NPTs), Hyper-V R2 significantly increases system performance in many cases. The performance improvement is due to improved memory management technology and a reduction in the number of memory copies required to use these processor features. Performance is improved especially when working with large datasets (such as Microsoft SQL Server). Memory usage for the Microsoft Hypervisor hypervisor can drop from 5 percent to 1 percent of total physical memory. Thus, more memory will be available to the child partitions, which allows for a high degree of consolidation.
Please note that not all applications may use this feature. In particular, applications that use pre-allocated buffers and long, high-volume connections will benefit the most from enabling this feature. Also, be aware that physical network adapters that support TCP Chimney offload can handle a limited number of offload connections that are used by all host VMs.
As a result, it improves network throughput and reduces CPU usage when transferring large files.
Increased scalability
Hyper-V R2 contains the following new features that increase the scalability of your server virtualization infrastructure:
- Support for up to 64 logical processors in the main processor pool
The number of logical processors supported in this release of Hyper-V has been quadrupled compared to old version Hyper-V This allows businesses to use latest models large and scalable server systems to maximize the benefits of consolidating existing workloads. In addition, the use of such server systems makes it easier to provide multiple processors for each virtual machine. Hyper-V supports up to four logical virtual processors per virtual machine. - Core parking support
The core parking feature allows Windows and Hyper-V to consolidate data processing on the minimum number of processor cores. To do this, inactive processor cores are suspended by placing them in the C state (the "parked" state). This allows VMs to be scheduled to run on a single host rather than spread across multiple hosts. This has the advantage of moving closer to a green computing model by reducing the amount of power required by the CPUs of the data center nodes.
Comparison of Hyper-V and Virtual Server
The power of Hyper-V has already seen it replace Microsoft Virtual Server in many organizations that previously used Virtual Server for server consolidation, business continuity, testing, and development. At the same time, Virtual Server can still be used in corporate virtualization infrastructure. Table 1 compares some of the features and technical data of Hyper-V and Virtual Server.
Table 1. Comparison of components and specifications Virtual Server 2005 R2 SP1 and Hyper-V R2
|
Component or technical data |
Virtual Server 2005 R2 SP1 |
|
|
Architecture |
||
|
Type of virtualization |
Hosted Systems |
Based on the hypervisor |
|
Performance and scalability |
||
|
32-bit virtual machines |
||
|
64-bit virtual machines |
||
|
32-bit nodes |
||
|
64-bit nodes |
||
|
Virtual machines with multiple processors |
||
|
Maximum guest RAM per virtual machine |
||
|
Maximum number of guest CPUs per virtual machine |
||
|
Maximum RAM node |
||
|
Maximum number of running virtual machines |
||
|
Resource management |
||
|
Availability |
||
|
Failover of guests |
||
|
Host Failover |
||
|
Node migration |
||
|
Snapshots of virtual machines |
||
|
Control |
||
|
Ability to expand and control through scripts |
||
|
User interface |
Web interface |
MMC interface 3 0 |
|
SCVMM integration |
||
More information For more information additional information For Virtual Server features and downloads, go to http://www.microsoft.com/windowsserversystem/virtualserver/downloads.aspx . For information about migrating virtual machines from Virtual Server to Hyper-V, see "Virtual Machine Migration Guide: How To Migrate from Virtual Server to Hyper-V" in the TechNet Library at http://technet.microsoft.com/en -us/library/dd296684.aspx .
background
I built a home computer about 4 years ago that suited all my needs. I decided to save on the processor - I took amd. There are no questions about the computer.Then I started developing for Android and then a surprise awaited me! The emulator only ran on intel processor. It could be run without hardware virtualization of course using this tip www.youtube.com/watch?v=QTbjdBPKnnw&t=127s, but who used it knows that the emulator can start for a very long time. I got up to 10 minutes with 12GB. This may of course be due to the built-in video card.
Main workplace I had it in the office, so I was especially worried and tested at home on real devices. But a couple of months ago, the emulator became necessary. The first thought was, of course, to buy an intel processor. But I had to buy more. motherboard and a video card. I probably would have done that if I hadn't stumbled upon the updated system requirements. The requirements say that the emulator can still be run on Windows 10 (with updates after April 2018) using WHPX technology.
Now the main part of the story is how to do it. Everything turned out to be not so trivial. I apologize in advance for omissions, because I can not call myself an expert in either hardware or Windows.
Instruction
After all the updates, the emulator naturally did not start. AndroidStudio was trying to launch the emulator using HAXM and was throwing the error "Emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration!".Must support to work with hardware virtualization.
3. Remove HAXM:
4. Turn on virtualization mode in bios. It may be called IOMMU there, not VT.
5. Download updates for bios from the official site. For my asus, for example, they were .
Bios Version should become something around 3001:
7. We go to the microsoft website and study the instructions for enabling the component.
8. You need to check the Hyper-V requirements. For this in command line typing systeminfo. Check that these values are displayed:
I got this message instead:
The official website says that until Yes-Yes-Yes-Yes, the WHPX system will not work. My emulator starts with the low-level shell enabled.
In Russian translation, the names are somewhat different:
By the way, after disabling the “Platform low-level Windows shells”, “hyper-v requirements” become Yes-Yes-Yes-Yes. I did not understand this moment. If anyone understands, write in the comments.
10. Determine if we need all this? Or was it easier to buy intel)
After these settings, everything should work:
I want to note, using WHPX technology and amd processor, starting the emulator takes about the same time as on an intel processor. Given that the rest of the hardware is comparable in terms of its parameters.
With the advent of virtualization support in new operating systems from Microsoft, and even client Windows 7, 8 and 10, the proprietary Hyper-V service has ceased to be the lot of system administrators in mid-sized companies. Hyper-V may well replace the same popular VirtualBox from Oracle in the field of entry-level (client-level) virtualization. However, before installing this service need to check compliance system requirements, otherwise you may receive the following message: "The virtual machine cannot be started because the hypervisor is not running." What you should pay attention to when choosing hardware for virtualization. Is it possible to somehow save the situation if the hardware has already been purchased? Let's take a look at it in this post.
So, you have Hyper-V deployed on Windows server 2008 Server and when you try to start the virtual machine, you get a window
Do not despair, perhaps the situation can still be saved. It should be noted that the OS must be 64-bit, well, of course, on x32 you would not be able to deploy Hyper-V at all. The first thing to do is to check that the corresponding items are enabled in the BIOS - enable VT and AMD-V. Next, you need to make sure that your processor supports virtualization, check tools for Intel platforms and AMD described one of them is . (pictured below).
It can also help in determining the utility from Mark Russinovich.
Another common problem is the inability to run virtual machines from Windows 2008 R2 on processors that support Advanced Vector Extensions (AVX). This OS does not natively support AVX, however, in this situation, a fix may help you
