[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unikraft and Virtualization.



As a unikernel, unikraft has:
-Single address space: no border between the user and the kernel space, meaning no syscalls. Single process (thus only multi-threading), no fork
-Low memory footprint compared to a traditional VM: only the necessary software composed the binary

The unikernel image is seen as a traditional VM from the point of view of the hypervisor.ervisor


De: "Jason Long" <hack3rcon@xxxxxxxxx>
À: "K. Kahurani" <k.kahurani@xxxxxxxxx>, "gichini ngaruiya" <gichini.ngaruiya@xxxxxxxxx>, "admin" <admin@xxxxxxxxxxxxxxxx>
Cc: "Xen-users" <xen-users@xxxxxxxxxxxxxxxxxxxx>
Envoyé: Samedi 1 Août 2020 22:20:25
Objet: Re: Unikraft and Virtualization.

Thus, it is not an alternative for Virtualization. It is a secure technology that running on Xen.
Right?


On Sat, Aug 1, 2020 at 8:06 PM, K. Kahurani
<k.kahurani@xxxxxxxxx> wrote:


On Sat, Aug 1, 2020 at 8:33 AM Jason Long <hack3rcon@xxxxxxxxx> wrote:
Hello,
Is Unikraft (Unikernel) an alternative for Virtualization technology?

For instance,

"The high level goal of Unikraft is to be able to build unikernels targeted at specific applications without requiring the time-consuming, expert work that building such a unikernel requires today. The main idea behind Unikraft is depicted in Figure 1 and consists of two basic components: (1) library pools containing libraries that the user of Unikraft can select from to create the unikernel and (2) a build tool and menu allowing users to pick and choose from those libraries to build images tailored to specific applications."

From [1]


Tnx.




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.