Virtualization, VMs and Proxmox
Split ROBUST and regions into virtual machines without adding physical servers.
Definition: hypervisor
A hypervisor allows multiple operating systems to share a physical host. Proxmox VE is an open-source virtualization management platform: it supports KVM virtual machines, LXC containers, networks and backups. Proxmox is neither ROBUST nor an internet hosting provider.
Definition: VM and LXC container
A VM runs a guest OS with its virtual disk, allocated RAM and virtual NIC; depending on the host, it may run Linux or Windows. An LXC container shares the host Linux kernel with a different isolation model: often lighter, but not identical to a VM for security or compatibility. Separate VMs are generally easier to reason about as a beginner.
CPU: physical core, thread and vCPU
A physical CPU contains cores executing workloads; some expose multiple hardware threads per core. A vCPU is the processor allocation visible to a guest. Giving a VM eight vCPUs does not create eight physical cores. For OpenSimulator, monitor CPU contention, latency and simulator processes; avoid indiscriminately overallocating guests without measurements.
RAM, swap and virtual disks
Allocated VM RAM must leave headroom for the host. A guest can report free/cacheable RAM while the physical host is pressured; monitor both levels. Virtual disks sit on physical storage: track IOPS, latency, capacity and inodes, especially for FSAssets. A snapshot is not automatically a complete or off-site backup.
Networking: bridge, private IP and public IP
A Proxmox network bridge (for example vmbr0) virtually connects VM interfaces. Provider setups may require a private NAT network, additional public IP addresses or specific routing. Never assign the same public IPv4 arbitrarily to several VMs. Proxmox, guest and provider firewalls may all apply.
A simple two-VM design
On one Proxmox server: Ubuntu VM 1 runs ROBUST, MySQL and perhaps a web service; Ubuntu VM 2 hosts one or more OpenSim simulator processes. Both communicate over a protected private network. Public access reaches only the required services and regions. This separation simplifies maintenance but does not provide high availability if the physical host fails.
Illustrative example: adapt to the actual installation.
Serveur physique / Physical host
Proxmox VE
VM 1 : Ubuntu + ROBUST + MySQL (+ Web)
VM 2 : Ubuntu + OpenSim regions
Bridge privé -> échanges entre VM
Routage / pare-feu -> seuls ports publics nécessairesMaintenance and recovery
Document restarts in dependency-aware order, back up VMs and also keep consistent SQL plus FSAssets backups. Before increasing resources, measure actual RAM usage, CPU load, disk and response times. Rebooting the hypervisor interrupts all its VMs.