vsock - Package vsock provides access to Linux VM sockets (AF_VSOCK) for communication between a hypervisor and its virtual machines

  •        26

Package vsock provides access to Linux VM sockets (AF_VSOCK) for communication between a hypervisor and its virtual machines. MIT Licensed.For more information about VM sockets, check out my blog about Linux VM sockets in Go.

https://github.com/mdlayher/vsock

Tags
Implementation
License
Platform

   




Related Projects

HyperPlatform - Intel VT-x based hypervisor aiming to provide a thin VM-exit filtering platform on Windows

  •    C++

HyperPlatform is an Intel VT-x based hypervisor (a.k.a. virtual machine monitor) aiming to provide a thin platform for research on Windows. HyperPlatform is capable of monitoring a wide range of events, including but not limited to, access to virtual/physical memory and system registers, occurrences of interrupts and execution of certain instructions. For more details, see the HyperPlatform User Document and Programmer's Reference.

acrn-hypervisor - Project ACRN hypervisor

  •    C

The open source project ACRN defines a device hypervisor reference stack and an architecture for running multiple software subsystems, managed securely, on a consolidated system by means of a virtual machine manager. It also defines a reference framework implementation for virtual device emulation, called the "ACRN Device Model". The ACRN Hypervisor is a Type 1 reference hypervisor stack, running directly on the bare-metal hardware, and is suitable for a variety of IoT and embedded device solutions. The ACRN hypervisor addresses the gap that currently exists between datacenter hypervisors, and hard partitioning hypervisors. The ACRN hypervisor architecture partitions the system into different functional domains, with carefully selected guest OS sharing optimizations for IoT and embedded devices.

HaLVM - The Haskell Lightweight Virtual Machine (HaLVM): GHC running on Xen

  •    Haskell

The HaLVM is (C) 2008 Galois, Inc., and distributed under a standard, three-clause BSD license. Please see the file LICENSE, distributed with this software, for specific terms and conditions. The Haskell Lightweight Virtual Machine, or HaLVM, is a port of the Glasgow Haskell Compiler toolsuite to enable developers to write high-level, lightweight virtual machines that can run directly on the Xen hypervisor.

kernel virtual machine

  •    C

KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc.

Xen - Open Source Virtualization

  •    c

The Xen hypervisor is a layer of software running directly on computer hardware replacing the operating system thereby allowing the computer hardware to run multiple guest operating systems concurrently. It suppors x86, x86-64, Itanium, Power PC, and ARM processors allow the Xen hypervisor to run on a wide variety of computing devices.


runv - Hypervisor-based Runtime for OCI

  •    Go

runV is a hypervisor-based runtime for OCI. runv by default uses qemu to start virtual machines and makes use of KVM if it is supported. Please make sure qemu is installed on the machine.

coreos-vagrant - Minimal Vagrantfile for Container Linux

  •    

This repo provides a template Vagrantfile to create a CoreOS virtual machine using the VirtualBox software hypervisor. After setup is complete you will have a single CoreOS virtual machine running on your local machine.The VirtualBox provider is the default Vagrant provider. Use this if you are unsure.

rvmi - rVMI - A New Paradigm For Full System Analysis

  •    C

rVMI is a debugger on steroids. It leverages Virtual Machine Introspection (VMI) and memory forensics to provide full system analysis. This means that an analyst can inspect userspace processes, kernel drivers, and pre-boot environments in a single tool. It was specifically designed for interactive dynamic malware analysis. rVMI isolates itself from the malware by placing its interactive debugging environment out of the virtual machine (VM) onto the hypervisor-level. Through the use of VMI the analyst still has full control of the VM, which allows her to pause the VM at any point in time and to use typical debugging features such as breakpoints and watchpoints. In addition, rVMI provides access to the entire Rekall feature set, which enables an analyst to inspect the kernel and its data structures with ease.

Libvirt - The virtualization API

  •    C

Libvirt is collection of software that provides a convenient way to manage virtual machines and other virtualization functionality, such as storage and network interface management. These software pieces include an API library, a daemon (libvirtd), and a command line utility (virsh). It provides a single way to manage multiple different virtualization providers/hypervisors like Xen, OpenVZ, VirualBox, Microsoft Hyper-V hypervisor, VMware.

cloud-hypervisor

  •    Rust

This project is an experiment and should not be used with production workloads. Cloud Hypervisor is an open source Virtual Machine Monitor (VMM) that runs on top of KVM. The project focuses on exclusively running modern, cloud workloads, on top of a limited set of hardware architectures and platforms. Cloud workloads refers to those that are usually run by customers inside a cloud provider. For our purposes this means modern Linux* distributions with most I/O handled by paravirtualised devices (i.e. virtio), no requirement for legacy devices and recent CPUs and KVM.

XCP-ng - A turnkey open source virtualization platform

  •    C

XCP-ng is a virtualization platform based on Xen Source and Citrix® Hypervisor (formerly XenServer). XCP-ng stands for Xen Cloud Platform - New Generation and is a tribute to the old Open Source project XCP, which was abandoned when XenServer was open-sourced in 2013.

docker-machine-driver-xhyve - docker-machine/minikube/minishift driver plugin for xhyve/hyperkit (native macOS hypervisor

  •    Go

Master branch inherited from nathanleclaire/docker-machine-xhyve. Thanks @nathanleclaire :) If you have issues or pull-requests, Desired to be posted to this repository.docker-machine-driver-xhyve using libmachine plugin model.

docker-machine-driver-xhyve - docker-machine/minikube/minishift driver plugin for xhyve/hyperkit (native macOS hypervisor

  •    Go

Master branch inherited from nathanleclaire/docker-machine-xhyve. Thanks @nathanleclaire :) If you have issues or pull-requests, Desired to be posted to this repository. docker-machine-driver-xhyve using libmachine plugin model.

QEMU - Machine Emulator and Virtualizer

  •    C

QEMU is a generic and open source machine emulator and virtualizer. When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). By using dynamic translation, it achieves very good performance.

hyperkit - A toolkit for embedding hypervisor capabilities in your application

  •    C

HyperKit is a toolkit for embedding hypervisor capabilities in your application. It includes a complete hypervisor, based on xhyve/bhyve, which is optimized for lightweight virtual machines and container deployment. It is designed to be interfaced with higher-level components such as the VPNKit and DataKit.HyperKit currently only supports Mac OS X using the Hypervisor.framework. It is a core component of Docker For Mac.

DuNodes

  •    

DuNodes is an Hypervisor based on Cosmos OS. DuNodes should be able to span virtual machine across several nodes.

View OS: a Process with a View

  •    C

View OS is a user configurable, modular process virtual machine, or system call hypervisor. For each process the user is able to define a quot;view of the worldquot; in terms of file system, networking, devices, permissions, users, time and so on.

capstan - Capstan, a tool for packaging and running your application on OSv.

  •    Go

Capstan is a tool for rapidly building and running your application on OSv. Capstan is as simple and fast as using Docker for creating containers, but the result is a complete virtual machine image that will run on any hypervisor with OSv support.You can install Capstan either by downloading pre-built binaries or building it from sources.

infrakit - A toolkit for creating and managing declarative, self-healing infrastructure.

  •    Go

InfraKit is a toolkit for infrastructure orchestration. With an emphasis on immutable infrastructure, it breaks down infrastructure automation and management processes into small, pluggable components. These components work together to actively ensure the infrastructure state matches the user's specifications. InfraKit therefore provides infrastructure support for higher-level container orchestration systems and can make your infrastructure self-managing and self-healing. In this video, InfraKit was used to build a custom linux operating system (based on linuxkit). We then deployed a cluster of virtual machine instances on a local Mac laptop using the Mac Xhyve hypervisor (HyperKit). A cluster of 3 servers booted up in seconds. Later, after the custom OS image has been updated with a new public key, InfraKit detects the change and orchestrates a rolling update of the nodes. We then deploy the same OS image to a bare-metal ARM server running on Packet.net, where the server uses custom ipxe boot directly from the localhost. It demonstrates some of the key concepts and components in InfraKit and shows how InfraKit can be used to implement an integrated workflow from custom OS image creation to cluster deployment and Day N management. The entire demo is published as a playbook, and you can create your own playbooks too.

runq - run regular Docker images in KVM/Qemu

  •    Go

runq is a hypervisor-based Docker runtime based on runc to run regular Docker images in a lightweight KVM/Qemu virtual machine. The focus is on solving real problems, not on number of features. runq requires a host kernel >= 4.8 with KVM and VHOST_VSOCK support enabled. The easiest way to build runq and to put all dependencies together is using Docker. For fast development cycles a regular build environment might be more efficient. For this refer to section Developing runq below.