TerraMaster Forum

Thanks for your update.

We have confirmed that this issue does exist. It is a known defect in the old version's installation/uninstallation script. When the application is uninstalled from Volume2 and reinstalled to Volume1, the old script fails to completely clean up the virtlogd.service symbolic link in the /usr/lib/systemd/system/ directory, resulting in a broken link pointing to the deleted old path. This causes systemd to be unable to find the service, leading to virtual machine startup failure.

This issue will be fixed in the upcoming latest version. The new installation/uninstallation script will improve the logic for cleaning up and recreating symbolic links. Please wait patiently for the update.

The fact that you previously restored normal service by "uninstalling and reinstalling the application" indirectly avoided the impact of the old link (as reinstalling recreated the correct link). If you encounter similar issues in the future or need to install to a different Volume path, simply updating to the latest version will resolve the problem.

Thank you again for your patience and cooperation!

No problem.

TMzethar wrote: ↑05 Apr 2026, 11:07 Hi,
VMs is a newly launched app, and we will continue to optimize and maintain it.
Could you please send a screenshot of the screen where you encountered the error here? If possible, please also describe the specific steps you took. This will help us pinpoint the issue.

I did want to pass on that once I got it running again. It's works pretty well.
Note for RHEL folks, when creating a VM, you must change the video selection from vmvga to just vga, otherwise the initial run, the boot up process just stops. But building Ubuntu VMs, that isn't necessary. Go figure.
I tired RHEL versions, 8.5, 9.3 and 10.1
I also switch to a putty session once the VM is built as the console mode sucks (technical term) as it does all other Virtual managers as well.

Export feature does not work. I mean I select the VM and click/select Export, a message comes up saying successful, but nothing is written to the folder selected.

rfbjr wrote: ↑11 Apr 2026, 23:14 Export feature does not work. I mean I select the VM and click/select Export, a message comes up saying successful, but nothing is written to the folder selected.

We will look into the situation you mentioned. If you find out anything else, please let us know.

We have found that this issue occurs when the destination directory does not have sufficient space.
Please verify that the destination directory is located on a volume with sufficient free space.

I just double checked and the volume (Volume2) has 35TB free, I also checked the permissions of the Export folder I use, it's wide open.
I'll try turning on Debug mode and try the export again and post the link to the logs.
https://1drv.ms/f/s!AgP4K-RskQ9MjLwJvJG ... Q?e=2GWq4N

rfbjr wrote: ↑12 Apr 2026, 18:53 I just double checked and the volume (Volume2) has 35TB free, I also checked the permissions of the Export folder I use, it's wide open.
I'll try turning on Debug mode and try the export again and post the link to the logs.
https://1drv.ms/f/s!AgP4K-RskQ9MjLwJvJG ... Q?e=2GWq4N

Unless the system freezes, runs slowly, or becomes unresponsive, you do not need to use Debug mode.
Please collect a system report when the issue occurs during runtime.
(Support and Help > Report Issues)

Ok good to know about debug mode. I’ll try it again and generate the system report instead.

Update: System report generated and uploaded to the share

rfbjr wrote: ↑13 Apr 2026, 09:28 Ok good to know about debug mode. I’ll try it again and generate the system report instead.
Update: System report generated and uploaded to the share

Unfortunately, we couldn't find any relevant information there.
Please check whether the @tmp folder on the volume where the virtual machine is located still exists.
/Volume?/@tmp