Running servers and other software in Virtual Machines in the cloud or on local hardware
The official Ubuntu images that are built for Azure/Hyper-V really are only compatible with Hyper-V on Azure, but there is a solution…
This guide provides and important step missing from any articles I could find on converting from a Windows 7 physical machine to a Hyper-V (or other) virtual machine.
These are notes on creating a Windows and Linux hybrid environment, specifically when running Windows in a Libvirt/KVM VM.
Whether you want old school ARM (32-bit) or a shiny new UEFI ARM (32-bit) virtual machine in Libvirt/KVM, and automated or ‘manual’ creation, there is a way to get what you want. This post introduces the four ARMs and will point to the four posts as they are added.
Create a non-EFI (old school) ARM hardfloat virtual machine for Libvirt/KVM using a traditional interactive Debian install.
Create an UEFI (newish) ARM hardfloat (32-bit) virtual machine for Libvirt/KVM using a traditional interactive Debian install.
Create a non-EFI (old school) ARM hardfloat virtual machine for Libvirt/KVM using packer to automate a repeatable process.
Create an UEFI (newish) ARM hardfloat (32-bit) virtual machine for Libvirt/KVM using automated image build using Packer.
The fastest and most practical way to build software for armel is to cross-compile on an x86_64 machine even for a Linux 2.6-series kernel
On using a Debian ‘cloud’ image and cloud-init on a ‘bare-metal’ host for fast deployment.
Getting good performance with Windows 11 Pro running under Libvirt/KVM on Linux requires some special configs, especially if one wants to enable WSL2 (which requires ‘Nested virtualization’). This is a brief cheatsheet on the required configuration.