Here are some important information and improvements Microsoft released for Hyper-V Manager in Tp5:
- Alternate credentials support. You can now use a different set of credentials in Hyper-V Manager when you connect to another Windows Server 2016 TP5 or Windows 10 remote host. You can also save these credentials to make it easier to log on again.
- Previous version management: the New Hyper-V Manager will allow you to manage versions manage computers running Hyper-V on Windows Server 2012/R2 and Windows 8.x client version.
- Updated management protocol – Hyper-V Manager has been updated to communicate with remote Hyper-V hosts using the WS-MAN protocol, which permits CredSSP, Kerberos or NTLM authentication. When you use CredSSP to connect to a remote Hyper-V host, you can do a live migration without enabling constrained delegation in Active Directory. The WS-MAN-based infrastructure also makes it easier to enable a host for remote management. WS-MAN connects over port 80, which is open by default.
- No more Integration services for Windows Virtual Machines. Updates to integration services for Windows guests are distributed through Windows Update. For service providers and hosting companies, this puts the control of applying updates into the hands of the tenants who own the virtual machines. Customers (tenants Administrators) can now update their Windows virtual machines with all updates, including the integration services, using a single method.
- Integration services for Linux and FreeBSD Virtual Machines. Hyper-V supports both emulated and Hyper-V-specific devices for Linux and FreeBSD virtual machines. Linux Integration Services (LIS) or FreeBSD Integration Services (BIS) , the collection of drivers that are required to run Hyper-V-specific devices, has been added to the Linux kernel and is updated for new releases, but Linux distributions based on older kernels may not have the latest enhancements or fixes. Microsoft provides a download containing installable LIS drivers for some Linux installations based on these older kernels.
Note: As some Linux distributions include versions of LIS, make sure you install the latest downloadable version of LIS, if applicable, for your installation.
Red Hat announced the release of RHEL 5.9 which includes the Hyper-V Linux Integration Services built-in.
New Virtualization Capabilities and Flexibility in Multi-vendor Environments. Red Hat Enterprise Linux 5.9 enhances the operating system’s usability in multi-vendor environments by introducing Microsoft Hyper-V drivers for improved performance. This enhances the usability of Red Hat Enterprise Linux 5 for guests in heterogeneous, multi-vendor virtualized environments and provides improved flexibility and interoperability for enterprises.
To download Red Hat Enterprise Linux 5.9 visit here
keeping time inside of virtual machines, how Hyper-V tackles these ?
Check out here in Ben Armstrong, Microsoft Virtualization Program Manager : http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/19/time-synchronization-in-hyper-v.aspx
When Microsoft says that does not support all linux distributions, does not mean that a particular distribution will not work on Hyper-V.
It’s easy to get a DEBIAN running on Hyper-V. It took me more time to install Debian than to add the Hyper-V integration services components, thanks to Yusuf Ozturk , who created the kernel updates, ready to deploy on Debian.
Here are the steps:
1. Download Debian 5.06 (lenny) from http://www.debian.org/releases/lenny/debian-installer/ (full CD/DVD sets – CD 1 )
2. Create a VM with 1 Legacy Network ( we will add the synthetic one, later ) and 4 processors
3. Install Debian using the ISO.
4. After installation finished, logon
5. Using a Terminal session, typed the following commands
# apt-get update
# aptitude update
# wget -c http://www.yusufozturk.info/linux/linux-headers-2.6.36-hyperv-debian.x86_64.deb
# wget -c http://www.yusufozturk.info/linux/linux-image-2.6.36-hyperv-debian.x86_64.deb
# dpkg -i linux-image-2.6.36-hyperv_2.6.36-hyperv-10.00.Custom_amd64.deb linux-headers-2.6.36-hyperv_2.6.36-hyperv-10.00.Custom_amd64.deb
# echo -e “hv_vmbus\nhv_storvsc\nhv_blkvsc\nhv_netvsc” >> /etc/initramfs-tools/modules
# update-initramfs –u –k 2.6.36-hyperv
6. Shutdown the Virtual Machine
7. Added synthetic Network
8. Start the VM
Now you have a Debian distribution running on Hyper-V, with 4 processors, synthetic network and also integrated shutdown is available. Simple as that!
When installed in a supported Linux virtual machine running on Hyper-V, the Linux Integration Components provide:
• Driver support for synthetic devices: The Linux integration components include support for both the synthetic network controller and synthetic storage controller that have been developed specifically for Hyper-V. These components take advantage of the new high-speed bus, VMBus, which was developed for Hyper-V.
• Fastpath Boot Support: Boot devices now take advantage of the storage VSC to provide enhanced performance.
• Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.
• Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager, using the “Shut Down” command.
• Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.
• Heartbeat: Allows the host to detect whether the guest is running and responsive.
• Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest.
Although this version of the integration services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 / 5.3 / 5.4 / 5.5, Red Hat Enterprise Linux 5 x64 editions do not support using the Pluggable Time Source component.
However, you can use the existing timesync component with the adjtimex RPM package, to compensate for time drift:
If using the x64 version of Red Hat Enterprise Linux, follow these additional instructions:
1. Attach the Red Hat Enterprise Linux ISO that was used for installation in the virtual machine, and mount it using the following commands at a shell prompt:
# mkdir /mnt/cdrom
# mount /dev/cdrom /mnt/cdrom
2. Install the adjtimex RPM for more accurate time keeping in the virtual machine:
# rpm –ivh /mnt/cdrom/Server/adjtimex-1.20-2.1.x86_64.rpm
To install the Linux IC.
After the ISO is “available”.
Firstly, install the Required Components via Command Line
Red Hat updates
# yum install kernel-devel
# yum groupinstall “development tools”
# yum update
Restart the VM and then, insert the LinuxIC iso into the DVD drive and copy the contents to /opt/linuxic directory.
Run the commands below, to install the IC:
# mount /dev/cdrom /mnt
# mkdir /opt/linux_is
# cp –r /mnt/* /opt/linux_is
# cd /opt/linux_is
# make install
To verify that the Linux ICs are working.
# /sbin/lsmod | grep vsc
# modinfo vmbus
To verify the Synthetic Ethernet adapter is working
# ifconfig seth0 Note: Article also published by myself at http://social.technet.microsoft.com/wiki/contents/articles/workaround-for-pluggable-time-source-support-for-rhel-5-x-64-bit-hyper-v-guests.aspx My thanks to Sumesh P - MSFT, who helped with the tip.