HP Blade 460c G7 strange issues

Today i have been helping a customer with their Hyper-V R2 Cluster and patching it with the hotfix for westmere processor. one strange issue was that we found two of the blades reporting only 36 GB RAM, while the others correctly showed 72 GB RAM. As it was another consultant that was responsible for assembling the servers we first thought that they had missed to put in all DIMMs, when we loooked in the servers all slots where filled? And when we put it back in the chassi and powered on the server correctly showed 72 GB RAM! really strange.

after boot:

i used the following powershell commands in VMM powershell console to get the memory for the cluster nodes:


Get-VMHostCluster -name cluster01
Get-VMHost -VMHostCluster $VMCluster | ft Name, TotalMemory

If this happens again we will report it to the HP Support, (Edit) it happend again now..  it seems to be related to a reboot of the hosts 🙁

Microsoft Virtualization Jumpstart videos for VMware Professionals

On Technet Edge there is a couple of videos for Virtualization admins to learn more about how Microsoft Virtualization solution works.

It is a very good way to get up to speed what Microsoft has to offer and that it is a competitive solution!

from the jumpstart site:

About this Jump Start series:

The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging “team teaching” approach which makes the class as entertaining as it is educational.

Click here to watch the complete video series


 

Hyper-V 2008 R2 hotfix CSV redirect

Hi

on one of the blogs i am following, Adian Finn, he has a post about a new hotfix from Microsoft that has come out regarding a problem with Hyper-V clusters and CSV volumes in redirected mode, read more at this link and get the hotfix

Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected access

Consider the following scenario:

  • You enable the cluster shared volume (CSV) feature on a Windows Server 2008 R2-based failover cluster.
  • You create a virtual machine on the CSV on a cluster node.
  • You start the virtual machine on the cluster node.
  • You move the CSV owner to another cluster node, and you change the state of CSV to redirected access.
  • The connection that is used for redirected access is switched to another connection when one of the following scenarios occurs:
    • The cable for local area network (LAN) is disconnected.
    • The related network adapter is disabled.
    • The connection is switched by using Failover Cluster Manager.

In this scenario, you receive a Stop error message that resembles the following in the virtual machine:

STOP 0x0000007a ( parameter1 , parameter2 , parameter3 , parameter4 )
KERNEL_DATA_INPAGE_ERROR

Note

  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all “0x0000007a” Stop error messages are caused by this issue.
  • You may also receive other Stop error messages when this issue occurs. For example, you may receive a “0x0000004F” Stop error message.

Playing around with Powershell and SCVMM 2012 beta and Hyper-V R2

Hi

Have been playing a little with powershell and SCVMM2012 and with these simple lines i add 64 SCSI vhd drives á 4 GB each and then delete them all while the VM is running


$VM = Get-VM -Name "VMc2test"

for ($i=0;$i -le 63;$i++){

$vhdfilename = "vhdtest" + $i
New-VirtualDiskDrive -VM $VM -Dynamic -Filename $vhdfilename -sCSI -Size 4000 -Bus 0 -LUN $i
}

and to delete them

$vhds = @(Get-VirtualDiskDrive -VM vmc2test | where {$_.BusType -match "SCSI"})

foreach ($vhd in $vhds){

Remove-VirtualDiskDrive -VirtualDiskDrive $vhd

}

and why did i select the ones that had SCSI in the remove part, well the system vhd where the OS resides is on the IDE controller so i can safely assume that the OS will still be accessible, as some of you already know in Hyper-V the boot volume must reside on a IDE controller for the VM to boot.