Tag: Virtual Machine

Last updated by at .

Hyper-V vNext Runtime Memory Resize

Sneak Peek into the Next Version of Hyper-V

Back in October Microsoft released the first public Windows Server Technical Preview for the next release of Windows Server. At TechEd Europe Bed Armstrong, Principal Program Manager on the Hyper-V team at Microsoft, talked about a couple of new features which are coming in the next release of Windows Server Hyper-V. This is a quick list of some of the new features we will get in the next release of Windows Server Hyper-V, there is a lot more coming until the release of Windows Server vNext and System Center vNext in 2016.

Virtual Machine Configuration Changes

Hyper-V vNext VM Configuration Files

In the next release of Hyper-V Microsoft will change the Virtual Machine configuration files. Today the Hyper-V VM configuration files had the xml file format. You were able to open the file and check and edit the virtual machine configuration inside that file, even it was never supported. By running more and more workloads virtual and in a dynamic cloud way, scale and performance gets even more critical. In the next version of Hyper-V Microsoft will change the VM configuration from the xml file to a binary file format. The new binary format brings more efficient performance at large scale. Microsoft also now includes a resilient logging for changes in the configuration files so this should protect virtual machines from corruption.

New file extensions:

  • .VMCX (Virtual Machine Configuration) – replaces the .xml file
  • .VMRS (Virtual Machine Runtime State) – replaces .bin and .vsv file

Production VM Checkpoints (Snapshots)

Hyper-V vNext Production CheckPoint

Virtual Machine Checkpoints or in older versions Virtual Machine Snapshots were a great solution to take a state of a virtual machine and save it, doing some changes and if something fails you could simply revert back to the time you took the checkpoint. This was not really supported to use in production, since a lot of applications couldn’t handle that process. Microsoft now changed that behavior now fully supports it in production environments. For this Production Checkpoints are now using VSS instead of the Saved State to create the checkpoint. This means if you are restoring a checkpoint this is just like restoring a system from a backup. For the user everything works as before and there is no difference in how you have to take the checkpoint. Production Checkpoints are enabled by default, but you can change back to the old behavior if you need to. But still using Checkpoints brings some other challenges, like the growing .avhdx file, which still apply.

Hyper-V Replica support for Hot Add of VHDX

Hyper-V Replica was one of the greatest new features in Windows Server 2012 Hyper-V. In Windows Server 2012 and Windows Server 2012 R2 Hyper-V, if you have hot added a VHDX file to a Virtual Machine, replication failed. In the next version of Hyper-V when you add a new virtual hard disk to a virtual machine that is being replicated, it is automatically added to the not-replicated set so replication continues to run and you can then online update this set with via PowerShell and the VM will automatically resynchronize and everything works as expected.

Hot add / remove of Virtual Machine Memory

Hyper-V vNext Runtime Memory Resize

In Windows Server 2012 R2 Hyper-V you could decrease the Minimum Memory and increase the Maximum Memory of a Virtual Machine using Dynamic Memory while the VM was running. In the next version of Hyper-V you can now increase and decrease the Memory assigned to virtual machines while they are running, even if they are using static memory.

Hot add / remove of virtual network adapters

Hyper-V vNext Hot Add and Remove Virtual Network Adapters

This was maybe the feature VMware fan boys all over the world have used against Hyper-V. However I didn’t really saw a lot of customers doing this, but it is great that you can now hot add and remove network adapters from Virtual Machines.

Virtual Network Adapter Identification

Hyper-V vNext Virtual Network Adapter Identification

For me more important than hot add or remove virtual network adapters is this feature. When dealing with automation you are always happy you can identify different network adapters. For the Hyper-V hosts we have different solutions such as Consistent Device Naming (CDN), sort by PCI slot using PowerShell and other options to identify network adapters. But we didn’t really have a great solution for Virtual Machines. With Network Adapter Identification this changes. You can name individual virtual network adapters in the virtual machine settings and see the same name inside the guest virtual machine.

PowerShell on the Hyper-V Host

PowerShell in the guest

Hyper-V Manager Improvements

Finally, this is something which is not a problem in most environments , since we know how things work. But a lot of people which are Hyper-V beginners coming from VMware or other platforms, they have some simple troubles with Hyper-V Manager. In the next version there are a couple of create improvements which make things a lot easier.

  • Hyper-V Manager is now connecting via WinRM instead of WMI
  • Support for alternate credentials (Requires that you have CredSSP enabled on the server and client)
  • Connected to Hyper-V Hosts via IP address
  • Mange Windows Server 2012 Hyper-V, Windows Server 2012 R2 Hyper-V and the next version of Hyper-V from the latest console

Power Management improvements

SleepStudy Report Connected Standby Transitions

Microsoft updated the hypervisor power management model to support new modes of power management. And this is one of the reasons I run Windows 10 Technical Preview on my Surface Pro 3. Surface Pro 3 is a device which can run Connected Standby, but if you install Hyper-V on Windows 8.1 Connected Standby stops working. In the next version of Hyper-V Connected Standby will work.

Rolling Cluster Upgrade

Hyper-V vNext Rolling Cluster Upgrades

With this new feature you are finally able to upgrade a Hyper-V Cluster from Windows Server 2012 R2 Hyper-V to the next version of Hyper-V without new hardware, no downtime and the ability to roll-back safely if needed. In Windows Server 2012 R2 you had to create a new Hyper-V Cluster while the old Hyper-V Cluster was still running and migrate a Hyper-V Cluster via Cluster Migration Wizard or Live Migration. You can now have Windows Server 2012 R2 Hyper-V Hosts and the next version of Hyper-V running in the same Hyper-V Cluster. To make this scenario possible, the Hyper-V team had to do some changes to the Virtual Machine Upgrade Process

New Virtual Machine Upgrade Process

Hyper-V vNext Update VM Configuration Version

To support Rolling Cluster Upgrades Microsoft had to make some changes to the Virtual Machine Upgrade Process. In the current versions of Hyper-V, Virtual Machines were automatically upgraded from the old to the new version, which means that if you once moved a Virtual Machine to a new Hyper-V host you couldn’t move it back again. In a mixed cluster environment this does not work. In the next version of Hyper-V, Virtual Machines will not be upgraded automatically. Upgrading a virtual machines is a manual operation that is separate from upgrading the Hyper-V host. This allows you to move virtual machines back to earlier version of Hyper-V until they have been manually upgraded.

New way how VM Drivers (integration services) get updated

Since Windows Server 2012 R2 Hyper-V, VM drivers (integration services) were updated with each new host release, and it was required that the VM driver version matches the host version. When new Hyper-V integration services were shipped you had to update the Hyper-V host and form there you could upgrade the VM drivers inside the virtual machine. With Windows Server vNext Hyper-V Microsoft brings VM driver updates over Windows Update. This means also that you now don’t have to have the VM integration services matching the host version, you simply need the latest version of the integration services released.

Secure Boot Support for Linux

Microsoft is pushing hard to bring more and more supported for Linux operating systems such as dynamic memory and other features. With Hyper-V vNext Microsoft bring Secure Boot support for Linux which works with Ubuntu 14.04 (and later) and SUSE Linux Enterprise Server 12.

PowerShell to enable Secure Boot Support for Linux:

Distributed Storage QoS

Hyper-V vNext Storage QoS

In Windows Server 2012 R2 Hyper-V we got the possibility to limit maximum IOPs for an individual virtual hard disk which was a great feature. Everything worked great when you were running the Virtual Machine on a single Hyper-V host, but when you were running multiple Hyper-V hosts with multiple Virtual Machine against the same storage, the Hyper-V host didn’t know that he had to compete with other servers for Storage IOPs or bandwidth. For example the scenario of a minimum IOPs setting did only work on standalone Hyper-V servers. With the next release of Hyper-V and Windows Server Microsoft adds a lot of new stuff. Together with the Scale-Out File Server and Storage Spaces, Microsoft now allows you to define IOPs reservation for important virtual hard disks and a IOPs reserve and limit that is shared by a group of virtual machines / virtual hard disks. This intelligence, build by Microsoft Research, enables a couple of interesting scenarios especially in service provider environments and large scale enterprises.

Virtual Machine Compute Resiliency

Hyper-V vNext Compute VM Reciliency

Microsoft invested heavily into VM resiliency, especially to hardware failure. One of them is the VM Compute Resiliency feature. This feature allows Virtual Machines to run on a host even if the cluster node is not available to the other nodes in the cluster. For example in Windows Server 2012 R2, if the cluster service couldn’t reach the node in the cluster for 30 seconds, the cluster would failover all the virtual machines to another node. If the same things happens in Windows Server vNext Hyper-V, the node would go into isolated mode for the next 4 minutes (default setting) and when the node comes back in four minutes all the virtual machines will still be running. If it doesn’t come back within four minutes the VMs will failover to another node. If a node is flapping from Isolated Mode to running the cluster service will set the node to quarantined and will move all the virtual machines from the node to another node. This should help keep your workloads running even if there are some hardware or network failures.

Evolving Hyper-V Backup

If you are working in IT you know that Backup is always a issues. And things didn’t really get better by running Virtual Machines running on Storage Systems. With the next release of Hyper-V Server Microsoft will release a completely new architecture to improve reliability, scale and performance of Virtual Machine backups. There are three big changes in the backup architecture:

  • Decoupling backing up virtual machines from backing up the underlying storage.
  • No longer dependent on hardware snapshots for core backup functionality, but still able to take advantage of hardware capabilities when they are present.
  • Built in change tracking for Backup of Virtual Machines

RemoteFX

Microsoft also did some improvements on RemoteFX which now includes support for OpenGL 4.4 and OpenCL 1.1 API. It also allows you to use larger dedicated VRAM and VRAM in now finally configurable.

Hyper-V Cluster Management

This is maybe something you will never use by yourself but there is another great improvements in terms of automation and development. If you have ever used WMI against a Hyper-V Cluster you always had to run it against every Hyper-V Host in the cluster to get all the information. In the next version of Hyper-V you can finally run WMI against Hyper-V Cluster and it will handle it as it would be a single Hyper-V host, so you get all the information from all hosts in the cluster.

This was a quick overview over just some of the feature and improvements which are coming in the next release of Windows Server Hyper-V which will be released in 2016. There will be much more coming until Microsoft officially releases the next version of Hyper-V and of course some of the stuff I wrote about will be improved as well.

If you want to know more about the next version of Hyper-V checkout Ben Armstrong’s TechEd Europe session or visit some of our TechNet events.

 



Microsoft Virtual Machine Converter 3.0

Microsoft releases Microsoft Virtual Machine Converter 3.0

Microsoft today released the next version of the Microsoft Virtual Machine Converter (MVMC). (MVMC) is a Microsoft-supported, stand-alone solution for the IT pros or solution provider who wants to convert virtual machines and disks from VMware hosts to Hyper-V hosts and Microsoft Azure.

In MVMC 3.0 Microsoft adds the ability to convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a Virtual Machine. This feature was highly claimed by the community, since the P2V (Physical to Virtual) Migration feature was removed in System Center Virtual Machine Manager 2012 R2.

MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2 or Service Management Automation. It can also be invoked through the Windows PowerShell command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.

This tool can not only help you to migrate from VMware or physical computers to Hyper-V, it also allows you to directly upload the Virtual Machine to Microsoft Azure.

MVMC3 migrate to Hyper-V or Azure

You can get the new version of the Microsoft Virtual Machine Converter 3.0 in the Microsoft Download Center.



centos hyper-v

Best Practices for running Linux on Hyper-V

Sometimes I just need my blog as a reminder or a database to find something in a few months so this is exactly one of this blog posts. Microsoft has a TechNet article where they describe the best practices for Linux VMs running on Hyper-V 2012 or Hyper-V 2012 R2. The article is a list of recommendations for running Linux virtual machine on Hyper-V.

Right now they have 4 recommendations on the list (Source Microsoft TechNet):

  • Use static MAC addresses with failover clustering.
  • Use Hyper-V-specific network adapters, not the legacy network adapter.
  • Use I/O scheduler NOOP for better disk I/O performance.
  • Add “numa=off” if the Linux virtual machine has more than 7 virtual processors or more than 30 GB RAM.

 



Azure Preview Virtual Machines

Virtual Machines IaaS now available in the Azure preview portal

Some months ago Microsoft lunched a new preview portal for Microsoft Azure, with a cool new design and features. The IaaS or Virtual Machine services was missing from the portal. A week ago Microsoft announced to add some enhancements to the preview portal including Virtual Machines. Now today Microsoft rolled out the enhancements to the portal. with other improvements:

  • IaaS Functionality: Create, deploy, monitor and manage rich virtual machines’ based applications, and manage virtual networks within a fully customizable Portal experience. In addition to creating simple virtual machines, we are adding the ability to automate the deployment of rich multi-machine application templates with a few clicks. With this, deploying a multi-tier, highly-available SharePoint farm from the portal will be a few clicks away!
  • Resource Group enhancements: Manage infrastructure services like virtual machines and virtual networks along with platform services like web sites and databases, all within the same Resource Group, as a single application. This level of flexibility and control is an example of how Azure is leading the way in blurring the lines between infrastructure and platform services, giving customers the choice to pick the best platform for their application needs.
  • Azure Image Gallery Updates: The completely re-imagined Azure Gallery is more powerful with the addition of several new virtual machine images that enable you to provision dev/test servers or production applications in minutes. The new virtual machine images and templates take the guesswork out of building, orchestrating and deploying complex applications, thus letting you focus on creating business value instead of managing the infrastructure.
  • Azure SQL Database: Customers can manage their Azure SQL Databases within the Portal, consistent with other Azure services. This includes provisioning databases across Web and Business (currently in general availability) and Basic, Standard, and Premium (currently in preview).

Checkout the blog from  Director, Product Marketing, Microsoft Azure to learn more.

Azure Preview Portal Virtual Machine



Azure Site Recovery

Microsoft Azure Site Recovery Preview

Microsoft today announced the preview of Disaster Recovery to Azure called Microsoft Azure Site Recovery. This also replaces HRM (Hyper-V Recovery Manager). Microsoft Azure Site Recovery (ASR) allows you to orchestrate disaster recovery to a second site or directly to Azure.

Microsoft ASR

Both solutions use Microsoft on-prem technology like Windows Server Hyper-V Replica and System Center Virtual Machine Manager and you can start using them via the Microsoft Azure Management Portal.

In addition to enabling Microsoft Azure as a DR site in multiple geographies, this preview also includes an impressive list of features for enabling virtual machine replication to Azure:

  • At-Scale Configuration
    You can configure the protection and replication of VM settings in a private cloud and configure and connect on-prem networks with Azure Networks. Those VM’s are then only replicated to customer-owned and managed geo-redundant Azure Storage.
  • Variable Recovery Point Objective (RPO)
    This feature provides support for near-synchronous data replication with RPOs as low as 30 seconds. You can also retain consistent snapshots at desired frequency for a 24-hour window.
  • Data Encryption
    VM Virtual Hard Disks can be encrypted at rest using a secure, customer-managed encryption key that ensures best-in-class security and privacy for your application data when it is replicating to Azure. This encryption key is known only to the customer and it is needed for the failover of VM’s to Azure. Simply put: All of this service’s traffic within Azure is encrypted.
  • Self-Service Disaster Recovery
    With ASR you get full support for DR drills via test failover, planned failover with a zero-data loss, unplanned failover, and failback.
  • One-Click Orchestration
    ASR also provides easy-to-create, customizable Recovery Plans to ensure one-click failovers and failbacks that are always accurate, consistent, and help you achieve your Recovery Time Objective (RTO) goals.
  • Audit and Compliance Reporting with Reliable Recovery
    DR testing and drills can be performed without any impact to production workloads. This means you get risk-free, high-confidence testing that meets your compliance objectives. You can run these non-disruptive test failovers whenever you like, as often as you like. Also, with the ability to generate reports for every activity performed using the service, you can meet all your audit requirements.

ASR does not only help you in terms of Disaster Recovery, it also allows you to quickly and easily migrate your Virtual Machines to Azure or create a new dev environment.

Check out the ASR session at TechEd 2014 and Brad Andersons blog about the release of the Azure Site Recovery Preview.

Once you’re ready to see what ASR can do for you, you can check out pricing information, sign up for a free trial, or learn more about the product specs.

 

 



SMA Author RunBooks in Windows Azure Pack

Service Management Automation – The Next Step in Cloud and Datacenter Automation

With System Center Orchestrator Microsoft already had an datacenter automation engine in his portfolio. Microsoft acquired Opalis added it to the System Center Suite, after a while Microsoft renamed Opalis to System Center Orchestrator. As we have a look at modern datacenters and our cloud environment automation is a key part of it. With the latest release of System Center 2012 R2 and Windows Azure Pack, Microsoft release a new automation engine based on PowerShell Workflows called Service Management Automation (SMA).

Windows Azure Pack Automation with SMA

SMA is integrated as one of the key Resource Provider in Windows Azure Pack, and allows you to manage your PowerShell Workflows in so called Runbooks. Service Management Automation enhances PowerShell Workflows in several different ways.

  • Centralized management
  • Centralized store for variables, credentials, certificates, connections, modules, workflows, checkpoints and schedules.
  • High availability workflow execution
  • Versioning
  • Odata web service (HTTP API)
  • Historical view of workflow jobs and their output

Architecture

SMA is build form several different components.

  • Web Service – HTTP/HTTPS API which distributes runbook jobs to runbook workers and builds the connection to Widnwos Azure Pack
  • Runbook worker – Executes Runbooks
  • PowerShell module – Enables SMA to be managed by Windows PowerShell
  • Windows Azure Pack – UI for administrators to create and manage runbooks
  • SQL database – Store for Runbooks and settings

SMA Architecture

  • The Automation web service communicates with Windows Azure Pack and authenticates users.
  • The SQL Server databases store and retrieve runbooks, runbook assets, activities, integration modules, and runbook job information.
  • Runbook workers run the runbooks, and they can be used for load balancing.
  • The management portal in Windows Azure Pack is where you author, debug, and start and stop runbooks.

Source: TechNet

One of the greats enhancements Service Management Automation together with Windows Azure Pack brings is the possibility to link runbooks to SPF and VMM activates used in the Virtual Machine Cloud. What does this mean? For example you link a runbook to a Create Virtual Machine activity, so every time a VM gets created the runbooks starts and also gets as input object the VM which was created. This is just one example what you can do with SMA and Windows Azure Pack VM Cloud, there are a lot of other possibilities as well.

If you compare System Center Orchestrator to Service Management Automation, SMA looks a little bit more complex if you have used a lot of Integrations Packs in SCORCH but if you have done a lot of work in PowerShell you will really like SMA and see the advantages of it.

Service Management Automation does not offer an user interface by itself, instead it is using the Windows Azure Pack portal, where admins can author, run, schedule and link runbooks.

SMA Author RunBooks in Windows Azure Pack



Veeam

Two new Veeam Webinars about Hyper-V

A couple of week ago I was presenting for Veeam about Windows Server 2012 R2 Hyper-V and Veeam Backup & Replication v7 R2. The webinar was in German and during a huge request from people about an English webinar, Veeam offered to do the same webinar in English. Together with Aseem Anwar I will present about the new feature in Windows Server 2012 R2 Hyper-V showing the following enhancements:

  • Storage
  • Networking
  • Management
  • Live Migration
  • Generation 2 Virtual Machines
  • And more

The webinar will take place on Thursday 24 April 11:00 CEST (10:00 BST) and you can register free on the Veeam website. The webinar will be held in English.

 

Register

Register for the free webinar on Windows Server 2012 R2 Hyper-V and Veeam Backup & Replication v7 R2. (English)

 

There will be also a second webinar about Windows Server 2012 R2 Hyper-V and Veeam Backup and Replication in German together with Moritz Höfer. This webinar will focus on small businesses and will show you how you can make use of Hyper-V and Veeam Backup & Replication in a small business environment.

The webinar will take place on Thursday 23 April 15:00 CEST and you can register free on the Veeam website. The webinar will be held in German.

 

Register

Register for the free webinar on Windows Server 2012 R2 Hyper-V and Veeam Backup & Replication v7 R2. (English)

 

If you have any are interested in Hyper-V 2012 R2 or Veeam Backup & Replication or how the products work together, you should definitely join this free webinar.