Last updated by at .

  • Microsoft Azure
  • Virtual Machine Manager

Tag: Virtualization

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.

 



System Center Logo

SCVMM 2012 R2 Error 23317 When You Try to Apply Changes on VM That is Using Shared VHDX Disk

A customer of mine had a issue when he tried to change properties of Virtual Machines in System Center Virtual Machine Manager 2012 R2 which use shared VHDX, which were not created with VMM. The properties do he wanted to change had nothing to do with the Shared VHDX it self. He tried to set the availability set for these Virtual Machines.

The Error in SCVMM is the following:

Error (23317)
The operation Change properties of virtual machine is not permitted on a virtual machine that has shared virtual hard disks.

Recommended Action
The operation Change properties of virtual machine is not permitted on a virtual machine that has shared virtual hard disks.

Stanislav Zhelyazkov (Microsoft MVP) blogged about this in October 2013. The solution is pretty easy and is called PowerShell. Just do the modification but do not apply it. Use the script view in Virtual Machine Manager to get the code which would run behind the scene.

For example:

Remove all the things you don’t need and run the script:



Windows Azure Pack IaaS

Update Rollup 3 for Windows Azure Pack available

Microsoft released the Update Rollup 3 for System Center 2012 R2 with a lot of fixes for several product such as Virtual Machine Manager, Data Protection Manager or Orchestrator. This updates to directly affect private cloud deployments and public cloud deployments by service providers by bringing new functionally to the solutions. With that Microsoft also released Update Rollup 3 for Windows Azure Pack which also brings fixes and enhancements.

  • For stand-alone virtual machines (VMs) whose templates specified multiple network adapters, the tenant user cannot associate a particular network to each network adapter.Symptom: If the user is creating a VM that’s based on a template that contains multiple network adapters, the Tenant Site VM extension will automatically assign the first available network.

    Resolution: The tenant user now has the necessary user interface (UI) to select a particular network for a particular network adapter.

  • Developers who use Web Site Cloud to deploy PHP applications do not have an option to specify PHP 5.5 version.Symptom: If the user wants to deploy a PHP 5.5 application, there is no option to specify that version of PHP.

    Resolution: The user now has the PHP 5.5 version option.

  • Usage records that contain more than 4,000 characters of resource data are not supported.Symptom: If the Usage Collector encounters a usage record that has more than 4,000 characters, it fails and shuts down the usage pipeline for System Center usage data.

    Resolution: Some of the instructions in this article involve running an SQL script that will increase the size of the table field to nvarchar(max).

  • Tenants experience unexpected behavior in the portal when they create websites that have the same name in different plan subscriptions that are each on a separate Web Site cloud.Symptom: When a tenant creates two websites that have the same name on different Web Site clouds and subscriptions, the portal may display inaccurate information about one or both of the websites.

    Resolution: Users can now create websites that have the same name through separate subscriptions and clouds without seeing incorrect information about their sites or subscriptions.

  • Tenants who create an ASP.NET site by using Web Site Cloud cannot specify whether the Application Pool will be running in Classic or Integrated Mode.Symptom: When a tenant tries to create a website, the user notices that the Application Mode setting is not available. If the application requires Classic Mode, it will run the risk of failing at run time.

    Resolution: Users can now specify the Application Pool mode for their applications.

  • Administrators cannot use Fully Qualified Domain Names (FQDN) when they configure SQL Always-On Listeners, because the Windows Azure Pack Resource Provider for SQL Server does not support it.Symptom: When an administrator enters an FQDN in the SQL Extension of the Administration site, the SQL Resource Provider accepts it, but an error is returned after the provider tries to process the FQDN.

    Resolution: FQDNs are now fully supported by the Resource Provider.

  • When a tenant creates a VM, the name that is provided is not honored. Instead, a name is generated.Symptom: When tenants build a VM on premises, they expect the name that they provided to be honored as the NetBIOS name of the computer. This is not the case; the VM extension generates a name to maintain uniqueness in System Center Virtual Machine Manager.

    Resolution: Now the VM Resource Provider generates a name that’s based on the name that the user provides in the following pattern:

    Computer Name = name + “###”

    The numbers are added to the end of the name to guarantee uniqueness in System Center Virtual Machine Manager.

  • The metrics that are associated with websites that are located in separate clouds whose endpoint credentials differ from each other are sometimes not retrieved; instead an error message is displayed.Symptom: When the tenant or administrator accesses information about websites that are located in clouds that are configured to use different endpoint access credentials, you receive the following error message from the Administration site:
    The server could not retrieve metrics (Internal Server Error).

    Resolution: The monitoring service responsible for retrieving the websites data now returns the correct metrics instead of an error.

  • The SQL Resource Provider grants DB Owner permissions to tenants when during database provisioning.Symptom: When a SQL Server Database is provisioned by a tenant, the SQL Resource Provider grants DB Owner permissions to the corresponding SQL login.

    Resolution: Tenant logins that are created after you apply Update Rollup 3 are no longer granted DB Owner permissions. Existing tenant logins and already existing databases are not affected. To retroactively give existing tenant logins the same set of permissions and to remove the DB Owner level access, see the following TechNet article:

  • SQL Server Integrated Security or Windows Authentication is not supported by the Windows Azure Pack Tenant Site SQL extension.Symptom: When the tenant tries to create a database, no option for Windows Authentication is provided.

    Resolution: The SQL Tenant Site Extension now supports Windows Authentication.

For more information check out the Microsoft website: Update Rollup 3 for Windows Azure Pack



RemoteFX

GPU Requirements for RemoteFX on Windows Server 2012 R2

If your are planning a VDI (Virtual Desktop Infrastructure) deployment with Windows Server 2012 R2 Hyper-V  and you want to use physical graphics power with RemoteFX for your VDI machines fore example for CAD applications, you might wonder which cards are recommended and supported. Back in November 2013 Derrick Isoka (Microsoft Program Manager) wrote a blog post about recommendations and here is a quick summary.

RemoteFX GPU Requirements

To make use of RemoteFX with GPU acceleration on Windows Server 2012 R2 you require a compatible graphic card.

Most likely, the servers hosting the RemoteFX workloads will be located in a datacenter and as such, we recommend using passively cooled, server class graphics cards. However, it’s also acceptable to use a workstation card for testing on small deployments depending on your needs.

However the minimum requirements for the graphics cards to be used with Hyper-V RemoteFX are:

  • Direct 11.0 or later
  • WDDM 1.2 driver or later

DirectX and WDDM

There is some other point to this, in Windows Server 2012 R2 provides support for DirectX 11.0, DirectCompute and C++ AMP. Most of the graphics cards do support OpenGL 4.0 and OpenCL 1.1 or later, however these APIs are currently unsupported by RemoteFX in Windows Server 2012 R2.

Hardware and Driver Support

To find a graphics card also make sure you check the Windows Server Catalog.

RemoteFX Compatible GPUs

Microsoft did some tests and showed some of the results on the Remote Desktop Services blog.

RemoteFX Cards

  1. Best: These are server class cards, designed and certified for VDI workloads by hardware vendors like NVIDIA and AMD. They target the best application performance, experience, and virtual machine densities. Some of the cards are particularly recommended for designer and engineering workloads (such as Autodesk Inventor or AutoCad).
  2. Better: These are workstation class cards that provide acceptable performance and densities. They are especially capable cards for knowledge worker workloads (such as Microsoft Office or Internet Explorer).
  3. Good: These are lower-end cards that provide acceptable densities knowledge worker workloads.

Source: Microsoft

Performance and Scale

This is important, Microsoft also points out that GPU speed and memory, the performance and scale of your VDI deployment also depends on additional factors such as CPU, Storage and Network performance.

 



Cisco Microsoft

Cisco and Microsoft Announce Sales and Go-to-Market Agreement

At the Worldwide Partner Conference 2014 Cisco and Microsoft announced a multi-year sales and go-to-market agreement designed to modernize data centers through the delivery and acceleration of integrated solutions. This will focus on bringing a deeper integration between the datacenter technologies of both companies. This includes Cisco UCS and Nexus products as well as Microsoft’s CloudOS solutions based Windows Server, Hyper-V, System Center, SQL Server and Microsoft Azure.

Highlights:

Go-to-Market:

  • Cisco and Microsoft agree to a three-year go-to-market plan focused on transforming data centers through the delivery of integrated solutions for enterprise customers and service providers.
  • In year one, the companies will focus on six countries — the United States, Canada, UK, Germany, France, and Australia — with expansion to additional countries in the following years.
  • Cisco and Microsoft will align partner incentive programs to accelerate solutions selling via mutual channel partners.
  • Cisco and Microsoft sales teams will work together on cloud and data center opportunities, including an initial program focused on the migration of Windows 2003 customers to Windows 2012 R2 on the Cisco UCS platform.

Integrated Solutions:

  • Integrated solutions will focus on private cloud, server migration, service provider, and SQL Server 2014
  • Cisco technologies to include Cisco UCS, Cisco Nexus switching, Cisco UCS Manager with System Center integration modules, and Cisco PowerTool.
  • Cisco-based integrated infrastructure solutions will include FlexPod with NetApp and Cisco Solutions for EMC VXPEX.
  • Microsoft technology includes Windows Server 2012 R2, System Center 2012 R2, PowerShell, Microsoft Azure and SQL Server 2014
  • Cisco Application Centric Infrastructure and Cisco InterCloud Fabric to be integrated in the solutions in future releases

Source and More information: www.streetinsider.com

As you may know I am a Microsoft MVP and a Cisco Champion and I really like doing project with Cisco Hardware since they do a lot of integration with the Microsoft Stack especially System Center and PowerShell. In my opinion this could be a strong partnership and will make life of a lot of people a lot easier.



Hyper-V Share

Hyper-V is eating VMware’s lunch

During the WPC 2014 Keynote Microsoft COO Kevin Turner showed the following slide and commented it:

Hyper-V is eating VMware’s lunch

 

Hyper-V has now 30,6% market share in x86 Server Virtualization which means Microsoft won 4.6% since the release of Windows Server 2012. VMware is now at 46.4% market share which means they lost 5.1% market share since the release of Windows Server 2012 Hyper-V.

And this because of good reasons, like great features and 4 times lower cost than VMware. So if you are still running VMware you should definitely have a look at Hyper-V now!



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.