Hyperv mining

1. Using a closed system or an unpopular system is the simplest and most crude method, which is to some extent fruit powder welfare
to prevent hackers from mining with your machine is just like anti malware. Don't visit messy websites, Download messy software, insert picked up USB flash drives, install anti-virus software (Windows Defender on windows is very good, but it's too strict), check and kill viruses regularly, and check abnormal processes and files regularly. If a program attracts UAC, If you don't understand, try to choose no, and don't believe that "it may be misled by anti-virus software". If possible, you'd better install an isolation machine, shadow system, or create a virtual machine directly with Hyper-V of windows system for daily work
for Android phones, phones before Android 6 are unlikely to win. After all, mobile phone mining also needs good hardware. After Android 6, mobile phones have the management of the authority of each application, as long as they don't go blind root, don't install applications of unknown origin, try to download apps from the official market and rece the unnecessary authority as much as possible (you can also use "refrigerator" and "black domain" to prohibit other apps from running in the background)
for the mobile phones of apple, windows and other operating systems, I think that as long as we don't break the prison blindly and keep the system in the latest version, we can prevent the hooliganism of most apps.

2. First of all, you need to know the basic conditions for using hyper-v.
1. CPU supports hardware virtualization technology.
2. BIOS of motherboard should support virtualization technology.
3. OS must be 64 bit.
for what level of chipset can be supported, please refer to Intel's official website...
unless Dell's entry-level server explicitly states that it supports hyper-v.. Otherwise, there is no hope

3. If you don't use the resources, you have very little space. Only when you use a lot of resources can you occupy it

4. Microsoft introces a so-called "storage spaces" function in Windows 8 system, which integrates all hard disks into a virtual resource pool, and then establishes virtual disks that can be automatically repaired. These virtual disks will have some ZFS functions

advertisement

Steven Sinofsky, director of Microsoft's windows business unit, published a 4400 word in-depth blog article, describing in detail the situation of virtual disk, namely "storage space". Rajeev Nagar of Microsoft's storage and file systems team also contributed to the article
Microsoft added storage space to its Windows 8 beta system, and then displayed it on the Windows 8 developer preview. The central idea of storage space function is to provide automatic data protection and physical disk failure resilience, and the total storage capacity of storage space will be larger than that of a single disk
a group of physical disks consolidates the capacity to form a single named storage pool. Once assigned to a storage pool, a single physical disk is owned by the windows system and cannot be used by Windows 8 users
the disks that make up the resource pool with NTFS can be connected to windows servers through USB, SATA or SAS interfaces, and their capacity, speed and type can be different. Microsoft's blog post did not specify whether the resource pool supports SSDs
this resource pool cannot be used by Windows 8 users or application software as a data storage device. That is one of the functions of storage space. One or more storage spaces can be created in a resource pool. It is called storage space to build whole or part of virtual pool into virtual disk. Each storage space has its own name and disk symbol. For example, you can still use C: disk, but now it is a virtual disk or storage volume, which is composed of all or part of the storage pool after merging physical disks
you can only use storage space if there are a certain number of disks in the storage pool. That is, enough disks are needed to support capacity and data recovery
thin provisioning
data, that is, files and folders, are written to the virtual disk
the storage space can provide the function of thin provisioning, that is to say, the nominal 50tb storage capacity actually only uses 20tb capacity, because all data is written in that way. If the remaining capacity is less and less, Windows 8 will issue a warning to remind users to buy and add more disk capacity. When more capacity is added, new disks will be included in the storage pool and used to meet user needs
any capacity occupied by the deleted file will be returned to the original storage pool to release the storage space of the corresponding capacity< In fact, there are three kinds of storage space: basic space, mirror space and peer space
in the mirror space, all data have at least two copies and are stored on different physical disks. In other words, the system can tolerate the failure of two physical disks, which is roughly equivalent to software raid6; However, if there are only two copies, the mirror space can only tolerate the failure of one physical disk, which is equivalent to software RAID1
If a physical disk fails, the storage space can automatically regenerate the data copies of all affected spaces until there are enough available physical disks in the storage pool
in the mirror space, data is actually stored on a structure called "slabs", each of which has a capacity of 256MB. The slabs are stored on each physical disk participating in the storage pool, providing fault resilience for the whole disk.

5. Hyper-V is a virtualization proct of Microsoft, which is the first hypervisor based technology similar to VMware and Citrix Xen
it is to build a virtual machine, in which other operating systems can run.

6. Hyper-V is a hypervisor based hypervisor hypervisor virtualization technology, which can realize desktop virtualization.

7.

Using Hyper-V built in Windows Server 2008, it personnel can start to build virtual machines on the server and actually test the virtualized IT environment

at present, the common server virtualization software includes not only VMware, which is familiar to all, but also Hyper-V from Citrix and Microsoft, If we just install the virtual machine, the process will not be too complicated

for Hyper-V, if the operating system of the environment is Windows Server 2008, we can use the built-in Hyper-V to install the virtual machine

limit 64 bit Windows Server 2008 operating system

in fact, Microsoft's Hyper-V can not be installed in every version of Windows Server 2008. The first restriction is that you must use a 64 bit operating environment to start hyper-v

moreover, the same 64 bit operating system, such as some versions of Windows Server 2008, such as enterprise, datacenter and standard, can use Hyper-V, but the conditions are not the same, while web 2008 does not have this role, which must be noted ring installation

the second condition is that the processor used by the hardware device must support virtualization technology, such as built-in Intel VT (virtualization technology) and amd-v. in addition to checking whether the processor supports it directly on the Internet, we can also check it directly in the BIOS. If the processor supports virtualization technology, we can check whether the processor supports virtualization technology, We can find the option of virtualization technology in the BIOS processor options and choose to turn it on

installation steps

to start Hyper-V function, the two most important conditions are that you must use 64 bit Windows Server 2008 operating system (excluding Itanium system and Windows Server 2008 R2 WEB), and turn on the virtual technology of processor in BIOS

Hyper-V administrator's operation interface

add a new role in the server administrator, check Hyper-V, and click next installation. After that, the system will restart and install the role

8. It is not easy to select the right hardware for the host and network in the newly deployed Microsoft Hyper-V environment, let alone the task of measuring and monitoring performance in the proction environment. In this article, I will analyze the different components of the underlying hardware architecture of Hyper-V, starting with the processor configuration, and then I will introce the memory, storage, network and other subsystems

then we will introce the methods and skills to improve performance, how to choose the appropriate Hyper-V version, common problems in configuration, and finally introce the performance monitoring of virtual machine and the difference between it and physical environment monitoring

note: all recommendations apply to Hyper-V in Windows Server 2008 R2 (including service pack 1). As far as scalability is concerned, the new Hyper-V version of windows
server 8 has been greatly improved, but this is not the topic of this paper. The recommendations given here apply only to the latest version of windows

virtual processors and logical processors

the IT administrators I contacted often have a misunderstanding about what virtual processors and logical processors are and how they affect the maximum number of virtual machines on a physical host. This is not only related to the number of processors allocated to the virtual machine, but also directly related to the amount of physical memory per host (described in the next chapter)

logic processor is a core of multi-core processor, so a four core processor has four logic processors. If the four core processor has hyper
threading technology, it will be displayed as eight cores; This means that your system has eight logic processors. Although Microsoft's documentation describes logical processors in this way, it should be noted that hyper threading does not magically double the processor capacity. To be on the safe side, let's look at the core as a logic processor - if you enable hyper threading, the number won't double

virtual processors are the resources that you allocate to virtual machines; How many virtual processors you can allocate depends on the guest / virtual machine operating system. Here, the newer the operating system version is, the stronger the function is; So windows
2008 / 2008 R2 can work with four virtual processors, while Windows Server 2003 can only be assigned one or two virtual processors. SUSE
linux enterprise, CentOS, and Red Hat Enterprise Linux (all supported operating system versions) can be assigned up to four virtual processors. If you run a client operating system in a virtual desktop infrastructure (VDI) environment, windows
7 can run with up to four virtual processors, Vista can see two virtual processors, and windows xp
SP3 can see two virtual processors

just because you assign two or four virtual processors to a virtual machine doesn't mean you should. First, because of the cross processor communication, there is a certain overhead in any multiprocessor system, whether it is physical processor or virtual processor. However, in the newer operating system, the cost is relatively low, so it is no problem for windows
2008 R2 virtual machine to use four virtual processors, while Windows Server
2003 may need to be tested to see if it is beneficial to use two virtual processors in your specific environment. Second, it all depends on the workload - some applications are dense multithreaded (think SQL
server and other similar applications), so it's better to use several virtual processors; Single threaded applications or applications with only a few threads don't get much benefit

another common misconception is that assigning one or more virtual processors to a virtual machine is related to the physical core. Assigning virtual processors to virtual machines is more like assigning a predetermined processor time to virtual machines, and the hypervisor actually allocates the burden of running virtual machines to all available processor cores

the number of virtual processors allocated to multiple virtual machines on a certain host is closely related to Microsoft's proposal: each logical processor in a system has at least four virtual processors, and each logical processor has at most eight virtual processors. The exception is: if you are a Windows
7 virtual machine in a VDI environment, the maximum support ratio is 12; That is to say, each logical processor can have up to 12 virtual processors

if you have a Hyper-V host with two quad core processors (i.e. eight logical processors), it's no problem to run eight virtual machines. Each virtual machine has four virtual processors (a total of 32 virtual processors) and up to 16 virtual machines (a total of 64 virtual processors). If you allocate as like as two peas to each virtual machine, two virtual processors will be doubled in each instance. Of course, in reality, the number of virtual processors in different virtual machines will be different, depending on the workload running inside

to view the ratio of virtual processors to logical processors on your host, you can manually view each running virtual machine, and then accumulate the total number of virtual processors allocated. This method is not very convenient. A better way is to run this simple PowerShell
cmdlet command, which will give the answer:

write host (@ (gwmi - ns rootvirtualization MSVM)_ Processor).count /
(@(gwmi

Win32_ Processor) | measure -p NumberOfLogicalProcessors -sum).Sum)
" virtual

processor(s) per logical processor" - F yellow

thanks to Ben Armstrong, the virtualization project manager of Microsoft, for giving this method

indicates the number (8 logical processors in total) on my 4-core laptop with hyper threading technology enabled. There are 4 virtual machines running, and each virtual machine has 4 virtual processors

: with this simple cmdlet command, it's easy to figure out the ratio of virtual processors to logical processors on Hyper-V hosts

it's also important to understand the workloads and applications that you want to run on each virtual machine: are they processor bound or memory bound? Do they benefit from multithreading and therefore from additional virtual processors

make sure that the processor you buy supports Level 2 address translation (slat), which Intel calls extended page table (EPT), amd calls rapid virtualization index (RVI), and AMD's early documentation calls nested page table (NPT). Older processors do not support slat, which means that each virtual machine will take up 10 to 30 MB more memory, and the processor occupancy will increase by 10% or more

slat can bring significant benefits, depending on the workload. If you virtualize Remote Desktop Services, you may see a 40% increase in the number of sessions supported by the slat processor. Processors with high-capacity L2 and L3 caches also help to handle the workload that requires a lot of memory

Figure 2: it's easy to assign virtual processors to virtual machines; Just choose from the list

finally, if you have a host but have limited processor resources, you can change the balance among virtual machines by using virtual machine reservation settings and virtual machine quota settings; The virtual machine reservation setting ensures that the virtual machine can always use this amount of processor resources (but limits the total number of virtual machines that can run on the host). The virtual machine quota setting controls how much processor capacity the virtual machine can use. Relative
weight balances the virtual machine with other virtual machines running; If the value is low, it means that it will get less resources in the competition period. Microsoft's advice is not to change these settings unless you have a good reason to do so

there are also processor compatibility settings, which allow you to migrate virtual machines between hosts with processors of different ages, and also allow you to run very old versions of operating systems, such as Windows NT.

9. Virtualization can be divided into full virtualization and semi virtualization, bare metal architecture and non bare metal architecture
the so-called full virtualization means that the virtual machine does not need to change the system kernel, and all the hardware instructions are given to the virtual emulator of the virtualization layer to proxy. Semi virtualization needs to change the kernel of the virtual machine system, so that it can directly access the physical hardware. Traditionally, the performance of semi virtualization is better than that of full virtualization because of the lack of intermediate agent. Now the full virtualization of VMware has exceeded the performance of part of semi virtualization. In addition to bare metal architecture, the virtualization layer directly installed on the physical hardware is called bare metal architecture (such as esxi, Xen, KVM, etc.), and the virtualization software that needs to be installed with the help of the operating system is not considered bare metal architecture (such as VMware Workstation)

10. First of all, if we open the Hyper-V program, we can find Hyper-V in the windows management tools under all applications, and we click open. After opening, we click new

after clicking New, a selection will pop up. We choose "virtual machine"

then enter the new virtual machine wizard. First, set the name and location for the virtual machine, and click next

then there will be the algebra of virtual machine, which is divided into two generations. We can choose according to our own needs, and then click next

set the memory to be allocated for the virtual machine, and then click next

of course, at the beginning, there is no network configuration. We can click Next directly

then we can see the interface as shown in the figure. If we want to change the name here, we can do it. After modification, click next.