home.social

#cloudhypervisor — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cloudhypervisor, aggregated by home.social.

  1. Cool, KVM-based AMD SEV-SNP support was recently added to Cloud Hypervisor! Including support for Google's oak stage0 firmware and IGVM image format.
    github.com/cloud-hypervisor/cl

    #ConfidentialComputing #virtualization #KVM #CloudHypervisor

  2. Cool, KVM-based AMD SEV-SNP support was recently added to Cloud Hypervisor! Including support for Google's oak stage0 firmware and IGVM image format.
    github.com/cloud-hypervisor/cl

    #ConfidentialComputing #virtualization #KVM #CloudHypervisor

  3. Cool, KVM-based AMD SEV-SNP support was recently added to Cloud Hypervisor! Including support for Google's oak stage0 firmware and IGVM image format.
    github.com/cloud-hypervisor/cl

    #ConfidentialComputing #virtualization #KVM #CloudHypervisor

  4. Cool, KVM-based AMD SEV-SNP support was recently added to Cloud Hypervisor! Including support for Google's oak stage0 firmware and IGVM image format.
    github.com/cloud-hypervisor/cl

    #ConfidentialComputing #virtualization #KVM #CloudHypervisor

  5. Cool, KVM-based AMD SEV-SNP support was recently added to Cloud Hypervisor! Including support for Google's oak stage0 firmware and IGVM image format.
    github.com/cloud-hypervisor/cl

    #ConfidentialComputing #virtualization #KVM #CloudHypervisor

  6. ⛔️ "Cloud Hypervisor si schiera contro l'IA: è vietato l'uso di codice generato artificialmente! Un passo coraggioso o uno step indietro? #CloudHypervisor #AIdebate"

    🔗 tomshw.it/business/cloud-hyper

  7. ⛔️ "Cloud Hypervisor si schiera contro l'IA: è vietato l'uso di codice generato artificialmente! Un passo coraggioso o uno step indietro? #CloudHypervisor #AIdebate"

    🔗 tomshw.it/business/cloud-hyper

  8. ⛔️ "Cloud Hypervisor si schiera contro l'IA: è vietato l'uso di codice generato artificialmente! Un passo coraggioso o uno step indietro? #CloudHypervisor #AIdebate"

    🔗 tomshw.it/business/cloud-hyper

  9. #virshle

    The documentation gets better! 🤓

    Manage multiple #VM on remote nodes/servers through a single cli.

    #rust #cloudhypervisor #ipv6 #nixos #linux
    github.com/pipelight/virshle

  10. #virshle

    The documentation gets better! 🤓

    Manage multiple #VM on remote nodes/servers through a single cli.

    #rust #cloudhypervisor #ipv6 #nixos #linux
    github.com/pipelight/virshle

  11. @qyliss Similar situation with . I really could use user space networking with it, so I wrote a quick backend for its UNIX socket target. Maybe you can reuse that same mechanism + tool with - just implement a UNIX socket network backend 😁

    github.com/agraf/slirp-unix

  12. @qyliss Similar situation with #VirtualizationFramework. I really could use user space networking with it, so I wrote a quick #Slirp backend for its UNIX socket target. Maybe you can reuse that same mechanism + tool with #CloudHypervisor - just implement a UNIX socket network backend 😁

    github.com/agraf/slirp-unix

  13. @qyliss Similar situation with #VirtualizationFramework. I really could use user space networking with it, so I wrote a quick #Slirp backend for its UNIX socket target. Maybe you can reuse that same mechanism + tool with #CloudHypervisor - just implement a UNIX socket network backend 😁

    github.com/agraf/slirp-unix

  14. @qyliss Similar situation with #VirtualizationFramework. I really could use user space networking with it, so I wrote a quick #Slirp backend for its UNIX socket target. Maybe you can reuse that same mechanism + tool with #CloudHypervisor - just implement a UNIX socket network backend 😁

    github.com/agraf/slirp-unix

  15. @qyliss Similar situation with #VirtualizationFramework. I really could use user space networking with it, so I wrote a quick #Slirp backend for its UNIX socket target. Maybe you can reuse that same mechanism + tool with #CloudHypervisor - just implement a UNIX socket network backend 😁

    github.com/agraf/slirp-unix

  16. One thing that's been annoying up to now about developing individual #SpectrumOS VMs has been that #CloudHypervisor can't do a virtual network device unless it's privileged. I can run the VM in #QEMU instead, which has a user-mode networking implementation and so doesn't need privileges, but then I can't test features that QEMU doesn't have.

    But I just realised that as of recently it should be possible to run a cloud-hypervisor VM with a QEMU virtual network device using vfio-user!

  17. #AmpereComputing Joins Intel, AMD, Arm, Microsoft & Others backing the #CloudHypervisor Project hosted by the #LinuxFoundation as a Rust-written #VMM focused on running modern cloud workloads in a fast and secure manner. bit.ly/3FZv5iK #hypervisor

  18. #AmpereComputing Joins Intel, AMD, Arm, Microsoft & Others backing the #CloudHypervisor Project hosted by the #LinuxFoundation as a Rust-written #VMM focused on running modern cloud workloads in a fast and secure manner. bit.ly/3FZv5iK #hypervisor

  19. Joins Intel, AMD, Arm, Microsoft & Others backing the Project hosted by the as a Rust-written focused on running modern cloud workloads in a fast and secure manner. bit.ly/3FZv5iK

  20. #AmpereComputing Joins Intel, AMD, Arm, Microsoft & Others backing the #CloudHypervisor Project hosted by the #LinuxFoundation as a Rust-written #VMM focused on running modern cloud workloads in a fast and secure manner. bit.ly/3FZv5iK #hypervisor