Professional Documents
Culture Documents
Windows Hyper V Interview Q&A - 2015!09!19
Windows Hyper V Interview Q&A - 2015!09!19
Windows Hyper V Interview Q&A - 2015!09!19
HYPER-V
Q. What is Hyper-V?
A. Hyper-V, previously codenamed Viridian, is a hypervisor-based technology that is a key feature of Windows Server
2008 R2. It provides a scalable, reliable, and highly available virtualization platform. It is part of Microsoft's ongoing
effort to provide our customers and partners with the best operating system platform for virtualization.
Q. What is Windows hypervisor?
A. A core component of Hyper-V, Windows hypervisor is a thin layer of software between the hardware and the OS that
allows multiple operating systems to run, unmodified, on a host computer at the same time. It provides simple partitioning
functionality and is responsible for maintaining strong isolation between partitions. It has an inherently secure architecture
with minimal attack surface, as it does not contain any third-party device drivers.
Q. What benefits does Hyper-V offer customers?
A. Hyper-V provides customers an ideal platform for key virtualization scenarios, such as production server
consolidation, business continuity management, software test and development, and development of a dynamic datacenter.
Hyper-V provides key functionality, which an ideal virtualization platform should providescalability, high performance,
reliability, security, flexibility, and manageability. It provides scalability and high performance by supporting features like
guest multi-processing support and 64-bit guest and host support; reliability and security through its hypervisor
architecture; flexibility and manageability by supporting features like quick migration of virtual machines from one
physical host to another, and integration with System Center Virtual Machine Manager.
Q. Will Microsoft continue to support Linux operating systems with Hyper-V?
A. Yes, Microsoft provides integration components and technical support for customers running select Linux distributions
as guest operating systems within Hyper-V. Please check the Supported Guest Operating Systems page for more
information and updates.
Q. Can you provide a brief overview of Hyper-V's feature set?
A. Some of the capabilities of Hyper-V include x64 host and guest support, ability to run guest machines in a multiprocessor environment, large memory allocation per virtual machine, integrated virtual switch support, and ability to
migrate virtual machines across hosts with minimal downtime. With the R2 release of Hyper-V, Live Migration, new
processor support, and dynamic virtual machine capabilities were added.
Q. How will customers migrate to Hyper-V?
A. Customers who invest in the .vhd file formatthe format used by Virtual Server, as well as a multitude of vendor
licenseeswill have a clear path forward to Hyper-V. Customers can leverage V2V capabilities in System Center Virtual
Machine Manager to conveniently migrate from Virtual Server or VMware to Hyper-V or work with Microsoft's partners
who provide migration solutions.
Q. Are there tools available to assist in planning for Hyper-V migration?
A.
Yes, the Microsoft Assessment and Planning (MAP) Toolkit helps you plan for Hyper-V migration by determining which
of your physical servers are underutilized and, therefore, good candidates for server virtualization.
LICENSING INFORMATION
Q. How do I know which Windows Server 2008 R2 features or services I am allowed to run on the host without requiring
CALs?
A. When using Windows Server 2008 R2 and Hyper-V to run virtual machines with older versions of Windows Server,
Windows Server 2008 CALs will not be required in certain scenarios.
When the Host OS is only running services related to virtualization, such as Hyper-V and Failover Clustering,
then Windows Server 2008 CALs are not required.
If the Guest OS is Windows Server 2008, or if the Windows Server 2008 host, installs other services, then
Windows Server 2008 CALs would still be required.
Q. What are the licensing considerations in a virtual machine environment?
A. It is important to understand your licensing rights and obligations when running Microsoft Windows Server and/or
other Microsoft applications in a virtual machine environment.
In addition, it's good to understand the licensing terms offered by independent software vendors (ISVs) for any software
provided by those vendors. For more information on licensing considerations in these cases, you should consult with your
ISV.
Q. Does running Windows NT in a virtual machine mean that Microsoft is extending its support for the product?
A. No. While you may receive benefit from moving the applications from physical hardware to virtual machines, running
applications in a virtual environment does not extend their support life cycles. For more information about the support
life-cycle timeframes.
TECHNICAL INFORMATION
Q. What are the system requirements for Hyper-V?
A. In addition to the systems requirement for Windows Server 2008 R2, the two key requirements for the Hyper-V
platform are the need to ensure that the server is a 64-bit environment and supports hardware-assisted virtualization (Intel
VT or AMD-V) technology.
Q. How many virtual machines can run per processor?
A. The number of virtual machines running per host depends on many factors, including physical memory, processor, and
workload running in the guest. With Hyper-V, you define the amount of memory available to a virtual machine, and that
memory allocation can be altered to reflect the needs of the virtual machine.
Q. Does Hyper-V support 64-bit processors?
A. Hyper-V runs on a 64-bit (x64) server platform and requires support of either AMD64 or Intel IA-32e/EM64T (x64)
processors with hardware-assisted virtualization support. Note that Hyper-V does not support Itanium (IA-64) processors.
For the virtual machines, Hyper-V supports both 32-bit and 64-bit systems as guest OSes.
Q. Does Hyper-V support symmetric multiprocessing (SMP) in the virtual machine environment?
A. Hyper-V supports both uniprocessor and multiprocessor configurations in the virtual machine environment.