Archive for the ‘SCVVM’ Category
If you have improvements, please mention it in the comments or write me an e-mail specifying which value needs to be altered and some proof of you statement, a MS website, video, etc.
[
http://www.vmguru.nl/wordpress/wp-content/uploads/2012/09/Hypervisor-comparison.pdf
]
Updated to the latest two versions, Citrix XenServer 5.6 & 6.0, Microsoft Hyper-V 2008 R2 SP1 & 2012 and VMware vSphere 5.0 & 5.1.
At manufacturer’s websites and in the blogosphere there are many hypervisor comparisons which only compare hypervisors based on a single driver (performance, features or cost). In my opinion it’s a bit more complicated than that. After the everlasting discussion on make-believe cheaper Microsoft Hyper-V and Citrix XenServer implementations, I spend a fair deal of my time explaining to colleagues and clients that this is a hoax and that cost is not the only reason to base their decision on. Especially in the case of XenServer the choice and the long term effects make it a little bit more complicated.
Now you probably think ‘These VMGuru.nl guys are VMware fans so here we go again‘ but the opposite is true. Like Chris I think every situation has its own ideal solution and you should select the hypervisor based on well-considered selection criteria and because my employer, Imtech ICT, focuses on clients with 500+ workstations/employees these criteria are Enterprise-class hypervisor selection criteria.
==
I’m not found word "dynamic" ( and info about Dynamic Memory in MS Hyper-V) in Enterprise Hypervisor comparison v4.2 2012-10-01 ( 2012/09/Hypervisor-comparison.pdf 01 Oct 2012 17:55:04 GMT )
==
With SP1 for Hyper-V R2 Microsoft added a feature that is called Dynamic Memory, which adjusts the amount of memory
available to virtual machines depending on the needs of each virtual machine. Which is much like but not entirely
similar to hot-add/remove.
==
- Only legacy (emulated) 100Mbit Ethernet
- Only 4 emulated IDE disks which are then quite slow, no paravirt SCSI controller
- 1 vCPU and no dynamic memory (Linux doesn’t support the later one today, only Windows guests)
==
We have need for a temporary legacy setup here at the shop.
We used a Windows Server 2000 Standard SP2 CD ISO to install the base OS.
We have an ISO based DVD with every conceivable Microsoft service pack and needed critical update on it that we use to service our VMs. We needed to mount that ISO and update to Service Pack 4 before we could get the Hyper-V Integration Services installed.
. . .
Legacy operating system support
Q. The virtual machine settings include a processor option which limits processor functionality to run an older operating system such as Windows NT on the virtual machine. What does this feature actually do?
A. This feature is designed to allow backwards compatibility for older operating systems such as Windows NT 4.0 (which performs a CPUID check and, if CPUID returns more than three leaves, it will fail). By selecting the processor functionality check box Hyper-V will limit CPUID to only return three leaves and therefore allow Windows NT 4.0 to successfully install. It is possible that other legacy operating systems could have a similar issue.
Q. Does this mean that Windows NT 4.0 is supported on Hyper-V?
A. Absolutely not. Windows NT 4.0 is outside its mainstream and extended support lifecycle and is not supported on Hyper-V and no integration components will be released for Windows NT 4.0.
Q. But one of the stated advantages for virtualisation is running legacy operating systems where hardware support is becoming problematic. Does this mean I can’t virtualise my remaining Windows NT computers?
A. The difference here is between “possible” and “supported”. Many legacy (and current) operating systems will run on Hyper-V (with emulated drivers) but are not supported.
. . .
- RHEL 5.7 (x86 and x64)
- RHEL 5.8 (x86 and x64)
- RHEL 6.3 (x86 and x64)
- CentOS 5.7 (x86 and x64)
- CentOS 5.8 (x86 and x64)
- CentOS 6.3 (x86 and x64)
==
Microsoft have made strategic investments in interoperability that continues to reap rewards and here’s another big one TODAY with Red Hat. Today, Red Hat has announced the beta of RHEL 5.9 which includes the Linux Integration Services for Hyper-V built-in.
==
==
This means that RHEL will include the following Linux Integration Components for Hyper-V “inbox”:
1. Driver support: Linux Integration Services supports the network controller and the IDE and SCSI storage controllers that were developed specifically for Hyper-V.
2. Fastpath Boot Support for Hyper-V: Boot devices now take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
3. Timesync: The clock inside the virtual machine will remain accurate by synchronizing to the clock on the virtualization server via Timesync service, and with the help of the pluggable time source device.
4. Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager by using the “Shut down” command.
5. Heartbeat: This feature allows the Hyper-V to detect whether the virtual machine is running and responsive.
6. Key Value Pair (KVP) Exchange: Information about the running Linux virtual machine can be obtained by using the Key Value Pair exchange functionality on the Hyper-V host.
7. Integrated Mouse Support: Linux Integration Services provides full mouse support for Linux guest virtual machines.
==
The Microsoft press release
http://blogs.technet.com/b/openness/archive/2012/09/21/windows-server-hyper-v-drivers-supported-in-red-hat-enterprise-linux.aspx
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5-Beta/html/5.9_Release_Notes/virtualization.html
==
Chapter 9. Virtualization
Inclusion of, and Guest Installation Support for, Microsoft Hyper-V Drivers
Integrated Red Hat Enterprise Linux guest installation, and Hyper-V para-virtualized device support in Red Hat Enterprise Linux 5.9 on Microsoft Hyper-V allows users to run Red Hat Enterprise Linux 5.9 as a guest on top of Microsoft Hyper-V hypervisors. The following Hyper-V drivers and a clock source have been added to the kernel shipped with Red Hat Enterprise Linux 5.9:
a network driver ( hv_netvsc)
a storage driver ( hv_storvsc)
an HID-compliant mouse driver ( hid_hyperv)
a VMbus driver ( hv_vmbus)
a util driver ( hv_util)
a clock source (i386: hyperv_clocksource, AMD64/Intel 64: HYPER-V timer)
Red Hat Enterprise Linux 5.9 also includes a guest Hyper-V Key-Value Pair (KVP) daemon ( hypervkvpd) that passes basic information, such as the guest IP, the FQDN, OS name, and OS release number, to the host through VMbus.
==
http://blogs.technet.com/b/port25/archive/2012/08/09/windows-server-hyper-v-is-now-a-hypervisor-for-freebsd.aspx
==
Microsoft and partners NetApp and Citrix are excited to announce the availability of FreeBSD support for Windows Server Hyper-V
8,500 lines of code released under the BSD license, is the result of collaboration between Microsoft, NetApp, and Citrix to enable FreeBSD to run as a first-class guest on Windows Server Hyper-V.
==
http://blogs.technet.com/b/openness/archive/2012/08/09/available-today-freebsd-support-for-windows-server-hyper-v.aspx
==
enable FreeBSD to run on Hyper-V with high performance. This release includes 8,500 lines of code submitted under the BSD license, supporting FreeBSD 8.2 on Windows Server 2008 R2.
. . .
Analysis is currently underway to assess customer demand and partner capacity to extend support to FreeBSD 9.0 on Windows Server 2012.
==
FreeBSD enlightened device drivers for Hyper-V/Azure with FreeBSD source tree
http://freebsdonhyper-v.github.com/
https://lists.launchpad.net/freeonhyper-v/msg00000.html
==
From: Chris Knight stryqx (at) DOMAIN.HIDDEN
Date: Mon, 13 Aug 2012 20:34:57 +1000
I’ve pulled down a git clone and created patchsets for FreeBSD 8.2,
8.3, 9.0 and 9.1-BETA1. They can be found here:
==
http://blog.chrisara.com.au/2012/08/hyper-v-integration-components-for_13.html
==
Monday, August 13, 2012
Hyper-V Integration Components for FreeBSD – Patchfiles
Call me old fashioned, but I’d much prefer a patchset than having to install a version control package and suck down a source code check out. So please find a patchset for the Hyper-V integration components for the following versions of FreeBSD:
FreeBSD 8.2 Hyper-V Integration Components Patchset
FreeBSD 8.3 Hyper-V Integration Components Patchset
FreeBSD 9.0 Hyper-V Integration Components Patchset
FreeBSD 9.1-BETA1 Hyper-V Integration Components Patchset
Download the patchset, then issue:
patch –p –d /usr/src <
to patch the source tree, followed by:
cd /usr/src; make kernel KERNCONF=HYPERV_VM INSTKERNNAME=kernel.HYPERV
to install the Hyper-V enabled kernel to /boot/kernel.HYPERV.
Before booting to the Hyper-V enabled kernel it’s best to use GEOM labels to mount the partitions. Follow the instructions here to do this. This makes it easy for you to quickly swap between a Hyper-V enabled kernel and a non-Hyper-V enabled kernel – the reason being the Fast IDE storage driver presents itself as a SCSI driver, changing the device node path which prevents /etc/fstab from working correctly.
. . .
==
Mini How-To: practical method to install OpsMgr ( SCOM) agents on all Hyper-V guest managed by SC VVM ( System Center Virtual Machine Manager)
SCVMM 2008 R2 Интеграция с SCOM 2007 R2 « ИТ Блог Алексея Максимова
12.Установка агентов SCOM на сервер VMM, все хосты виртуализации и все виртуальные машины
На этом этапе мы должны обеспечить наличие агента SCOM на всех объектах, которые подпадают под инфраструктуру VMM, а именно:
•На сервере VMM
•На всех серверах несущих роль VMM Library Server
•На всех серверах виртуализации с ролью Hyper-V
•На всех виртуальных машинах
Учетная запись «Action Account» SCOM на время установки агентов должна быть с правами «Local Admin»; проще всего этого добиться включив в группу «Domain Admin».
Перезапустить сервисы или сервер с OpsMgr.
Solution:
# Filename: Install-Agent_VMMComputers-Get-VM-_for_YoureSCVMM.ps1
# Description: Adds System Center Virtual Machine Manager host servers,
# ( and may be library servers ) and all guest to the set of computers
# managed by System Center Operations Manager and install OpsMgr agents.
#
#[ Victor Miasnikov:
#
# 1) Filter Hyper-V guest without Windows ( or other issue ) by "Unknown" :
# if ( -not ( $Computer.ComputerNameString -eq "Unknown" ) ) {
#
# 2) Using $Computer.ComputerNameString as current full DNS Name of computer for install agents, etc. :
# . . . New-WindowsDiscoveryConfiguration -ComputerName $Computer.ComputerNameString
#
#]
#[ Based:
# Filename: DiscoverVMMComputers.ps1.ps1
# Description: Adds System Center Virtual Machine Manager host servers
# and library servers to the set of computers managed
# by System Center Operations Manager.
# Copyright (c) Microsoft Corporation. All rights reserved.
#]
# DISCLAIMER:
# This script is made available to you without any express, implied or
# statutory warranty, not even the implied warranty of
# merchantability or fitness for a particular purpose, or the
# warranty of title or non-infringement. The entire risk of the
# use or the results from the use of this script remains with you.
$VMMServerComputerName = "YoureSCVMM.YoureADDomain.tut.by"
$RMS = “YoureOpsMgr.YoureADDomain.tut.by”
#
# http://www.thomasmaurer.ch/2010/12/powershell-for-system-center-virtual-machine-manager-and-hyper-v/
#
# Load Powershell Snapin for Virtual Machine Manager:
#
if ((Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SystemCenter.VirtualMachineManager'}) -eq $null)
{
Write-Host("Loading SC VMM PS Snapin")
Add-PSSnapin Microsoft.SystemCenter.VirtualMachineManager
}
#################################
#Init the connection to SCOM srv
#################################
if(-not (Get-pssnapin | Where-Object {$_.Name -eq "Microsoft.EnterpriseManagement.OperationsManager.Client"}))
{
Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
}
new-managementGroupConnection -ConnectionString:$RMS
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
Set-Location $RMS -ErrorVariable errSnapin ;
####################################################################
# Connect to the Virtual Machine Manager server
####################################################################
# Substitute the name of your VMM server and domain in this command:
$VMMServerByComputerName = Get-VMMServer -ComputerName $VMMServerComputerName
####################################################################
# Get all computers managed by VMM and get OpsMgr server
####################################################################
# Get the object for all host and library servers and all guest managed by VMM
$VMMManagedComputer = Get-VM
# Get an instance of the OpsMgr Management Server
$OpsMgrServer = Get-ManagementServer
####################################################################
# For each VMM host, ( and may be library server ) and all guest initiate a discovery
####################################################################
ForEach ($Computer in $VMMManagedComputer)
{
Write-Host $Computer.Name
if ( -not ( $Computer.ComputerNameString -eq "Unknown" ) ) {
Write-Host $Computer.ComputerNameString
Write-Host ""
#Create a new discovery configuration
$DiscoveryConfig = New-WindowsDiscoveryConfiguration -ComputerName $Computer.ComputerNameString -ComputerType Server
#Initiate the Operations Manager discovery
$discoResult = Start-Discovery -ManagementServer $OpsMgrServer -WindowsDiscoveryConfiguration $DiscoveryConfig
#Check that the discovery process discovered the Windows computers you specified.
$discoResult.CustomMonitoringObjects
if($discoResult.CustomMonitoringObjects -ne $null)
{
Write-Host "Agent installation in progress..."
Write-Host ""
Install-Agent –ManagementServer $managementServer –AgentManagedComputer $discoResult.CustomMonitoringObjects
Write-host "Installation Finished, waiting for 60 secondes"
Start-Sleep -s 60
}
}
}
Used resources:
http://www.opsmode.com/2009/09/scheduling-opsmgr-powershell-scripts/
#
#Scheduling OpsMgr PowerShell scripts
#2009/09/17, 10:37 When scheduling an Operations Manager PowerShell script you have to load the powershell snapins.
#
#Insert this in the beginning of your script
#
#$ServerName = “hostname”
#add-pssnapin “Microsoft.EnterpriseManagement.OperationsManager.Client”;
#set-location “OperationsManagerMonitoring::”;
#new-managementGroupConnection -ConnectionString:$ServerName;
#set-location $ServerName;
##if ((Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.EnterpriseManagement.OperationsManager.Client'}) -eq $null)
# {
## add-pssnapin “Microsoft.EnterpriseManagement.OperationsManager.Client”;
# }
#
# Var B
#
##################################
##Init the connection to SCOM srv
##################################
#if(-not (Get-pssnapin | Where-Object {$_.Name -eq "Microsoft.EnterpriseManagement.OperationsManager.Client"}))
# {
# Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
# }
#new-managementGroupConnection -ConnectionString:$RMS
#Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
#Set-Location $RMS -ErrorVariable errSnapin ;
#
> У части виртуальных серверов состояние . . . Not Monitored.
Например:
Они могут быть не в домене.
Если на виртуальном комп-е ISA Server или TMG, то надо задать в них IP OpsMgr.