When i was working at a customer today i ran in to some strange networking issues witch took me to this HP download site this is indeed critical and should have been shouted out in big…

 

/Jorgen

If you are still running older version then 4.21 you are affected by the heartbleed SSL issue so head to HP download site and install it at once.

/Jorgen

On of the really cool new features in Hyper-V is Single Root I/O Virtualization, but not all hardware support this one easy check is using PowerShell, just run this command on the host (Get-VMHost).IovSupportReasons if you get message like below your hardware is obsolete.

 

If it looks like this its supported but not enabled, but then at least you know that you have support for it.

Now I have seen it to many times so its time for a post about the subject, people handling SCVMM and not using  templates.

First let me clarify the topic a bit, it seems that Microsoft (as always) is going for compatibility so they “optimize” for compatibility. Now most of my customers is deploying Windows and it still works, but it´s far from “optimized” for performance (That also means less load on the host, rather than only “faster” VM’s)

Now lets get down to why next next is wrong.

CPU Settings:
First out is actually a compatibility feature this will cap your VM to utilize the latest functions of the CPU but you should still use this since most likely your apps don’t use them anyway and you want to be able to migrate to another CPU revision more about this is can be found from this blog http://blogs.technet.com/b/virtualization/archive/2009/05/12/tech-ed-windows-server-2008-r2-hyper-v-news.aspx

RAM Settings:
Next is RAM default value is static 512mb RAM, to be honest how many VMs do you run with that ? so every time you run next..next..you end up with changing the amount of RAM you will use and probably changing from static to dynamic memory allocation.

NIC Settings:
Network is probably the biggest issue maker of them all.

As I said before Microsoft seems to “optimize” for compatibility, so it creates a legacy nic witch is an emulated DEC21140 this nic runs in user mode in the parent partition. This will result increase of CPU and memory usage on the host in the parent partition and also decreased performance in the VMs. Still most of my customers are using OS that have support for integrated components meaning that we want to take full advantage of the Hyper-V virtualization so delete the Legacy nic and create a new synthetic. (In VMM it just says Network Adapter)

MacAddress Setting: 
This should be handled by VMM, you can easily see if its created with VMM because then it starts with 00:1d if its created with a node or standalone host it starts with 00:15, with standalone it has a limit of 256addresses to start with meaning that you most likely to end up with macaddress conflict.

Dynamic MacAddress:
The the dynamic address that is default value this is going to give you trouble sooner or later. I can promise you that of the VMs you create is going to be used for some sort of application server and registering SPN or some other service that is using macaddress and the service will then stop, or that you are using DHCP and add reservations instead of static ip addresses. More info about the subject http://blogs.technet.com/b/jhoward/archive/2008/07/15/hyper-v-mac-address-allocation-and-apparent-network-issues-mac-collisions-can-cause.aspx

Finish:
Now you have created a new VM using next next, as I mentioned earlier Microsoft “optimize” for compatibility so you have some integrated services that’s nice, but if you are going to use this VM in an AD environment you want to disable the time synchronization under integrated services. otherwise it will get time synchronization  from both your AD as well from the service.

So what is the purpose of this post? create and use  templates/profiles and fix this from the start so you don’t have to think about this every time you create a new VM.

 

/Jorgen

A Couple of years ago I got the question – How many VMs do we have today? How much disk is presented to these ones?  How much memory do we utilize? And so on…
At the time we had VMM2008R2 pre SP1 so it was easy.

Just a couple of days ago I needed same type of info again, this time it was a little more complicated because this time it involved dynamic memory and dynamic disks and I wanted to get the “thin provisioned” disk to show how much disk that is presented and map it to what we really have.

The script will create an “Export VMs Configuration.csv” on the desktop, it will show you something like this.

Ohh almost forgot this is for VMMm2012, it “should” work on VMM2008R2SP1 as well but not tested.

Thx Niklas Goude for assistance with syntax.

$Hostname=Hostname
$Path=”$env:USERPROFILE\Desktop\Export VMs Configuration”
get-vm -vmmserver $Hostname |
sort-object name |
select-object Name, Description, OperatingSystem, CPUCount, Memory, MemoryAssignedMB, Status,
@{n=’TotalSize (Gb)’;e={($_.totalsize / 1gb).tostring(“F02”)}},
@{n=’MaxlSize (Gb)’;e={
$TotalVirtualHD=0
Foreach ($Disk in $_.Virtualharddisks) {
$TotalVirtualHD += $disk.maximumsize
}
($TotalVirtualHD/ 1gb).tostring(“F02”)}
},
HostName | export-csv -NoTypeInformation -delimiter “;” -encoding Utf8 -path $Path

/Jorgen

I have a lot of VMs on my laptop, and i need to change the switch on these machines sometimes, since I’m moving around i need to be able to change the switch that they are connected to. This is time consuming and not to mention booooring so lets look @ powershell and how this can help me.

Get-VMNetworkAdapter -VMName * | Connect-VMNetworkAdapter -SwitchName External

Problem solved, the first part is get all network connectors from * and pipe/connect it to my virtual switch named External

/Jörgen