Skip to main content

Hitachi finally brings out Virtage, embeds it in Xeon blades

Hitachi will continue carving out its own place in the virtualization market with a Xeon-based blade server that includes a built-in hypervisor.

In the first quarter of next year, Hitachi America – a subsidiary of the big guy – will ship a Xeon version of the BladeSymphony 1000 system outfitted with homegrown Virtage technology. Virtage stands as Hitachi's firmware-based hypervisor that has been available with the Itanium-based version of BladeSymphony since last November. The pre-loaded hypervisor gives Hitachi a unique attack in the server game with the company claiming performance and security leads over rivals with the technology.
Click here to find out more!

Built-in hypervisors have suddenly become all the rage. VMware and XenSource have revealed plans to work with OEMs on embedded hypervisors that pop into the flash memory of servers. Hitachi, however, thinks it's creating a much tighter bond between hardware and the hypervisor with its Virtage approach.

"All they are doing with the embedded hypervisor is allowing customers to boot from flash memory," said Steve Campbell, a VP at Hitachi.

With Virtage, Hitachi loads its own hypervisor into the firmware of the service processor found on its blade server chassis. This lets Hitachi's software span all of the blades slotted into the chassis. In addition, it gives Hitachi a chance to reach deep into the server components, controlling things such as physical I/O interfaces.


Ashlee reporting...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op