NAS Codex › QNAP › QNAP Virtualization Station VM won't start, won't resume, or shows a black console
QNAP Virtualization Station VM won't start, won't resume, or shows a black console
QNAP has separate articles for three Virtualization Station problems: a black screen in the VM console after the Virtualization Station 4.0.0.278 update, VMs that won't resume after upgrading to QTS 5.0.0 on TS-x73 models, and VMs that run short of system memory. This page puts their fixes together.
Written against: Virtualization Station on QTS (QNAP FAQs last modified 2025-06-10 and 2022-06-24; QNAP tutorial last modified 2020-07-01). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Black console: update QTS to 5.2.4 or later in Control Panel > System > Firmware Update, restart the NAS, and open the console again. VM won't resume after QTS 5.0.0 (TS-x73): force shut down the VM and change its CPU Model away from AMD Opteron 63xx. Not enough memory: use Virtualization Station's Memory Optimizer and stagger VM auto start.
1. The VM console shows a black screen
QNAP says you may see a black screen when opening the VM console in the web interface. The cause is a compatibility problem between Virtualization Station 4.0.0.278 and QTS 5.2.3 or earlier: those firmware versions lack updates needed for stable display rendering. QNAP's fix:
- Go to Control Panel > System > Firmware Update.
- Click Check for Update, or manually upload the latest firmware file, to reach QTS 5.2.4 or later.
- Restart the NAS after the upgrade.
- Open Virtualization Station and open the VM console again.
2. VMs won't resume after upgrading to QTS 5.0.0
For Virtualization Station on TS-x73, TVS-x73 and TS-x73U models, QNAP says this comes from a compatibility issue between QTS 5.0.0 and VMs that use the AMD Opteron 63xx (Gen 5 Class Opteron) CPU model. The fix is to force shut down the VM and choose a different CPU model:
- Go to the VM information screen and choose Force Shutdown.
- Go to Settings > General.
- Under CPU Model, select another option.
- Go to the Information tab and restart the VM.
3. Not enough memory for your VMs
QNAP says a lack of system memory affects both the NAS and VM performance, and offers a Memory Optimizer that combines memory sharing and dynamic memory allocation. Its tutorial walks through these settings.
Memory overcommitment and the Memory Optimizer
- In Virtualization Station, go to Preferences > Memory and select Memory Overcommitment. QNAP's example sets Overcommitted Ratio to 50%.
- Select Enable Memory Optimizer and Automatic Optimization Adjustments, which QNAP says are usually recommended. Customized Adjustments let you set your own scanning threshold and interval.
- Click Apply.
Memory sharing and dynamic memory allocation (each VM)
- Shut down the VM and go to VM Settings > General.
- Select Enable Memory Sharing and Enable Dynamic Memory Allocation.
- Set Reserved Memory, which is always allocated to the VM. QNAP says the combined reserved memory of all VMs shouldn't exceed the usable system memory, and setting it below the operating system's minimum may hurt performance.
- Set Shares (Low, Normal, High or Custom). VMs with a higher value get more memory when the system has free memory, and give up a larger share when memory runs low.
Balloon driver for Windows VMs
QNAP says modern Linux VMs include the balloon driver by default; Windows VMs need it. Stop the VM, go to VM Information, choose Insert Guest Tools CD, start the VM, open the console, and install qnap-guest-tools from the CD drive.
Stagger auto start
QNAP says delaying auto start may help reduce insufficient-memory problems when VMs start. Because Windows VMs use all their allocated memory when starting, QNAP recommends starting them first. For each VM, go to VM Settings > Others, set Auto Start to Delay, and set a start delay; QNAP's example uses 0, 60, 120 and 180 seconds for four VMs.
When to stop and get help
QNAP's CPU-model fix starts with a Force Shutdown of the VM. Its memory tutorial warns that setting a VM's Reserved Memory below its operating system's minimum may impact performance.
Questions
Why is my QNAP Virtualization Station VM console black?
QNAP says Virtualization Station 4.0.0.278 has a compatibility problem with QTS 5.2.3 or earlier. Update QTS to 5.2.4 or later, restart the NAS, and open the console again.
Why won't my VMs resume after upgrading to QTS 5.0.0?
On TS-x73, TVS-x73 and TS-x73U, QNAP says VMs using the AMD Opteron 63xx CPU model are affected. Force shut down the VM and pick another CPU Model.
How do I fix not enough memory for VMs in Virtualization Station?
QNAP's tutorial uses Memory Overcommitment with the Memory Optimizer, memory sharing and dynamic allocation per VM, the balloon driver for Windows, and staggered auto start.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.