Sujet : virtualization
-
Hyper-V from PowerShell: virtual machines, checkpoints, and why a checkpoint is not a backup
Get-VM and the shape of a New-VM call, the difference between Standard and Production checkpoints, Export-VM for moving a VM, integration services, and the -ExposeVirtualizationExtensions switch that turns on nested virtualization.
-
Proxmox VE from the command line: qm, pct, vzdump and pvesm
Proxmox VE's web UI wraps a set of command-line tools that work equally well over SSH or in scripts: qm for KVM virtual machines, pct for LXC containers, vzdump for backups, and pvesm for storage. This methodology covers the core read and lifecycle commands for each.
-
FreeBSD jails: an administrative overview of jail.conf, jls, jexec and resource limits with rctl
A jail extends chroot(2) with its own process, network and (optionally) resource view, configured declaratively in jail.conf rather than via ad hoc jail(8) command lines. jls lists running jails, jexec enters one, and rctl caps what a jail's processes may consume — all administered from the host, which is also where compromise of one jail is meant to be contained.
-
Managing KVM guests with virsh: list, start, shutdown versus destroy, and autostart
virsh is the standard command-line client for libvirt-managed KVM guests. This methodology covers listing domains, the difference between a graceful shutdown and a hard destroy, setting autostart, and where to find the persistent domain definition.
-
Why NTP still runs inside virtual machines despite guest agents and paravirtual clocks
Virtual machines get time-related help from several layers — kvm-clock, guest agents, Hyper-V integration services — but none of them substitute for an NTP or chrony client running inside the guest. This article explains what each layer actually does and why time sync stays a guest-OS responsibility.
-
Checking hardware virtualization support and nested KVM before relying on it
Before installing a hypervisor or nesting a VM inside a VM, confirm the CPU exposes virtualization extensions and, for nesting, that the kvm_intel or kvm_amd module has the nested option enabled. virt-host-validate and /proc/cpuinfo give a quick answer.
Lisible par machine : JSON