Tuesday, April 14. 2009
Scott Herold talks about VESI and Vizioncore
Saturday, April 11. 2009
Using SCVMM to manage VMware, playing with fire!
Use caution when experimenting with the SCVMM and VMware, here are five reasons why you don’t’ want to use Microsoft’s SCVMM (System Center Virtual Machine Manager) for managing VMware Infrastructure.
SCVMM Displays Very Little VM and Guest OS Information
The VI Client presents useful information to VMware Infrastructure 3 administrators, such as guest OS IP address, hostname, and performance history. The SCVMM console does not offer any of this information, instead relying on integration with additional complex systems.
SCVMM Creates Unnecessary Port Groups on ESX vSwitches
When managing VMware ESX virtual machine networks, SCVMM exposes only vSwitches and not port groups. SCVMM then creates new port groups on every ESX vSwitch in the environment—duplicating existing functionality and increasing management costs and complexity.
SCVMM Imposes Artificial Constraints on VMware Infrastructure 3 Resources
SCVMM prevents migration and cloning of virtual machines that vCenter would otherwise allow. Managing VMware Infrastructure 3 with SCVMM compromises powerful features that make VMware ESX the more efficient virtualization platform.
SCVMM Provisioning Defaults Unsuitable for VMware ESX Virtual Machines
Microsoft advertises the ability to provision new VMware ESX virtual machines with SCVMM. In reality, SCVMM ignores advanced ESX capabilities and hypervisor platform differences, so the VMs it creates require numerous manual configuration adjustments to make them compatible with ESX.
SCVMM Destroys VMware Infrastructure 3 Templates During Import
Use caution when experimenting with the SCVMM capability to import VMware Infrastructure 3 templates. SCVMM will try to establish a foothold in your management environment by deleting the original templates from ESX datastores without any advance warning.
Architectural difference between VMware vs Hyper V explained?
There's a fundamental structural difference between VMware and Hyper-V. Tim Antonowicz, Senior SE and virtualization guru at Mosaic explains the difference, but is he right?
Update : Read Matt McSpirit's comment.
Thursday, April 9. 2009
Veeam has released version 4.5 of nworks products
Scott Herold announced the public availability of Virtualization EcoShell
I'm not talking "Free for 30 days and then we're going to rip 80% of the features away". I'm not talking "Free....for only a few ESX Servers". I'm talking 100% completely free of charge regardless of the size of your environment. How's that for an April 15th surprise?
The Virtualization EcoShell Initiative (VESI™) is a community-based initiative to help extend virtualization management using Microsoft Windows PowerShell. Whether you are a novice looking for assistance in enhancing your virtualization administration practices or an expert looking to share your knowledge with others, theVESI.org is the place for you.
Wednesday, April 8. 2009
How Microsoft Designs the Virtualization Host and Network Infrastructure
@vinternals : Public service announcement. Please ensure you are sitting down before reading my latest post http://vinternals.com/2009/04/microsoft-myths-and-realities/ I'm not kidding about that last tweet. I have just endanged a good proportion of the vExpert community, who may die from laughter.
In this paper, published January 2009, we get the cold hard facts on Hyper-V as deployed by none other than Microsoft IT themselves. Internally. Y’know, that whole dogfood thing. And the results are absolutely astounding. Now before going further, I need to re-iterate this is an actual Microsoft published case. It is not an April Fools joke, they are not having a lend of us. It is stone cold truth from Microsoft’s own IT department. If you were going to listen to anybody talk about the reality of Hyper-V, it’s these guys. And again, this is not a joke. This is real.