云計算平臺虛擬機-文庫吧
2025-06-08 14:57 本頁面
【正文】 a hypervisor are known as virtual machines(VMs. There are two basic types of hypervisor[IBM2005]:Type1hypervisors directly interface with the system operating systems run inside a virtual is usually a special,privileged virtual machine that can manage the is an example of this type of hypervisor. Type2hypervisors run as a normal program inside a normal operating system. This OS is known as the guest OS runs as a process in the host OS. These processes can be manipulated just like any other and KVM are examples of this type of hypervisor.See Figure1for a parison of Type1and2hypervisors.A strict Type2hypervisor requires that all I/O devices be emulated pletely in software,resulting in added overhead for I/O allows the virtual machine to make calls directly to the hypervisor,resulting in potentially increased e requires modi cations to the guest kernel. [IBM2005]See Table I for a parison of KVM and Xen.ACM Transactions on Computational Logic,Month20YY.An Evaluation of KVM for Use in Cloud Computing3Table KV M XenT ype1Hypervisor T ype2HypervisorHost is a privileged guest Host directly on hardwareUnprivileged guests Guests have user privilegesx86ring abstraction UNIX process abstractionP aravirtualized guests Unmodified guests Virtual Machine(KVMThe Kernelbased Virtual Machine(KVMis a Type2hypervisor maintained by Qumranet,Inc[Habib2008][Qumranet2006].KVM is based on the QEMU emulator and derives all its management tools from main focus of KVM development is to use the x86VT extensions,which allow virtual machines to make system calls[van Doorn2006].KVM versions newer than KVM62have support for paravirtualized Linux guests,but we did not utilize this capability in our initial prototype.KVM uses a set of Linux kernel modules to provide VT can run on a stock Linux kernel that is:(anew enough and(bhas had the KVM modules built for contrast,Xen requires a heavily patched Linux kernel,on which development lags behind the mainline kernel.KVM supports the QEMU Copyonwrite(QCOWdisk image format,allowing it to support a snapshot mode for its disk I/O snapshot mode, all disk writes are directed to a temporary le,and changes are not persisted to the original disk image VM39。s can be run from one disk image, somewhat mitigating the huge storage requirements associated with hosting a grid of VM39。s[Keahey et ].Destroying a virtual cluster is as simple as sending SIGKILL to each hypervisor and deleting the image from disk.KVM supports the standard Linux TUN/TAP model for Ethernet using this model,each VM gets its own networking resources,making it indistinguishable from a physical machine. Compute NodesCentral to the Virtual Organization Cluster Model(VOCMis the Virtual Organization Cluster(VOC,which is posed of Virtual Compute Nodes( Virtual Organization(VOthat wishes to utilize the pute facilities provided by a Virtualization Service Provider(VSPmust provide a VM image or set of VM images,along with some general con guration each image will potentially be used to spawn multiple VM39。s,the con guration of each image must not make any assumptions about the type of networking(hardware interface, hostname,or systemspeci c con guration ,dynamic networking con guration should be a hostname has been obtained,dynamic con guration based upon the hostname is allowed.Our model VOC was bui
研究報告相關(guān)推薦
鄂ICP備17016276號-1