Failed to create a snapshot of the virtual machine: Win Server 2019 guest

[charlweed]

I cannot snapshot any Win Server 2019 guest.

I can snapshot a guest before the OS is installed, but after, it refuses to snapshot.
Guests are stopped when I attempt. I have created multiple guests to attempt snapshoting, all fail.
Dispite the error, the NVRAM file is copied to the destination directory, but vbox fails anyway.
I have checked permissions and selinux.
I have tried temporarily changing the value for the "Guest OS" selector, and the "Graphics Controller"

Version VirtualBox 6.1.10
Host CentOS linux kernel 3.10.0-1127.13.1.el7.x86_64

Code: Select all

Failed to create a snapshot of the virtual machine melbourne.

Could not copy NVRAM file '/home/vmadmin/VirtualBox_VMs/melbourne/melbourne.nvram' to '/home/vmadmin/vbox_vms/melbourne/snapshots/2020-06-26T20-32-43-296493000Z.nvram' (VERR_NOT_SUPPORTED).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: SessionMachine
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

[fth0]

Config file:                 /home/vmadmin/VirtualBox_VMs/melbourne/melbourne.vbox
Snapshot folder:             /home/vmadmin/vbox_vms/melbourne/snapshots
Log folder:                  /home/vmadmin/VirtualBox_VMs/melbourne/Logs

00:00:01.044075 File system of '/home/vmadmin/vbox_vms/melbourne/snapshots' (snapshots) is xfs
00:00:01.044100 File system of '/home/vmadmin/VirtualBox_VMs/melbourne/melbourne_00.vdi' is xfs

I could imagine that VirtualBox doesn't handle the different path for the snapshot directory correctly (maybe in combination with xfs). Why is the path different?

[charlweed]

The problem occurred before I created the vbox_vms directory. I make that destination directory to test if there was a problem writing to the VirtualBox_VMs directory. I did not want to change any of the attributes or permissions of any directories that vbox created, so I made a new directory where I explicitly set the permissions and selinux labels.
It made no difference.

[fth0]

Then you had better changed it back and provided log files of your original problem, instead of leading us on a wrong track (just a suggestion for the next time, no hard feelings from me).

The error message, which you got, really means what it sounds like. VirtualBox detected something that it doesn't support while trying to copy the file. Two questions:

Is the source .nvram file larger than 4 GB?

Can you reproduce the error and post the VBoxSVC.log file?