SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor

VPS na wetin? Simple explanation wey go clear

VPS na private server slice for shared hardware. Learn wetin root access dey give you, how virtual machines or containers work, and the limits of your plan.

Wetin be VPS?

A VPS (virtual private server) na part of one real computer for data centre, wey dem rent give you as if na complete machine wey belong to you. Software for that computer divide am into several independent servers, and you get one of dem: your own memory allocation, your own disk space, an IP address, and administrator access to install software within the limits of your plan. E dey run all the time, and public-facing plans dey answer for an address for internet.

Make we break the three words apart, then the product go explain itself. Server na computer wey stay on and answer requests through network. Virtual mean say na software create am. Your server na partition for one bigger physical machine. Private mean say na only you get that partition. Your files and programs wey dey run no dey visible to person wey rent the slice beside your own.

If you never get root access for anything before, na this last part matter pass. VPS give you administrator access to your server environment. Wetin don already set up, and wetin you fit change, depend on the image, the virtualisation technology, and your plan.

Wetin hypervisor dey divide, and wetin e dey share

For virtual-machine VPS, the program wey dey do the dividing na hypervisor. E dey run for physical machine, wey dem dey call host. For each customer, e dey provide some pretend hardware: processor, memory block, disk, and network card. Dem install operating system for that pretend hardware, and e boot as if na real computer e own. That guest system na your VPS. KVM (kernel-based virtual machine), Xen, VMware ESXi, and Microsoft Hyper-V dey do this work. Container VPS like OpenVZ instead dey use virtualisation layer inside host operating system kernel, without separate guest kernel.

Memory and disk dey divide by space. Processor dey divide by time. Na this difference explain most of the things wey fit surprise person later. Assigned memory no automatically mean say physical RAM reserve don dey wait for you: KVM support memory overcommit, and host fit swap guest memory. Your disk na file or logical volume for host storage, and e remain your own until you delete am. Your virtual cores na queues wey lead go host real cores, and hypervisor dey schedule which guest go run next.

One command fit identify the virtualisation wey e detect.

systemd-detect-virt
uname -r

systemd-detect-virt dey print kvm for KVM VPS, meaning say full hypervisor boot one kernel wey belong to you alone. E dey print lxc or openvz for those container technologies, where your server na fenced-off area inside host own operating system, and kernel dey shared with other containers for the same box; container-other mean say e detect another container environment. E dey print none when e no detect any virtualisation. This difference get real consequences, because shared kernel na kernel wey you no fit change. For shared-kernel container, host dey control module loading, so in-kernel feature like WireGuard VPN module need host support. For shared-kernel container, uname -r normally dey report host kernel release, but container runtimes no dey behave the same way: gVisor dey run containers without sharing host kernel, and the official example for am report 5.15.0-gvisor. For KVM server, the same command go show kernel wey dem install inside your own guest, and you fit upgrade or replace am the same way you go do for any other machine.

Wetín virtual mean for here?

Because na software make up the server, provisioning no need person rack new physical machine for you. Nobody dey rack hardware for you. Dem build am from template image, so rebuild go put clean Ubuntu back, but e go still erase everything wey dey inside the existing disk. Most provider panels fit also take snapshot of the disk before you try risky thing, resize the plan with reboot, and move your guest go different hardware when the host underneath need work.

The price follow from this same fact: many customers dey pay for one physical machine at the same time. Na why VPS cost wetin e cost compared with renting whole server.

The cost dey close to the benefit. Dem dey share the hardware underneath, so busy neighbour fit become your own problem too. The section about limits below get the command wey go measure am.

Wetin private mean for here?

Private mean isolation, and e good make we explain exactly how much isolation you get. You get your own root filesystem, your own user accounts, and your own process list. Virtual-machine VPS also get its own kernel, while OpenVZ container share the host kernel. Another customer for the same host no fit list your processes or read your files, because their guest no get route enter your memory or virtual disk. Virtual machines dey run separate operating systems, while shared-kernel containers dey isolate their users and programs inside one operating system. But this privacy stop for the host itself: whoever dey run the hypervisor fit read your guest memory anytime. To close that last gap, you need the encrypted-memory hardware wey confidential computing for VPS describe.

Shared hosting dey work the other way. You get one directory for a machine wey dey serve hundreds of other websites, one control panel, and any software wey provider choose install. No apt install dey there, because when you install package, e dey change the whole machine, and the whole machine no be your own to change. Shared hosting compared with VPS explain the trade in detail. For one line: shared hosting rent account give you, while VPS rent computer give you.

VPS spec sheet wey get one line after another

Dem dey sell every VPS as short list of numbers. Na illustrative mid-range plan be this one, and na am we go use as example for the rest. These figures na example; dem no be quote or market survey for any particular date.

ChartAn illustrative mid-range VPS plan
Di data wey dey behind dis chart
[
  {
    "plan": "Example mid-range VPS",
    "vcpu_cores": 4,
    "ram_gb": 16,
    "nvme_gb": 160,
    "bandwidth_tb": 8,
    "ipv4_addresses": 1
  }
]

That one line na the whole product. Read am from left to right.

4 vCPU. vCPU (virtual central processing unit) na virtual processor wey hypervisor dey schedule for the host processors. Unless the plan talk say e dedicated, na share of that thread e be, no be reserved processor. Inside the server, nproc normally dey print 4. E dey count the processors wey current process fit use; CPU affinity and supported cgroup CPU quotas fit reduce the number, while OMP_NUM_THREADS and OMP_THREAD_LIMIT dey set the minimum and maximum values e fit return, respectively, and nproc --all dey count every installed processor. lscpu dey show model name. Depending on how dem configure the host, the name fit be the real host CPU or generic QEMU model.

16 GB of RAM. The plan dey specify memory allocation or limit, but this one alone no guarantee say physical RAM dey reserved for the host. free -h dey report usable memory for binary units, after e exclude kernel and reserved memory regions. So compare the provider GB or GiB units before you judge the difference. Any extra memory beyond your allocation depend on the plan and virtualisation configuration.

160 GB of NVMe. NVMe (non-volatile memory express) na the way the drive dey connect inside the host, and e dey much faster than SATA SSDs wey older plans use. Your share go appear as virtual disk, normally /dev/vda under KVM. df -h / dey report root filesystem for binary units, so the size wey e display go differ from disk wey dem advertise in decimal GB. E also exclude space wey other partitions and filesystem metadata dey use. The available figure go lower again because ext4 dey reserve 5 percent of the filesystem for root by default. Wetin the SSD for SSD VPS actually mean and how to verify the disk wey dem sell you explain the matter more.

8 TB of transfer. This one na data wey move every month, and dem usually count outbound traffic only. E na volume, while port speed na separate number wey the plan specify. If you pass the allowance, provider fit charge you or throttle the traffic, so read that line before you host video. sudo apt install vnstat go give you your own count with vnstat -m, starting from the day you install am.

1 IPv4 address. The address na your own for as long as you rent the server. You fit point domain to am and accept traffic for ports wey your firewall and provider network policy allow; reverse DNS settings too depend on the provider. Very cheap plans sometimes put many customers behind one shared address. Dem dey call this NAT VPS, and then ip -4 addr show go report private address like 10.0.0.5, while inbound ports go limited.

Four commands go confirm wetin dem give you.

nproc
free -h
df -h /
ip -4 addr show

If any of them no match the spec sheet beyond the rounding wey we describe above, e worth opening support ticket before you build anything for the machine.

Wetin root access mean for real life

Root na administrator account for Linux, and e user ID na 0. Run id -u and you go see 0 when you be root. Root fit install packages for the whole system, open ports below 1024 (by default, kernel reserve dem for root or processes wey get CAP_NET_BIND_SERVICE, so non-root process wey get that capability fit bind to port 80 without lowering net.ipv4.ip_unprivileged_port_start), read and edit system files, and destroy the system with one careless command; loading modules and replacing the kernel need control of the kernel, and shared-kernel containers no provide that. Nobody go undo that for you.

The practical difference short. For shared hosting, you open support ticket to ask for one software. For VPS, you type this.

sudo apt update
sudo apt install -y nginx
systemctl status nginx

For Ubuntu image wey dey use systemd, systemctl status nginx suppose print active (running) after installation. The server IP address for browser suppose show default nginx page if port 80 dey reachable. If status print failed, run journalctl -u nginx -n 50 and read the last lines, because the service dey record why e refuse to start. The usual reasons na typo for config file, or another program already dey listen on port 80.

Root na also your complete security boundary, and access dey come through the login method wey you configure for the server, like SSH key or password. The first session for new server no be the right time to install applications. Create ordinary user, move your login go SSH key, and put firewall in front of the ports. The first ten minutes for new VPS na that checklist in order, SSH key basics dey explain the login itself, ufw firewall basics dey explain the ports, and least privilege users dey explain wetin your services suppose run as afterwards. Monitor SSH service logs with journalctl -u ssh -f for login attempts.

Wetin be the limits of a VPS?

The processor dey shared, and you fit measure the sharing. Steal time na the portion of time wey your virtual CPU ready to run but e get nothing, because the hypervisor give the physical core to another guest.

vmstat 1 5

The st column na steal time. Small steal-time spikes fit happen for shared hosts. If double-digit figure dey remain steady while your own processes dey idle, e usually mean say the host get more workload than e fit handle, and no tuning inside your server go fix am, because the waiting dey happen outside your server. Hostinger dey separate CPU steal from its CPU credit system; its CPU credit policy restores full capacity after usage drops and credits build again reach the recovery threshold. Read your plan's CPU policy before you blame your neighbours. How to benchmark VPS properly shows how to prove am before you report am to the provider. KVM and Xen guests dey report steal. For containers, the reported value depend on how CPU statistics dey exposed, and e no be reliable measure of the container's CPU throttling.

The memory fixed, and the ceiling dey come suddenly. When memory don finish and reclaim no fit free enough, the kernel's OOM (out of memory) killer go choose one process and end am with SIGKILL.

sudo dmesg -T | grep -i "out of memory"

One line fit explain outage wey otherwise go look like mystery:

Out of memory: Killed process 2412 (mysqld) total-vm:2183104kB, anon-rss:1897224kB, file-rss:0kB

The application's own log usually no go talk anything, because SIGKILL no give the process chance to write anything. Check the kernel log for the reason; whether a container fit access that log depend on the host's configuration. Check whether swap dey configured before you add swap file, and check the host's rules for a container VPS.

The disk fast and e dey shared. The host's NVMe fast, and your own portion dey compete with every other guest for input and output operations. Benchmark wey you take during quiet hour no be promise say the same machine go perform like that during peak time.

The hardware no be your own to touch. You no fit plug anything inside. No USB device, no capture card, and no graphics card unless the plan intentionally pass one through, and that one na separate product: VPS wey get GPU.

Na exactly one instance dey. A VPS na one machine. Host fault fit bring your server down; whether the provider go migrate am or restart am somewhere else depend on the service, and application failover still need arrangement. Backups na your responsibility, so restic backups from VPS suppose dey on your setup list. Provider snapshot convenient, but its protection depend on where dem store am and how long dem retain am; keep one independent backup too.

Support stop for the hypervisor. For unmanaged plan, the provider dey keep the hardware, network, and virtualisation layer healthy. Everything from operating system upward na your responsibility, including security updates. Managed hosting versus unmanaged hosting explain where that line dey, and unattended upgrades on Ubuntu na the smallest useful thing to switch on.

How VPS dey compare with things wey people dey confuse am with

A virtual machine na guest wey get virtual hardware and im own operating system kernel; VPS na rented server product wey dem build either as virtual machine or as container, usually with public address and network wey don already attach. A VPC (virtual private cloud) na private network inside bigger cloud, and servers dey inside am, so e dey answer different question entirely. VPS against VM against VPC separate the three terms properly.

A dedicated server na the complete physical machine wey dem reserve for you, without other customers' guests sharing am; you fit install hypervisor by yourself. E dey useful when steal time or disk contention na your real bottleneck. VPS against dedicated server list the points wey you need consider.

A VPN (virtual private network) share two letters with VPS and nothing else. VPN na encrypted tunnel between machines. VPS na machine, and one popular way to use am na to run your own VPN, na from there the confusion dey start. VPS against VPN settle the difference between the two words.

Hardware wey you own, or hypervisor like Proxmox for machine wey dey your house, give you control of the hardware and residential connection wey many services dey treat with suspicion. E also give you the host itself, so guest fit run im own hypervisor after you enable nested virtualization in Proxmox, something rented VPS must also support explicitly. Proxmox against VPS weigh power, noise and uptime against monthly fee.

Wetin people dey run for VPS?

The honest answer na software wey fit the VPS operating system, architecture, resources, and provider rules. Common choices na website with database, private VPN, game server, status monitor, mail server, media library, or coding agent wey go continue work while your laptop dey closed. Mail need policy check first: DigitalOcean, for example, blocks SMTP ports 25, 465 and 587 for Droplets by default. Network services dey listen on ports, so wetin port be for Linux na the next concept wey worth learning, and wetin you fit do with VPS get the longer list plus the resource cost of each one.

FAQ

VPS na the same thing as virtual machine?

VPS na server wey company rent give you, with operating system, usually public IP address, and price attached. E fit be virtual machine wey get im own kernel, or container like OpenVZ VPS wey dey share host kernel. The words no mean exactly the same thing: "virtual machine" describe any guest wey dey run for hypervisor, including one for your own laptop, while "VPS" describe the product wey you buy. VPC na another thing entirely: private network inside cloud provider, instead of server.

I need to know Linux before I fit use VPS?

You need small knowledge, and you fit learn the rest as you dey use am. The starting set na to connect with ssh, move around with cd and ls, edit file with nano, install software with apt, and read logs with journalctl. Unmanaged VPS assume say na you go handle updates and firewall yourself. If that one pass wetin you want do, compare the price and responsibilities of managed plan or control panel.

Why my VPS dey show RAM wey small pass wetin the plan promise?

Linux report usable memory, while the plan advertise assigned memory. Kernel image and some reserved memory regions dey subtract before free -h calculate the total; the binary units too different from decimal GB, so check the units wey provider dey use. Compare allocation, units, and reserved memory before you judge the difference. If the shortfall no get explanation, e worth support ticket.

Wetin be steal time, and I suppose worry about am?

Steal time na percentage of time wey your virtual CPU ready to run but must wait because hypervisor give the physical core to another guest. The st column for vmstat 1 show am. Small steal-time spikes fit happen for shared hardware. If double-digit figure continue while your own load low, e usually mean say physical host get too many workloads, and the solution na different host or different plan, because nothing inside your server control the host scheduler. CPU usage caps too limit performance, and recovery follow provider policy, including rebuilding CPU credits where required.

I fit run more than one service for one VPS?

Yes. Na the reason root access dey useful: the machine na general-purpose system, and services fit coexist as long as dem fit inside memory and each one listen on im own port. Memory usually na the first limit wey you go meet, while disk speed na the second. Mail na the awkward exception, because delivery depend on the reputation of your IP address and provider SMTP policy, plus the mail server itself.

Dis article help you?