Skip to main content

iSCSI Virtualization: Ever heard of Stonefly?



StoneFly's Product Manager, Jame Ervin, has written a neat article on Intelligent IP SANs. They're cheap, they're smart and they're what a typical SMB would want!

Three Major Approaches to Virtualizing Operating Systems and Applications

A simple way to maximize system utilization and take advantage of the huge processing power of current hardware platforms is to use server virtualization. The three major approaches to virtualizing operating systems and applications include emulation, para-virtualization, and operating system virtualization. These are described in more detail below. Each type has specific benefits and drawbacks. Some approaches attract more media attention than others, but it is important during the planning phases to evaluate the approaches and choose what makes the most sense in your environment based on your priorities, whether they are performance, hardware utilization, consolidation, or application availability.

  • Emulation virtualization platforms use a reference hardware platform to emulate, which specifies the CPU, memory and add-on components independently of the actual hardware the VM is installed on; all of the guest machines also take advantage of the reference platform. This approach is ideal when the application requires specific hardware or systems to run properly, but it may have more performance limitations than other approaches since performance is limited to the reference platform. This approach can have multiple operating system kernels (Unix, Linux or Windows variants) running simultaneously on the same hardware.
  • Para-virtualization adds a hypervisor that manages the communications of the virtual machines to the physical hardware devices. In order for paravirtualization to work, the operating system needs to be "hypervisor" aware and know to look in the hypervisor to execute commands. It is difficult to use older operating system kernels with this approach, but it offers performance advantages over the emulation approach since the hypervisor acts like a standard OS that communicates with the actual hardware devices. This approach also allows the simultaneous use of multiple operating systems.
  • Operating system-level virtualization allows one machine to run multiple instances of the same operating system. Since this approach has a single, native operating system communicating with the hardware devices, it is very speedy and efficient, but this approach cannot be used to consolidate multiple operating system kernels.




Check out his article here.

Comments

  1. Thanks for the shoutout! Jame

    ReplyDelete
  2. smart. finally someone puts these virtualization technologies into perspective! Great perspective from StoneFly.

    ReplyDelete

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

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