Virtual Machine Manager Plattformen: VMware, Hyper-V & KVM

Überblick der Enterprise-Virtualisierung

Während Synology's integrierte VMM-Lösung perfekt für kleinere Umgebungen ist, benötigen größere Infrastrukturen oft professionelle Virtualisierungsplattformen. Die drei Marktführer bieten jeweils einzigartige Vorteile:

VMware vSphere/ESXi:

Marktführer mit ausgereiften Features
Beste Performance und Skalierbarkeit
Umfangreiche Management-Tools
Premium-Preismodell

Microsoft Hyper-V:

Tief in Windows-Ökosystem integriert
Kosteneffektiv für Windows-Umgebungen
Starke Active Directory Integration
Gute Performance bei Windows-VMs

KVM (Kernel-based Virtual Machine):

Open Source und kostenlos
Linux-nativ mit bester Linux-VM Performance
Hochgradig anpassbar
Steile Lernkurve

VMware vSphere Ecosystem

ESXi Hypervisor

Installation und Grundkonfiguration:

# ESXi 7.0/8.0 Hardware-Anforderungen
CPU: 64-bit x86 mit Hardware-Virtualisierung
RAM: Minimum 4 GB (empfohlen 8+ GB)
Storage: 32 GB für Boot-Drive (USB/SD/SSD)
Network: Gigabit Ethernet (minimum)

Erste Schritte:

ESXi ISO von VMware herunterladen
Bootable USB erstellen
Hardware-Kompatibilität prüfen (HCL)
Installation durchführen
Management-IP konfigurieren

Netzwerk-Konfiguration:

# ESXi Host Netzwerk-Setup
Management Network: 192.168.1.10/24
vMotion Network: 192.168.2.10/24
VM Network: 192.168.3.0/24
Storage Network: 192.168.4.10/24 (iSCSI)

vCenter Server Appliance (VCSA)

Deployment:

# VCSA 7.0/8.0 OVF Deployment
Sizing:
  Tiny: Bis 10 Hosts, 100 VMs
  Small: Bis 100 Hosts, 1000 VMs
  Medium: Bis 400 Hosts, 4000 VMs
  Large: Bis 1000 Hosts, 10000 VMs

Ressourcen (Small):
  vCPU: 8
  RAM: 24 GB
  Storage: 579 GB

Cluster-Management:

# vSphere Cluster erstellen
1. vCenter einloggen
2. Datacenter > New Cluster
3. DRS aktivieren (Distributed Resource Scheduler)
4. HA aktivieren (High Availability)
5. ESXi Hosts hinzufügen

Advanced Features

vMotion (Live Migration):

Voraussetzungen:
  - Shared Storage (SAN/NAS)
  - Kompatible CPU-Features
  - vMotion-Netzwerk konfiguriert
  - Enterprise Plus Lizenz

Konfiguration: 1. VMkernel-Port für vMotion
  2. vMotion-Netzwerk zuweisen
  3. VM-kompatibilität prüfen
  4. Migration durchführen

Distributed Resource Scheduler (DRS):

# DRS-Regeln konfigurieren
Automation Level:
  - Manual: Admin entscheidet
  - Partially Automated: Empfehlungen
  - Fully Automated: Automatische Migration

Affinity Rules:
  - Keep VMs together (Affinity)
  - Separate VMs (Anti-Affinity)
  - VM-to-Host rules

High Availability (HA):

HA-Konfiguration:
  Admission Control:
    - Host failures cluster tolerates: 2
    - Slot Policy oder Percentage

  VM Monitoring:
    - VM and Application Monitoring
    - VM Restart Priority: High/Medium/Low

  Heartbeat Datastores:
    - Minimum 2 Datastores
    - Preferably on different storage arrays

Microsoft Hyper-V

Hyper-V Server vs. Windows Server

Hyper-V Server (Kostenlos):

# Hyper-V Server 2019/2022 Features
- Core Hypervisor (ohne GUI)
- PowerShell Management
- Remote-Management über RSAT
- Unlimited Windows VMs mit gültigen Lizenzen
- Keine Additional Costs

Windows Server mit Hyper-V Role:

# Windows Server Datacenter
- GUI-Management verfügbar
- Alle Windows Server Features
- Unlimited VMs mit Datacenter License
- Integration Services included

Installation und Konfiguration

Hyper-V Role Installation:

# PowerShell Installation
Install-WindowsFeature -Name Hyper-V -ComputerName Server01 -IncludeManagementTools -Restart

# DISM Installation (Alternative)
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

Hyper-V Manager Setup:

# Virtual Switch erstellen
New-VMSwitch -Name "External-Switch" -NetAdapterName "Ethernet" -AllowManagementOS $true

# VM erstellen
New-VM -Name "Server2022" -MemoryStartupBytes 4GB -Generation 2 -NewVHDPath "C:\VMs\Server2022.vhdx" -NewVHDSizeBytes 60GB

System Center Virtual Machine Manager (SCVMM)

Enterprise Management:

SCVMM 2022 Features:
  - Centralized Management
  - Fabric Management
  - Cloud Integration (Azure)
  - Compliance & Governance
  - Automated Deployment

Lizenzierung:
  - Datacenter License erforderlich
  - Management License pro verwalteten Host

SCVMM Installation:

# Voraussetzungen
- SQL Server (Express/Standard/Enterprise)
- .NET Framework 4.8
- Windows ADK
- PowerShell 5.1+

# Installation Steps
1. SQL Server Database erstellen
2. SCVMM Setup ausführen
3. Library Server konfigurieren
4. Host Groups definieren
5. Hyper-V Hosts hinzufügen

Advanced Hyper-V Features

Live Migration:

# Live Migration konfigurieren
Enable-VMMigration
Set-VMMigrationNetwork "192.168.2.0/24"
Set-VMHost -VirtualMachineMigrationAuthenticationType Kerberos

# Migration durchführen
Move-VM -Name "TestVM" -DestinationHost "HyperV02" -IncludeStorage -DestinationStoragePath "D:\VMs"

Hyper-V Replica:

# Replica Server konfigurieren
Set-VMReplicationServer -ReplicationEnabled $true -AllowedAuthenticationType Kerberos

# Replica für VM aktivieren
Enable-VMReplication -VMName "CriticalVM" -ReplicaServerName "HyperV-DR" -ReplicaServerPort 80 -AuthenticationType Kerberos

Storage Spaces Direct (S2D):

# S2D Cluster erstellen
New-Cluster -Name S2D-Cluster -Node HyperV01,HyperV02,HyperV03 -NoStorage
Enable-ClusterStorageSpacesDirect

# Storage Pool und Volumes
New-Volume -StoragePoolFriendlyName S2D* -FriendlyName "VM-Storage" -FileSystem CSVFS_ReFS -Size 2TB

KVM (Kernel-based Virtual Machine)

KVM auf Ubuntu/CentOS

Installation Ubuntu 22.04:

# Hardware-Virtualisierung prüfen
egrep -c '(vmx|svm)' /proc/cpuinfo

# KVM Installation
sudo apt update
sudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils

# Benutzer zu libvirt Gruppe hinzufügen
sudo usermod -aG libvirt $USER
sudo usermod -aG kvm $USER

Installation CentOS/RHEL:

# KVM Packages installieren
sudo dnf groupinstall "Virtualization Host"
sudo dnf install virt-manager virt-viewer

# Services starten
sudo systemctl enable libvirtd
sudo systemctl start libvirtd

# Firewall konfigurieren
sudo firewall-cmd --add-service=libvirt --permanent
sudo firewall-cmd --reload

libvirt Management

VM erstellen via virt-install:

# Ubuntu Server VM
virt-install \
  --name ubuntu-server \
  --ram 4096 \
  --disk path=/var/lib/libvirt/images/ubuntu-server.qcow2,size=20 \
  --vcpus 2 \
  --os-type linux \
  --os-variant ubuntu22.04 \
  --network bridge=virbr0 \
  --graphics none \
  --console pty,target_type=serial \
  --location 'http://archive.ubuntu.com/ubuntu/dists/jammy/main/installer-amd64/' \
  --extra-args 'console=ttyS0,115200n8 serial'

VM Management Commands:

# VM Status
virsh list --all

# VM starten/stoppen
virsh start vm-name
virsh shutdown vm-name
virsh destroy vm-name

# VM Info
virsh dominfo vm-name
virsh dumpxml vm-name

# Snapshots
virsh snapshot-create-as vm-name snapshot1 "Initial snapshot"
virsh snapshot-list vm-name
virsh snapshot-revert vm-name snapshot1

Erweiterte KVM-Konfiguration

SR-IOV für Performance:

# Intel VT-d aktivieren (GRUB)
# /etc/default/grub
GRUB_CMDLINE_LINUX="intel_iommu=on iommu=pt"

# GRUB update
sudo update-grub
sudo reboot

# SR-IOV VFs erstellen
echo 4 > /sys/class/net/eth0/device/sriov_numvfs

# PCI Passthrough
virsh nodedev-list --tree
virsh nodedev-detach pci_0000_01_00_0

NUMA-Optimierung:

<!-- VM XML NUMA-Konfiguration -->
<domain type='kvm'>
  <cpu mode='host-passthrough'>
    <numa>
      <cell id='0' cpus='0-3' memory='4194304' unit='KiB'/>
      <cell id='1' cpus='4-7' memory='4194304' unit='KiB'/>
    </numa>
  </cpu>
</domain>

Virtio-Optimierung:

<!-- High-Performance Disk -->
<disk type='file' device='disk'>
  <driver name='qemu' type='qcow2' cache='none' io='native'/>
  <source file='/var/lib/libvirt/images/vm.qcow2'/>
  <target dev='vda' bus='virtio'/>
</disk>

<!-- High-Performance Network -->
<interface type='bridge'>
  <source bridge='br0'/>
  <model type='virtio'/>
  <driver name='vhost' queues='4'/>
</interface>

oVirt (Red Hat Virtualization)

Open Source Enterprise KVM:

oVirt Features:
  - Web-basiertes Management
  - Live Migration
  - High Availability
  - Storage Management
  - REST API
  - Integration mit Gluster/Ceph

Deployment: 1. oVirt Engine (Management)
  2. oVirt Nodes (Hypervisor)
  3. Storage Domains
  4. Logical Networks

Synology NAS als Storage-Backend

iSCSI Integration

VMware iSCSI Setup:

# Synology iSCSI Target erstellen
1. SAN Manager > iSCSI
2. Create iSCSI Target
3. Create LUN (Block-level)
4. CHAP Authentication konfigurieren

# ESXi iSCSI Initiator
1. Configuration > Storage Adapters
2. Add Software iSCSI Adapter
3. Configure CHAP
4. Add Dynamic Discovery
5. Rescan for LUNs

Hyper-V iSCSI Integration:

# Windows iSCSI Initiator
# iSCSI Initiator Properties
1. Discovery Tab > Discover Portal
2. Target Portal: synology-ip:3260
3. Advanced > CHAP Settings
4. Targets Tab > Connect
5. Disk Management > Initialize Disk

KVM iSCSI Setup:

# iSCSI Initiator Installation
sudo apt install open-iscsi

# Discovery
sudo iscsiadm -m discovery -t st -p synology-ip:3260

# Login
sudo iscsiadm -m node --login

# Persistent Mount
echo "synology-ip:3260,1 iqn.target-name" >> /etc/iscsi/nodes

NFS Integration

VMware NFS Datastore:

# Synology NFS Setup
1. Control Panel > File Services > NFS
2. Enable NFS Service
3. Shared Folder > Edit > NFS Permissions
4. Configure Squash and Security

# ESXi NFS Mount
1. Configuration > Storage
2. Add Storage > Network File System
3. Server: synology-ip
4. Folder: /volume1/vmware-datastore
5. Datastore Name: SynologyNFS

Hyper-V über SMB:

# SMB 3.0 für Hyper-V
# Synology SMB Setup erforderlich
1. Control Panel > File Services > SMB
2. Advanced > Enable SMB 3.0
3. Create Shared Folder for VMs

# Hyper-V SMB Storage
New-SmbGlobalMapping -RemotePath "\\synology-ip\vm-storage" -Credential $cred -Persistent $true

Performance-Vergleich

CPU-Performance

VMware vSphere:
  Overhead: ~5-10%
  Features: CPU Hot-Add, NUMA-Aware
  Skalierung: Bis 768 vCPUs pro VM

Hyper-V:
  Overhead: ~8-12%
  Features: Dynamic Memory, NUMA
  Skalierung: Bis 240 vCPUs pro VM

KVM:
  Overhead: ~3-8%
  Features: CPU Pinning, NUMA
  Skalierung: Bis 288 vCPUs pro VM

Memory-Management

VMware TPS (Transparent Page Sharing):

# Memory Overcommitment
VM Memory: 100 GB
Physical RAM: 64 GB
TPS Savings: ~20-30%
Ballooning: Ja
Compression: Ja

Hyper-V Dynamic Memory:

# Dynamic Memory Konfiguration
Set-VMMemory -VMName "TestVM" -DynamicMemoryEnabled $true -MinimumBytes 512MB -StartupBytes 2GB -MaximumBytes 8GB

KVM Memory Management:

# KSM (Kernel Shared Memory)
echo 1 > /sys/kernel/mm/ksm/run
echo 100 > /sys/kernel/mm/ksm/pages_to_scan

# Hugepages für Performance
echo 1024 > /proc/sys/vm/nr_hugepages

Management-Tools Vergleich

VMware Tools

vSphere Client (HTML5):

Modern Web Interface
Vollständige Funktionalität
Responsive Design
Plugin-frei

PowerCLI:

# VMware PowerShell Module
Install-Module VMware.PowerCLI

# Connection
Connect-VIServer -Server vcenter.domain.com

# VM Operations
Get-VM | Where {$_.PowerState -eq "PoweredOff"} | Start-VM
New-VM -Name "NewVM" -Template "Win2022-Template" -Datastore "SynologyNFS"

Hyper-V Tools

Hyper-V Manager:

Standalone Management
Local und Remote
Basic VM Operations

Windows Admin Center:

Features:
  - Modern Web Interface
  - Hyper-V Management
  - Performance Monitoring
  - Certificate Management
  - Extensible via Extensions

PowerShell Hyper-V Module:

# VM Bulk Operations
Get-VM | Where {$_.State -eq "Off"} | Start-VM
Get-VM | Measure-VMResourcePool

KVM Management Tools

virt-manager (GUI):

GTK-basiertes Interface
Remote-Verbindungen
VNC/SPICE Konsole
Storage/Network Management

Cockpit:

# Web-basiertes Management
sudo apt install cockpit cockpit-machines
sudo systemctl enable cockpit.socket

# Browser: https://server-ip:9090

oVirt/RHV:

Enterprise Web Interface
RESTful API
Role-based Access
Comprehensive Monitoring

Migration zwischen Plattformen

VMware zu Hyper-V

Microsoft Virtual Machine Converter (MVMC):

# MVMC Installation und Konvertierung
1. Download MVMC von Microsoft
2. Install auf Windows Management Station
3. Connect zu vCenter und Hyper-V
4. Select Source VM
5. Configure Destination
6. Start Conversion Process

Hyper-V zu VMware

VMware vCenter Converter:

# Converter Standalone
1. Download VMware Converter
2. Install auf Windows System
3. Connect zu Source (Hyper-V)
4. Connect zu Destination (vCenter)
5. Configure Conversion Options
6. Start Conversion Job

Physical zu Virtual (P2V)

VMware vCenter Converter:

P2V Process: 1. Boot from Converter ISO
  2. Configure Network Settings
  3. Connect to vCenter
  4. Select Source Disks
  5. Configure Destination VM
  6. Start Conversion

Limitations:
  - Domain Controllers kompliziert
  - Boot-time Dependencies
  - Driver Compatibility

Backup und Disaster Recovery

Agentless Backup

Veeam Backup & Replication:

VMware Integration:
  - vSphere API Integration
  - Application-aware Processing
  - CBT (Changed Block Tracking)
  - Instant VM Recovery

Hyper-V Integration:
  - VSS Integration
  - RCT (Resilient Change Tracking)
  - Quick Migration
  - File-level Recovery

Synology Active Backup for Business:

# VMware Backup
1. Install Agent auf vCenter
2. Configure Backup Job
3. Select VMs for Backup
4. Set Retention Policy
5. Monitor Backup Status

# Hyper-V Backup
1. Install Agent auf Hyper-V Host
2. Configure VM Discovery
3. Create Backup Task
4. Set Compression & Deduplication

Replication

VMware vSphere Replication:

# SRM (Site Recovery Manager)
1. Install SRM Server
2. Configure Array Managers
3. Create Protection Groups
4. Define Recovery Plans
5. Test Recovery Plans

Hyper-V Replica:

# Cross-Site Replication
Enable-VMReplication -VMName "CriticalVM" -ReplicaServerName "DR-Site" -ReplicaServerPort 443 -AuthenticationType Certificate

Lizenzierung und Kosten

VMware Lizenzmodell

vSphere Standard:
  - Basic Features
  - vMotion, HA, DRS
  - $995 pro CPU

vSphere Enterprise Plus:
  - Advanced Features
  - Distributed Switch
  - Storage vMotion
  - $3,595 pro CPU

vCenter Server:
  - Separate License erforderlich
  - $4,245 für Standard
  - Essential für kleine Umgebungen

Microsoft Lizenzierung

Windows Server Datacenter:
  - Unlimited VMs
  - Core-based Licensing
  - $6,155 für 16 Cores
  - Additional Core Packs

Hyper-V Server:
  - Kostenloser Hypervisor
  - Windows VM Licenses separat
  - Management Tools extra

Open Source Alternative

KVM/oVirt/Proxmox:
  - Keine Hypervisor-Lizenz
  - Support verfügbar
  - Community Edition kostenlos
  - Enterprise Support kostenpflichtig

Best Practices

Capacity Planning

Ressourcen-Kalkulation:

CPU Oversubscription:
  VMware: 2:1 bis 4:1
  Hyper-V: 2:1 bis 3:1
  KVM: 2:1 bis 6:1

Memory Overcommitment:
  VMware: 1.2:1 bis 1.5:1
  Hyper-V: 1.1:1 bis 1.3:1
  KVM: 1.2:1 bis 2:1

Storage IOPS:
  OLTP Database: 1000+ IOPS
  File Server: 100-500 IOPS
  Web Server: 200-800 IOPS

Security Hardening

VMware Security:

# vSphere Hardening
1. ESXi Security Profile
2. VM-VM Isolation
3. Network Security
4. vCenter Permissions
5. Certificate Management

Hyper-V Security:

# Shielded VMs
Set-VMSecurity -VMName "SecureVM" -EncryptStateAndVmMigrationTraffic $true -VirtualizationBasedSecurityOptOut $false

Monitoring und Performance

VMware vRealize Operations

vROps Features:
  - Predictive Analytics
  - Capacity Planning
  - Performance Optimization
  - Compliance Monitoring
  - Custom Dashboards

Integration:
  - vCenter Server
  - NSX-T
  - vSAN
  - Third-party Systems

System Center Operations Manager

# SCOM für Hyper-V
1. Import Hyper-V Management Pack
2. Configure Discovery Rules
3. Set Performance Counters
4. Create Custom Views
5. Configure Alerting

Open Source Monitoring

Zabbix für KVM:

# LibVirt Monitoring
1. Install Zabbix Agent
2. Configure LibVirt Monitoring
3. Import KVM Templates
4. Set Performance Triggers
5. Create Custom Dashboards

Fazit und Empfehlungen

Wann welche Plattform?

VMware vSphere:

Enterprise-Umgebungen mit höchsten Anforderungen
Multi-Vendor Hardware
Maximale Performance und Features
Budget für Premium-Lösung vorhanden