CentOS 6.6 was recently released. As expected, there are a few fixes and updates for Hyper-V guests.
The changes I can remember off the top of my head for Hyper-V guests are:
- Updated KVP and VSS user-space daemons
- CentOS 6.6 is now fully supports virtual NUMA topology presented by the host. In the past, if you have a guest that had processors and memory that spanned across more than 1 NUMA node, the guest would crash due to a bug in the kernel.
- The hv_balloon driver should now not cause a constant 1.00 load average due to the way how the driver reported the memory pressure back to the host.
Unfortunately, the documentation says that there is experimental support for CentOS 6.6 running as a Generation 2 guest. The installer runs fine, but since there is no hyperv-keyboard driver included in the initramfs image of the installer. You will need to install CentOS 6.6 via automated means by using a kickstart file. Unfortunately, when you first boot into the system, you will notice the guest crashes with a kernel panic. This makes Generation 2 support with CentOS 6.6 somewhat pointless at this time.
A while back Samba 4.0 shipped with the Active Directory Domain Controller functionality in the code. The other big thing was basic support for SMB 3.0 which Hyper-V supports hosting VHD’s off from.
Continue reading “Using Samba 4.1 SMB 3’s Feature for Hyper-V VHD(X) Storage”
Recently Ubuntu 14.04 has native support for booting under a Hyper-V Generation 2 VM. Unfortunately, the VM will not boot if the VHD has been copied over to a new VM. This is a known issue and it has been reported on Ubuntu’s Launchpad bug reporting system by a Project Manager inside Microsoft who is responsible for making Linux run under Hyper-V.
Continue reading “Ubuntu 14.04 Generation 2 VM Template Boot Issue Workaround”
As most people do know, it is possible to get Microsoft’s Virtual Machine Manager to deploy and customize a Linux based OS automatically. Officially Microsoft supports Ubuntu 12.04 LTS as a one of Linux distributions they support, however in practice any Debian like distribution can be supported as long as the locations of the network configuration, hostname configuration and SSH Host Keys are in the same locations as Debian and/or Ubuntu place them.
However in the upcoming Ubuntu 14.04 LTS release, there were some changes that can potentially cause VMM’s guest agent not to customize the virtual machines properly. In order to make VMM’s guest agent to provision correctly there are 2 options:
- Write your own VMM guest agent
- Modify a few file paths so Ubuntu 14.04 will look somewhat like Ubuntu 12.04 LTS in terms of network configuration
I choose the latter option. Now I do have a custom VMM Guest Agent written for FreeBSD in Perl, however creating a VMM guest agent for this specific reason isn’t a good utilization of time.
I’ve taken the following actions to make Ubuntu 14.04 to appear like Ubuntu 12.04 by doing the following:
- Remove the line in the
/etc/network/interfaces file where it references to
Surprisingly there’s only one thing you really need to do. There’s more if you decide to be even lazier and download the cloud image provided here, but it’s beyond the scope of this tidbit.
To make your Linux Template deployments easier, you now have the option of using the Windows Azure Linux Agent in place of the regular SCVMM Linux Agent.
However, please do not install both agents on your Linux template. Installing both of them can cause things to go awry, so you have been warned…