Next week Teched Europe kicks of and that will tons of great sessions! Sadly I can´t be there this year but family comes first and the week after that I will be at the MVP Summit in Redmond!
But whats so great with the Microsoft conferences is that you can be part of whats happening even if you cannot make it onsite! Channel 9 will be live broadcasting and also all cool sessions will be uploaded!!
Here are some of the sessions that either if you will be in Barcelona or if you want to check out the recording later should watch/attend!!
As I am an Hyper-V MVP I of course have focus on virtualization, but as my friend and former colleague Fredrik Nilsson says: “attend a session on something you do not know” so here is my top 10 to watch out for!
Tuesday, October 28 1:30 PM – 2:45 PM Room: Hall 8.1 Room L
Wednesday, October 29 12:00 PM – 1:15 PM Room: Hall 8.0 Room B1
Wednesday, October 29 10:15 AM – 11:30 AM Room: Hall 8.1 Room H
Wednesday, October 29 5:00 PM – 6:15 PM Room: Hall 8.1 Room L
Wednesday, October 29 10:15 AM – 11:30 AM Room: Hall 8.0 Room A2
Tuesday, October 28 5:00 PM – 6:15 PM Room: Hall 8.1 Room J
Thursday, October 30 3:15 PM – 4:30 PM Room: Hall 8.0 Room C1
Tuesday, October 28 3:15 PM – 4:30 PM Room: Hall 8.1 Room L
Thursday, October 30 10:15 AM – 11:30 AM Room: Hall 8.0 Room D1
Wednesday, October 29 10:15 AM – 11:30 AM Room: Hall 8.0 Room B1
There are of course a ton of more sessions and I will probably do a revision once I have watched the recordings
And during the week follow TechEd in social media :
Today I have been doing some work at a customer creating a Hyper-V 2012 R2 Cluster and starting to live migrate VM´s from their Hyper-V 2012 Cluster.
Doing that from VMM gave me some errors and here is the solution so that if you happens to get into the same problem
First of all, when added the new cluster to VMM I tried to live migrate a VM but got this error (12700)
After a quick search on the net I found this blog post explaining the need to configure kerberos live migration and delegation between the hosts and also that the hosts needs an “Host Management Credentials” account set up in the properties! I had already set up the hosts to use Kerberos and delegation between and still got the above error but when checking the Run As account it was empty:
The problem as you can see though, it is greyed out and cannot be altered, I tried to do add an account through PowerShell and there I got an answer that it had to be set on the cluster,
checking on the cluster properties in the VMM console there is nowhere to add or see the management credential
So back to PowerShell again:
$runas = Get-SCRunAsAccount "SCVMM Admin"
$clu = Get-SCVMHostCluster -Name HYPCLU
Set-SCVMHostCluster -VMHostCluster $clu -VMHostManagementCredential $runas
And when this is set all the cluster hosts have this credential set and then when doing a Live Migration it succeeded
The day has come with a new version of the free conversion tool from Microsoft, MVMC 3.0 have been released.
There where some bashing on the net when the VMM 2012 R2 was released and the P2V functionality was removed from that version and some crazy ideas using a secondary VMM 2012 SP1 to do the P2V migrations and then importing into the VMM 2012 R2 was suggested, well that time is now no more now
The installation is quite straightforward with the msi and just a simple wizard.
Once installed You can start exploring the new options including the new P2V.
When doing a P2V the MVMC will install an agent on the source and when doing a P2V the source have to be online during the migration.
And then you go through the wizard and start the conversion
Once it is finished, you find the VM in your Hyper-V host and can start it, but beware that the wizard does not ask if you want to shut down your source after migration so that is something you have to take care of before starting that P2V´d VM
But wait you say, I have 100 vm´s and will die if I use the wizard for all of them! Then you can use the PowerShell module and automate the conversion:
The operating systems that is supported migrating with the MVMC are (although only Windows with the P2V):
- Windows Server 2012 R2 Standard x64
- Windows Server 2012 R2 Datacenter x64
- Windows Server 2012 Standard x64
- Windows Server 2012 Datacenter x64
- Windows Server 2008 R2 Standard x64
- Windows Server 2008 R2 Enterprise x64
- Windows Server 2008 R2 Datacenter x64
- Windows Server 2008 R2 SP1
- Windows Server 2008 Standard (x86/x64)
- Windows Server 2008 Enterprise (x86/x64)
- Windows Server 2008 Datacenter (x86/x64)
- Windows 8 Enterprise (x86/x64)
- Windows 8 Pro (x86/x64)
- Windows 7 Enterprise (x86/x64)
- Windows 7 Professional (x86/x64)
- Windows 7 Ultimate (x86/x64)
- Windows Vista Enterprise x86/x64
- Red Hat® Enterprise Linux® 6 (x86/x64)
- Red Hat Enterprise Linux 5 (x86/x64)
- Ubuntu 12.04 (x86/x64)
- Ubuntu 10.04 (x86/x64)
- SUSE® Linux Enterprise Server 11 (x86/x64)
- CentOS 6 (x86/x64)
- CentOS 5 (x86/x64)
- Debian GNU/Linux 7 (x86/x64)
- Oracle Linux 6 (x86/x64)
- Oracle Linux 5 (x86/x64)
Good luck in your migrations!!
So today Microsoft released their technical previews of Windows 10 and also of Windows Server
As an Hyper-V interested guy I wanted to check out some things in this build, there have already been a blog post about cool features such as rolling cluster updates so that you can have different versions in the Hyper-V cluster and keep the VM´s up all time during an upgrade.
There are some more info on the technet site discussing the different new features:
I downloaded the Windows Server technical preview from my MSDN and started the installation, it was really fast (and yes I have an SSD)
In this screendump you can see that 5.0.9841.0 version of the PowerShell is included in the server technical preview
And as you can see there is 182 cmdlets for the new Hyper-V PowerShell module
After you have moved your 2012 or 2012 R2 VM´s you can update the VM configuration to the latest version but beware that once done that you cannot move those VM´s back to the old Hyper-V host.
A new feature in this version is also that you can make snapshots (yea I still not like Checkpoint name) that uses VSS, and if that is not available it will fail-back to standard snapshots
And still in this version you can via PowerShell enable Processor compability for those Windows NT server
When I get some more time I will dig some more into it and do a follow up post
I was talking to some guys with a quite solid VMware background and they were working on setting up a Hyper-V cluster with Windows Azure Pack as frontend.
Their environment was a traditional setup with Hyper-V hosts connecting to a SAN with FC thus using CSV´s for storing the VM´s. All VM´s including their management was configured on these hosts.
As a best practice they ran the Failover Cluster Validation (and yes you should run it or you won’t get support) but as I will show you, they had an unwanted restart of their VM´s including the one they had failover cluster manager started so look and think twice before starting that validation with all tests!
with no HA – VM´s there are not so much to think about but once you add VM´s there is, and it can have some consequences…
If you in the wizard add the CSV volume to the test you can see the warning showing that you will get the VM´s stopped doing the validation,
Going next in the wizard and then going back the warning has disappeared!
But of course in the Confirmation it still says that the VM roles will be stopped but if you are in a hurry and start the validation then all VM´s on the CSV volumes will be stopped and then started and maybe that was not what you had intended from the beginning!
So look and select the options carefully when doing a validation of a cluster with production workloads in
Yesterday I was testing Bare-Metal deployment on a VMM 2012 R2 with a new Hyper-v image and got the error 21161 during the process of making a physical machine into a Hyper-V Server.
I did of course check the library server (which was the same as the VMM server) and also that the vhdx that contains the Hyper-V image was in the library. I also checked the profile where the reference to the VHDx is and everything looked good.
The error was resolved when checking out the library server properties and changing to a host group instead of the default.
I have been deploying servers from this VMM before and why it started to complain right now is a mystery and I will dig and see if I can find the reason and if I do you will get an update on the blog, but now you know how to get it running
Update: Daniel Clarke mentioned my fix, In the VMM I have as this error occured I had not updated to UR3 during the time between the deployments which would otherwise had maybe explained the error. I have now updated the server to UR3 and can still do bare-metal deploy.
I have been helping a customer a while with their Hyper-V environment and now I saw on twitter that HP had new Emulex drivers that could be downloaded so I thought that I should give it a try, there has been quite a storm about the problems with VMQ and Emulex and if you want to read more about that you can check out this link to my friends at Hyper-V.nu . My experience of this problem is that it have been on Gen8 HP blades with a newer Emulex networking on them. Right now I only had G7 to test on.
As a best practice I run the Hyper-V hosts in Core but that did not give me any issues when installing (yes I use VMM bare-metal deployment and will after verified success update that to have this latest drivers )
As it is networking drivers I lost my RDP session for a few seconds before it was fully installed and then I could see the result
And checking with powershell Get-NetAdapter I can verify that the GUI is not lying
And also you can see that the VMQ is enabled for my two NIC´s
Here you can find the HP drivers for in this case a HP BL460 G7 .
In my latest blog I was exploring the possibility to get a Redhat Linux to work in a generation 2 VM and I was also explaining that I had some issues with the CentOS version 7 that is currently being developed and that issue was with the EFI boot and it was malfunctioning!
Now as of yesterday 25 of June when there was a new release I could actually get a working CentOS 7 in a generation 2 VM on my lab environment!
So to get the fresh build installed on a Gen2 HyperV 2012 R2 VM you can do the following,
here I found the Boot ISO -> http://buildlogs.centos.org/centos/7/os/x86_64-latest/images/ and downloaded the boot.iso and configured it to be used for boot in my test-VM and as I described in the other post I unchecked the Secure boot also
Once booted I connected the network and then added the path to the repository
The path to be added was http://buildlogs.centos.org/centos/7/os/x86_64-latest/ , by using -latest in the path you will get the latest build instead of some old maybe not so well working version, as described on their page the distribution is still being developed
And then choosing what roles to install and partitioning of the disk and then start the installation
Once installed you can see that it now nicely boots into CentOS and I can log in
And you can see that it utilizes the Dynamic Memory function of Hyper-V also
I was reading the post from Ben Armstrong how he installed and configured a Ubuntu Linux VM to work under a generation 2 VM.
And after that I wanted to try this with either Red Hat Enterprise Linux 7 or CentOS 7 as they would incorporate the Linux integration components that would be needed for being able to let go of that VM BIOS legacy generation 1 Hyper-V VM :-). Red Hat has released their 7 but CentOS is still in buildmode and thus this would be done on their “nightly build” as described on the site http://seven.centos.org and I did take a test with the current release but got an error during install with the EFI Boot so I went for the Red Hat and tried with that.
So Downloading the Redhat ISO and creating a VM was the first steps, If you do not have an account at redhat you can sign up and download a trial.
And then I created a VM and as Ben showed I disabled secure boot and added the ISO to boot:
After that I booted the VM and connected the network and configured the settings and choosed a Server with A GUI
The installation was successful and I could reboot with no warnings or errors
Then once the installation was complete I could start a browser and test and as you can see it is a Generation 2
I will during the next couple of days check out the new builds of CentOS and see if my error will be fixed and I can create a Gen2 VM of that one also
So I have been during these two last days been in deep waters to find out a customers demands and the possibility to add more than one external IP to the same NVGRE enabled VM network within WAP and VMM and the Hyper-V Network Virtualization Gateway this as the ports from the external application the customer has cannot be altered and they need to access several different VM´s simultaneously.
Described in this visio diagram the customer wish is:
As you maybe know, within the VMM when you have configured the HNV there is no possibility to add more external addresses in the GUI and configure port forwarding.
So how to do this then, well there is a way and that is called PowerShell on the HNV Gateway and first you add the external address and then add the NAT rules
# This command add an external IP to the HNV GW
Add-NetNatExternalAddress -NatName 59f91b1e-66c3-4372-96f1-ecdf2b2073d5 -IPAddress 10.88.24.88 -PortStart 1 -PortEnd 65535
# This command adds the actual NAT Port rules
Add-NetNatStaticMapping -NatName 59f91b1e-66c3-4372-96f1-ecdf2b2073d5 -Protocol TCP -ExternalIPAddress 10.88.24.88 -ExternalPort 475 -InternalIPAddress 192.168.50.3
Add-NetNatStaticMapping -NatName 59f91b1e-66c3-4372-96f1-ecdf2b2073d5 -Protocol TCP -ExternalIPAddress 10.88.24.88 -ExternalPort 3389 -InternalIPAddress 192.168.50.3
Add-NetNatStaticMapping -NatName 59f91b1e-66c3-4372-96f1-ecdf2b2073d5 -Protocol TCP -ExternalIPAddress 10.88.24.88 -ExternalPort 80 -InternalIPAddress 192.168.50.3
Here is a screendump of an addition of a port rule:
To get the NatName I added the first external IP and Port rules through VMM and then I could use that information when creating the rest config from within the HNV gateway.
The following cmdlets are available on the HNV GW
Observe though that when adding these things directly in the HNV GW you cannot manage these rules and IP addresses in Windows Azure Pack portal or VMM!