Running a Virtual Machine on Unraid

What a Virtual Machine Is

A virtual machine is a complete, self-contained computer that exists as software, running inside your real server. It has its own operating system, its own memory, and its own hard drive - all pretended into being by your server.

Picture your server politely setting aside a corner of itself and saying, "this corner will now behave exactly like a separate PC." Inside that corner you can install Windows or Linux, just as if it were a real desktop tower under your desk. It does not know it is a guest - it just runs.

• You get an extra computer without buying another box.
• It is completely separate, so what happens inside stays inside.
• You can create it, copy it, or delete it in minutes.

Why You'd Want One on Unraid

A virtual machine shines when you need a real, full computer for a specific job - but do not want to buy, power, and find room for another physical PC.

Because your server is likely already running around the clock, a VM gives you an extra computer that is always available, without a second machine humming in the corner and adding to your power bill.

• A spare Windows PC - for a program that only runs on Windows, kept separate from your main computer.
• A safe place to experiment - try software you are unsure about without risking your everyday machine.
• An always-on computer - something that stays running on the server for a task, even when your laptop is off.
• Learning - practice with Linux or a new operating system with nothing to lose.

VM vs. a Container - When to Use Each

Unraid can run apps two ways: as a lightweight "container" or as a full virtual machine. They solve different problems, and picking the right one saves you a lot of grief.

A container packages up a single app and just enough to run it - light, quick, and easy. A virtual machine is a whole computer with a full operating system - heavier, but able to do anything a real PC can. Most home-server apps run beautifully as containers. A VM is for when you truly need a complete computer.

The Requirements

Before you can run a virtual machine, your server needs a couple of things in place. The good news is that most computers made in the last decade have them.

If you are not sure whether virtualization is switched on, Unraid will usually tell you when you try to turn on the VM feature. If it is off, it is a quick change in the startup settings - though the exact wording varies by computer.

• A processor that supports virtualization - a feature called VT-x on Intel chips, or AMD-V on AMD chips. Most modern processors have it.
• That feature switched on - it lives in your computer's startup settings (the BIOS), and is sometimes turned off by default.
• Spare memory (RAM) - the VM needs its own slice, on top of what your server and other apps already use.
• Some free disk space - the VM's pretend hard drive is a large file that has to live somewhere.

Turning On the VM Feature

Virtual machines are switched off in Unraid until you turn them on. It is a single setting, and once it is on, a new area appears for managing your VMs.

In the Unraid web page, look for the settings area, and within it a section for VM Manager or similar. There you will find a switch to enable virtual machines. Flip it on and save, and a new "VMs" tab appears along the top for creating and managing your machines.

• A new VMs tab or area shows up once the feature is on.
• Unraid may check that your processor's virtualization is enabled.
• If something is missing, it usually tells you what to fix.

Getting an Operating-System Install File (ISO)

To install an operating system into your VM, you need its installer as a single file called an "ISO." Think of an ISO as a disc-in-a-file - the same thing that used to come on a DVD, now just a download.

You download the ISO for the system you want - Windows or a flavor of Linux - straight from its official source. When you create your VM, you point it at this file, and the VM "boots" from it just as an old PC would boot from an install DVD.

• Windows - Microsoft offers an official download of the Windows installer.
• Linux - each version (such as Ubuntu or Mint) offers a free download on its site.
• Store the file on your server - many people keep a shared folder just for ISOs.

Creating a Basic Windows or Linux VM

With the feature on and an ISO ready, creating a VM is mostly filling in a friendly form. Unraid provides templates that fill in sensible defaults for you.

The templates do the heavy lifting - they know the sensible settings for each kind of system, so you mostly confirm rather than invent. Do not worry about getting everything perfect; you can change most settings later.

• Open the VMs tab and choose to add a new VM.
• Pick a template - there are ready-made ones for Windows and for Linux.
• Give the VM a clear name, like "Windows Test" or "Linux Lab."
• Point it at your ISO file for the operating system.
• Set how many processor cores, how much memory, and how big a disk (next chapter).
• Create it, then start it to begin the operating-system install.

Assigning Cores, Memory, and Disk

When you create a VM, you decide how big a slice of your server it gets: how many processor cores, how much memory, and how large its virtual hard drive. Sensible portions keep both the VM and the server happy.

There is no single right answer - it depends on the job. A light Linux machine needs little; a Windows desktop wants more. When unsure, start modest. You can usually adjust later if it feels cramped.

• Processor cores - how much thinking power the VM gets. Two is plenty for a basic machine; do not hand over all your cores.
• Memory (RAM) - the VM's working space. A few gigabytes suits a simple VM; give it enough to be comfortable but leave lots for the server.
• Disk size - how big its pretend hard drive is. This becomes a large file on your server, so match it to what you actually need.

Viewing the VM's Screen (VNC)

Your virtual machine has a screen, but there is no monitor plugged into it. So how do you see it? Through a viewer called VNC, right inside your web browser.

VNC is simply a way to see and control a computer's screen over the network. Unraid builds it in: next to your VM there is a button - often a little screen icon labeled VNC - that opens the VM's display in a new browser tab. From there you use your keyboard and mouse just as if you were sitting in front of it.

• Click the VNC button and the VM's screen opens in your browser.
• You will watch the whole install happen through this window.
• It works from any computer on your network, no monitor needed.

Installing the Operating System

Once you start a new VM and open its screen, it boots from your ISO and greets you with the same installer you would see setting up a real PC. From here, it is just like installing Windows or Linux on any computer.

You follow the on-screen steps: choose your language, agree to the terms, pick the virtual disk to install onto, and let it copy the files. It takes a while, just as it would on real hardware. When it finishes, the VM restarts into a fresh, working operating system.

• Install onto the virtual disk you created - it is the one that appears inside the VM.
• Let it finish and restart fully before you judge how it is running.
• Set a password you will remember, just like on a real computer.

The Helper Drivers (VirtIO), Simply

A virtual machine runs faster and smoother when it has a small set of helper drivers made just for virtual hardware. On Unraid, these are called the VirtIO drivers. You mostly need this on Windows VMs.

A "driver" is just a little piece of software that teaches an operating system how to talk to a piece of hardware. Because a VM's hardware is pretend, it benefits from special drivers built for that pretend hardware. These make the network, the disk, and the screen behave better. Linux usually has them built in; Windows often needs them added.

• VirtIO drivers help a VM run more smoothly and quickly.
• Unraid can provide them as a second ISO you attach to the VM.
• You install them inside the VM, once, after the operating system is up.

Starting and Stopping a VM

Once your VM exists, running it is as simple as flipping a switch. In the VMs area, each machine has controls to turn it on, turn it off, and pause it - much like the power button on a real PC.

Whenever you can, use the gentle shut down rather than a force stop, just as you would not yank the plug on a real computer. A graceful shutdown lets the VM close its files properly.

• Start - powers the VM on. Open its VNC screen to use it.
• Shut down - asks the VM to close gracefully, like choosing Shut Down inside it.
• Pause - freezes it in place so you can resume exactly where you left off.
• Force stop - a hard power-off, for when a VM is stuck and will not respond.

Snapshots and Backing Up a VM

A virtual machine's entire hard drive is really just a big file on your server. That is wonderful news, because it means backing up a whole computer is as simple as copying that file somewhere safe.

To back up a VM, you shut it down and copy its virtual disk file to another location - another drive, or an off-site backup. If the VM ever breaks, you copy the good file back and you are running again. Some setups also support "snapshots": a saved moment in time you can jump back to if a change goes wrong.

• Before a big change inside the VM, make a copy of its disk file first.
• Keep a backup of any VM you would hate to rebuild from scratch.
• Store at least one copy somewhere other than the server itself.

Passing a Graphics Card to a VM (Advanced)

There is an advanced trick where you hand one of your server's physical graphics cards directly to a VM, so that VM can drive a real monitor and do heavy graphics work - even gaming. It is powerful, and it is genuinely advanced. I am mentioning it, not walking you through it.

This is called "GPU passthrough," and it turns a VM into something close to a real gaming or workstation PC. It is a favorite of enthusiasts. But it involves fiddly hardware settings, and getting it wrong can make the whole server unstable or refuse to start properly. It is not a beginner project.

• Know that it is a big step up in difficulty from a basic VM.
• It touches low-level hardware settings that can affect the whole server.
• Read current, specific guides for your exact graphics card and hardware.

Performance Tips

A virtual machine will never feel quite as snappy as a brand-new PC, but a few simple habits keep it running well without starving the rest of your server.

If a VM feels sluggish, resist the urge to just throw all your resources at it. More often the fix is a helper driver, faster storage, or simply closing programs you are not using inside the VM.

• Right-size it - give the VM enough cores and memory to be comfortable, but no more than it needs.
• Install the helper drivers - VirtIO drivers make a Windows VM noticeably smoother.
• Put the VM's disk on fast storage - an SSD makes a VM feel far quicker than a spinning drive.
• Shut down VMs you are not using - a stopped VM frees its resources for everything else.

When a VM Is Overkill

Virtual machines are impressive, but they are not always the right tool. Sometimes reaching for a VM is like renting a moving truck to carry a single grocery bag. Here is when to choose something simpler.

A VM makes sense when you need a complete, separate computer - to run Windows programs, to tinker safely, or to do something a container simply cannot. For most everyday server jobs, the humble container wins on ease and efficiency.

• You just want to run one app, and it exists as a container already.
• You want the lightest, easiest option that sips resources.
• You do not actually need a full desktop or a whole operating system.

Real Use Cases

To make this concrete, here are the kinds of everyday jobs people genuinely use VMs for on a home server. Notice that each one needs a full computer, not just a single app.

• Run a Windows-only program - keep an old but essential piece of software alive on a tidy, separate Windows machine.
• Keep a smart-home hub running - some people run Home Assistant as a VM so it is always on.
• Have a safe sandbox - test software or open questionable files in a machine you can wipe and rebuild.
• Learn Linux - practice a new operating system with nothing important at risk.
• Run a small always-on task - a lightweight computer that stays up alongside the server.

Troubleshooting Basics / Call Bill

When a VM misbehaves, most problems trace back to a short list of usual suspects. Run through these before you worry, and know that help is a phone call away.

If you have checked these and a VM still fights you - or you are eyeing something advanced like passing through a graphics card - that is a fine time to bring in a hand rather than risk your server.

• VM will not start? - make sure virtualization is switched on in the BIOS, and that you have free memory.
• Blank or stuck screen? - give it a minute, then reopen the VNC window; the display sometimes just needs a refresh.
• Running slowly? - install the VirtIO helper drivers and consider faster storage.
• Out of resources? - a VM set too large starves the server; trim its cores or memory.

What's in the 27-page PDF

• What a virtual machine actually is, in plain words
• Why you might want one, and when a simpler option is better
• What your server needs before you can run one
• How to create, view, start, and stop a basic VM
• Snapshots, backups, and keeping your server healthy
• Real uses, performance tips, and where to get help

Why I wrote this

I write these as printable handouts because a guide you can keep in a drawer beats a web page you have to find again. No jargon, no judgment, no rushing. If you'd rather have someone sit beside you and go through it together, that's a flat $99 first visit with the 30-day follow-up included — serving Portage County from Atwater, Ohio. — Bill