Red Hat Enterprise Virtualization 3.5

RedHat announced the general availability of Red Hat Enterprise Virtualization 3.5, enabling organizations to deploy an IT infrastructure that services traditional virtualization workloads while creating an enterprise-grade foundation for cloud infrastructure. Red Hat Enterprise Virtualization 3.5 delivers standardized services for mission critical workloads, and offers IT organizations greater visibility into provisioning, configuring and monitoring of their virtualization infrastructure, all based on open standards.

"The healthcare industry is undergoing significant changes that require us to rapidly adopt to new business and regulatory compliance requirements. Because Red Hat Enterprise Virtualization is built on open standards that enable flexibility and fast innovation, we can more quickly adopt our IT infrastructure and deploy services with stability and speed.”

Steven BellistriManager, IT, LDI Integrated Pharmacy Services

Red Hat is a recognized leader in the scale and performance of virtual machine workloads, and Red Hat Enterprise Virtualization 3.5 extends this leadership with support for four terabytes (4 TB) of memory per host, 4 TB of vRAM, and 160 vCPUs per virtual machine.

Notable new features in Red Hat Enterprise Virtualization 3.5 include:

• Lifecycle management and provisioning of bare-metal hosts via integration with Red Hat Satellite.
• Compute resource optimization through advanced real-time analytics with oVirt Optimizer integration. This enables users to identify the balance of resource allocation that best meets their needs while provisioning new virtual machines.
• Workload performance and scalability provided through non-uniform memory access (NUMA) support, which is extended to Host NUMA, Guest Pinning and Virtual NUMA. This enables customers to deploy highly scalable workloads with improved performance and minimizes resource overload related to physical memory access times.
• Enhanced disaster recovery via improved storage domain handling, providing support for migrating storage domains between different datacenters supported by Red Hat Enterprise Virtualization, enabling partner technologies to deliver site recovery capabilities.

Red Hat Enterprise Virtualization also serves as an ideal foundation for both traditional virtualization and highly flexible cloud-enabled workloads built on OpenStack. Red Hat Enterprise Virtualization 3.5 includes features that enhance this foundation for cloud-enabled workloads:

• Integration and shared common services with OpenStack Image Service (Glance) and OpenStack Networking (Neutron), available as a Tech Preview, enabling administrators to break down silos and to deploy resources once across the infrastructure.
• Instance types, unifying the process of provisioning virtual machines for both virtual and cloud-enabled workloads.

Red Hat Enterprise Virtualization Availability

• As a standalone offering - Red Hat Enterprise Virtualization 3.5 - including Hypervisor and Manager for virtualized enterprise workloads for supported guest operating systems.
• As an integrated offering called Red Hat Enterprise Linux with Smart Virtualization, aimed at customers looking to maximize the benefits of their virtualized infrastructure with Linux workloads. This offering combines the innovation, performance, scalability, reliability and security features of Red Hat Enterprise Linux with the advanced virtualization management capabilities of Red Hat Enterprise Virtualization.
• Via Red Hat Cloud Infrastructure, a comprehensive solution that supports organizations on their journey from traditional datacenter virtualization to OpenStack-powered clouds. Red Hat Cloud Infrastructure is a single subscription offering that includes Red Hat CloudForms, Red Hat Satellite, Red Hat Enterprise Linux OpenStack Platform, and Red Hat Enterprise Virtualization.

Internet Explorer Error After Windows Patches

Windows 7 Pro 64-bit SP1 systems

Solved the "invalid address" problem by removing the

 dword value "MoveImages"

from the following Windows registry key:

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

After that I was able to start IE10 without errors.

( Thank you Marcus Jaken for pointing me in the right direction: http://cloudsurvivalguide.com/?p=564 )

"MoveImages" seems to be related to "Address space layout randomization" ( http://en.wikipedia.org/wiki/Address_space_layout_randomization#Microsoft_Windows ).

For analysis I have checked some of our earlier Windows 7 installs:

• On two different Win7 installs without "MoveImages" we could start IE10 without error.
• On several Win7 installs with "MoveImages" equal to 0x00 we got an "invalid error" when starting IE10.  After removing "MoveImages" we could start IE10 without error.

We suspect that running EMET ( http://support.microsoft.com/kb/2458544/en-us ) caused the creation of the "MoveImages" dword in the registry.

Diff vSphere 5.0, 5.5 and 6.0

Install VMware vSphere Client on Domain Controller Machine

As VMware admin’s ,we are so much used to work with vSphere windows client against vSphere web Client. Have you tried to installing vSphere client on Domian controller machine. By default, that is not possible. When we try to install vSphere windows client on Domain Controller, We may end up with the error message” vSphere Client fails with a message saying the as a requirements the management station has to be running XP SP2 and not a domain controller”. For people running Lab environment, Will not prefer to install another windows VM just to install vSphere client. In that situation, You can make use of this OS SKIP command to install the vSphere client on Windows Domain controller as a workaround.
Below is the error message you will receive, when you try to install vSphere client on Windows Domain Controller machine.
 You can use an advanced switch when installing VI client on Domain Controller . You can launch the installer from a command line and in this case there is a switch to use which skips the OS check. Here is the command to use:
VMware-viclient.exe /VSKIP_OS_CHECKS=”1″