Archive for August, 2011
vSphere 5.0 Features - and that’s just part of it
Well, after long wait, it is now available to the public. But hey, it is still not too late for some of you to know what are the new features come with v5 and the long list can be found in the vSphere Blog here. More to come but it will take sometime for someone to list it out.
Nevertheless, below are the first 50 new features available in v5:
- Storage DRS - Perform ongoing load balance between storage based on available resources
- Storage I/O Control for NFS - To gain much control (prioritization) on storage I/O for NFS datastore
- VMFS-5 - New version of VMFS
- ESXi Firewall - The stateless firewall in ESXi but wasn’t based on iptables
- VMFS Scalability and Performance enhancements - Unified 1MB block size with larger single extent volume (max 64TB)
- 2TB+ pass-through RDM support - Larger RDM support which more than 2TB (max 64TB)
- vCenter inventory extensibility
- Storage APIs — VAAI T10 Compliancy
- Storage APIs — VAAI Offloads for NAS - allow NAS array offload certain storage operation to array
- Storage APIs — VAAI Thin Provisioning - allow monitoring of space on thin provision array
- Storage APIs — Storage Awareness/Discovery
- Storage APIs — Data Protection compatible with MN
- APD, Permanent APD Survivability Enablement
- Snapshot enhancements - Snapshot consolidation for broken snapshot
- Storage vMotion scalability improvements - Support VM with snapshot & linked clones (new mirroring technic)
- iSCSI Enablement: iSCSI UI Support
- iSCSI Enablement: Stateless Support
- Multi-queue Storage IO adapters
- Increase NFSv3 Max Share Count to 256
- SATA 3.0
- Software FCoE initiator support
- Enhanced logging support
- Enhanced Storage metrics
- Profile-Driven Storage - Level of storage based on capacity, performance, availability & etc
- Storage vMotion support for snapshots - Possible to do storage vmotion for VM with snapshot
- vSphere Storage Appliance (VSA) - Linux appliance (SLES 11) provides with benefit of vMotion & HA without shared storage
- SSD Detection and Enablement - SSD automatically detected, tagged and enabled by ESXi 5.0
- vSphere Replication - Built-in vSphere replication, simple and cost efficient replication
- vSphere Data Recovery 2.0
- VADP enhancements
- vCenter Orchestrator (vCO) Enhancements
- vCO — Library extension and consolidation
- vCO — vSphere Client integration - Third party application integration
- vCO — Scalability
- Network I/O Control (NIOC) Phase 2
- NIOC — User Defined Resource Pools
- NIOC — HBR traffic type
- NIOC — 802.1p tagging
- Network Traffic Stats for iOPS
- Improvement to UDP and Multicast traffic types
- New networking drivers for server enablement
- vDS support for Port mirror, LLDP and NetFlow V5 - discover network devices, traffic monitoring & network troubleshooting
- vDS Manage Port Group UI enhancement
- Hot-Insert/Remove of Filters
- Enhanced vMotion Compatibility
- Storage vMotion support for Linked Clones
- vMotion scalability (dual-NIC & longer latency support) - Multi NIC support (4x 10gE / 16x 1gE) & up to 10ms latency
- vNetwork API enhancements
- vNetwork Opaque Channel
- Support for 8 10GbE Physical NIC ports per host
ariyossss
No commentsFinally VMware Announce vSphere 5 General Availability today
Just got the news today from one of my colleague and you can read here for more details. To get start with v5, you can start download it from here. I’ve been involved with the Beta version for the last two weeks and the only thing I can say is, v5 definitely beat previous vSphere version I had tried before.
ariyossss
No commentsvMotion with NX flag related error
This problem happened last time when we try to migrate a VM via vMotion from one host to another. The hardware was slightly different on the processor:
- Source: 2x HP Blade BL460c G5 (AMD Opteron 2356)
- Destination: 5x HP Balde BL460c G7 (AMD Opteron 6xxx)
As it was mentioned in this KB, this issue caused by NX flag setting and nothing to do with EVC mode at all. Although you can correct this per VM basis, I rather chose to enable this setting (AMD No eXecute (NX)) at the bios for both G5 hosts. After that, vMotion VMs from G5 to G7 and vice versa can be done without issue.
ariyossss
