jhvst
terraform-provider-libvirt
jhvst | terraform-provider-libvirt | |
---|---|---|
1 | 13 | |
- | 1,520 | |
- | - | |
- | 6.8 | |
- | 24 days ago | |
Go | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jhvst
-
NixOS 22.11 “Raccoon” Released
Plugging my own thing here, but I have been experimenting with a Nix configuration for gaming only. My configuration is here (for Nvidia, which does not work without tinkering as AMD does) : https://github.com/jhvst/nix-config/blob/main/nvidia.nix
First, this is a whole system specification. This means that executing this on Nix will build you a whole OS image. You can build the image if you have Nix by running the first line on file. You can also use Docker with the instruction on my README: https://github.com/jhvst/nix-config
Back to elaborating on the Nix file from the gaming perspective. First, we have the overlays. These are like patches to the packages, and really useful for gaming because it allows building important packages like mesa from the source tip. This is particularly useful when new games or GPUs are released. Same thing for wayland: Nvidia and its proprietary drivers need some patching, but it's possible to get wayland (and sway) to work this way.
Then, I have taken the reproducibility of Nix to a next step in my opinion, and made the system stateless. This means that it runs from the RAM. It is easy to create installation media like kernel, initrd, and rootfs because you have all the steps to create the distribution. This means that here, Nix works as a meta-distro like Gentoo, on top of which you develop your own. Running from the RAM means that theoretically, if you have a working config, and two people with different hardware runs it, then they should have the same experience. If you look at ProtonDB, you often find that some people claim that game X works on their machine with drivers and mesa of Y and Z, but there is no way to copy their configurations because it's certain that the user has made some stateful changes which they have forgotten hence left undocumented, which is the reason it works for them. If everyone would be using Nix, you could reproduce their system and possibly fix your own, but this is not tractable with most OSs.
If you like to test my changes, you can read more about my approach here: https://github.com/NixOS/nixpkgs/pull/203750
For testing I distribute Nvidia as documented here: https://github.com/jhvst/jhvst.github.io/blob/main/ramdisk.m...
However, I have developed it bit further: if you manage to get into an iPXE shell, you can write `boot -a http://boot.ponkila.com/menu.ipxe`, then select the second option which is Nvidia (proprietary drivers), and with some waiting you will get into a shell prompt to which you can write `sway --unsupported-gpu`, which will launch sway. Cmd+Enter opens a prompt to which you can write `steam`, which will open Steam. Then, you have to mount some drive on another shell with `mount`, and add this as a Steam library via Steam's UI. Then you can play games. I use this on AMD and I have been very happy.
terraform-provider-libvirt
- What do y'all use to provision KVM VM's?
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.26
libvirt-terraform-provider ( based on https://github.com/dmacvicar/terraform-provider-libvirt )
- NixOS 22.11 “Raccoon” Released
-
libvirt-ocp4-provisioner - Provision an OCP 4.x.y cluster in minutes with Ansible, now with Single Node OCP support! .
Hi guys!I wanted to allotment with you a tool to provision a fully working OCP 4.x.y cluster in minutes using Ansible for automation, libvirt as virtualization provider and terraform as VMs templating and creation tool. https://github.com/kubealex/libvirt-ocp4-provisioner It will take care of all the infrastructure provisioning and OCP machines provisioning, starting and completing the UPI installation of a cluster. (IPI work in progress ;) ) To give a quick overview, this project will allow you to provision a fully working OCP stable environment, consisting of: * Bastion machine provisioned with: * dnsmasq (with SELinux module, compiled and activated) * dhcp based on dnsmasq * nginx (for ignition files and rhcos pxe-boot) * pxeboot * Loadbalancer machine provisioned with: * haproxy * OCP Bootstrap machine * OCP Master(s) VM(s) * OCP Worker(s) VM(s) From latest release, it also supports installing SNO on a single host! It also takes care of preparing the host machine with needed packages, configuring: * dedicated libvirt network (fully customizable) * dedicated libvirt storage pool (fully customizable) * terraform * libvirt-terraform-provider ( compiled and initialized basedon https://github.com/dmacvicar/terraform-provider-libvirt) PXE is automatic, based on MAC binding to different OCP nodes role, so no need of choosing it from the menus, this means you can just run the playbook, take a beer and have your fully running OCP 4.9.latest stable up and running. It has been tested on Fedora 3x and CentOS 7/8. Playing around with it and contributions to make it work even on different OSes is more than welcome, hope you enjoy it! Alex
-
Need help on Terraform with KVM/Libvirt
I learned and got terraform to work with the KVM/Libvirt provider.
-
Automate creation of KVM VM and Installation of OS
I saw Terraform with the dmacvicar/terraform-provider-libvirt provider, but sadly didn't get really warm with it. When some can explain to me how I can set up new images for every VM I would be very happy also there are more question in the pipeline. Sadly, the “Documentation” is not really that good. Maybe Terraform is also the wrong Application for me. I'm a little lost because I thought Terraform would be the big Solution I want and need, until now, not yet.
-
Terraform Persistent Storage
It looks like there was an issue dealing with "attaching an existing disk" to a terraform created VM. That's here: https://github.com/dmacvicar/terraform-provider-libvirt/issues/688
-
Those of you running a home cluster that is NOT comprised of RasPis, what hardware are you using?
Nice. I’m straight KVM as it’s a mirror of work (my Lab) and I’m using the terraform-provider-libvirt provider. 20 minutes to fully build a site. Pretty cool.
-
Provision a full functional cluster in less than 10 minutes! libvirt-k8s-provisioner
libvirt-terraform-provider ( compiled and initialized based on https://github.com/dmacvicar/terraform-provider-libvirt)
- QEMU Version 6.0.0 Released
What are some alternatives?
vanitygen-plusplus - A vanity address generator for BTC, ETH, LTC, TRX and 100+ more crypto currencies.
UTM - Virtual machines for iOS and macOS
terraform-provider-proxmox - Terraform provider plugin for proxmox
terraform-provider-rancher2 - Terraform Rancher2 provider
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
libvirt-k8s-provisioner - Automate your k8s installation
xemu - Original Xbox Emulator for Windows, macOS, and Linux (Active Development)
guestfs-tools - Tools for accessing and modifying guest disk images
libguestfs - library and tools for accessing and modifying virtual machine disk images. PLEASE DO NOT USE GITHUB FOR ISSUES OR PULL REQUESTS. See the website for how to file a bug or contact us.
cilium - eBPF-based Networking, Security, and Observability
xqemu - Open-source emulator to play original Xbox games on Windows, macOS, and Linux
k8s-lab-terraform-libvirt - A Kubernetes lab environment using terraform and libvirt