Skip to main content

Yet Another Virtualization Intro: Virtualization and Client Server Technology

Isolation implies the independence virtual machines afford. Virtual machines are completely isolated from hosts and other machines. This provides the security that if one machine crashes the rest of the machines will be unaffected. This isolation also ensures data control. Machines can only communicate through specifically configured network connections. Data cannot infiltrate or affect other machines or applications.

Encapsulation is similar to the abstraction and information hiding that characterizes virtualization. It is defined as the combination of elements to create a new entity. For example, OOP (Object-Oriented Programming) languages like C++ and Java use encapsulation to create high-level (abstracted) objects. In virtualization, an entire virtual machine and its contents are encapsulated so it can be saved as a single file. This makes it incredibly easy to copy and move. Encapsulation resonates with virtualization in its tendency towards hiding the details to make dealing with objects easier. This is accomplished by hiding complexity with a simple interface.
Link

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

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...