Skip to main content

SaS and Virtualization: LSI,Intel and Microsoft show how its done

SAS =! SaaS. SAS= serial Attached SCSI ;)

LSI Corporation announced it is collaborating with Intel and Microsoft at Intel Developer Forum to demonstrate the scalability, availability and performance enhancements that Serial Attached SCSI (SAS) brings to virtualized environments. LSI will showcase the Windows Server virtualization capabilities of its SAS portfolio at the Independent Hardware Vendor (IHV) Community booth #119, September 18-20, 2007 at the Moscone Center West in San Francisco. In addition, LSI will be displaying its end-to-end SAS solutions and unmatched storage interface breadth at various venues throughout the show, including the LSI booth #229, the Unified Extensible Firmware Interface (UEFI) Community booth #149, and the SCSI Trade Association (STA) booth #324.

"With more and more users deploying virtualization technology to capitalize on the operational efficiencies its provides, LSI is working to make sure that our industry-leading SAS portfolio not only meets the demands of these environments, but exceeds them," said Robert Andrews, director of product marketing for the Storage Components Group, LSI Corporation. "This demonstration with Intel and Microsoft substantiates the importance of our end-to-end SAS technology that has the ability to deliver superior scalability, availability and performance to virtualization implementations."

The Windows Server 2008 demonstration will showcase how extendible SAS storage products offer a flexible and simplified hardware infrastructure to scale up Windows Server virtualization deployments. This demonstration will highlight the seamless integration of SAS physical hardware in Windows Server 2008 and its hypervisor-based virtualization capabilities with a single driver implementation while achieving greater than 90 percent of physical storage hardware performance.


CNNMoney here.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!
Post a Comment
Read more