Hello,
i want to take a snapshot from Windows11 VM.
This is canceled with the following message:
vboxmanage snapshot Windows11 take "Sicherungspunkt 1"
0%...10%...20%...30%...VBOX_E_IPRT_ERROR
VBoxManage: error: Failed to take snapshot
VBoxManage: error: Could not copy NVRAM file '/home/user1/.Virtualbox/Windows11/Windows11.nvram' to '/home/user1/.Virtualbox/Windows11/Snapshots/2023-11-25T09-20-07-406971000Z.nvram' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component SessionMachine, interface IMachine
VBoxManage: error: Context: "RTEXITCODE handleSnapshot(HandlerArg*)" at line 495 of file VBoxManageSnapshot.cpp
This reproducible with every Windows VM that have EFI/Secureboot enabled.
tested OS:
Windows 10
Windows 11
Windows Server 2022
debian 12, not possible to install with EFI/Secureboot and TPM.
openSUSE 15.4
Host is Centos7, filesystems are local with ext4, /home/user1/.Virtualbox points to a second harddrive.
Virtualbox is 7.0.12
Hardware is older Shuttle with no TPM, no EFI
Export is working.
I asumed TPM, EFI and Secureboot is emulated. It seems it is not. Only TPM
Are there any solutions?
Best regards.
no snapshot with EFI/Secureboot possible
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: no snapshot with EFI/Secureboot possible
I don't know about diagnosing this problem, but for those that might, does this problem happen when:
- the VMs are running?
- the VMs are save-stated?
- the VMs are fully shut down?'
- the VMs are running?
- the VMs are save-stated?
- the VMs are fully shut down?'
-
fth0
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: no snapshot with EFI/Secureboot possible
In addition to what scottgus1 wrote:
Taking snapshots of Windows 11 VMs with (U)EFI BIOS and Secure Boot works for me. I'd suggest to take a closer look at the filesystem operations:
I've successfully analyzed a similar case in viewtopic.php?f=3&t=100830. After copying the NVRAM file contents, VirtualBox tries to copy the file access rights and the file access and modification times, and a failure to do that also results in the error message you're seeing.
Open a Linux terminal and try investigating with chown, touch and strace. Tell us if you need further assistance with that, and what you discover. I'm curious.
Taking snapshots of Windows 11 VMs with (U)EFI BIOS and Secure Boot works for me. I'd suggest to take a closer look at the filesystem operations:
I've successfully analyzed a similar case in viewtopic.php?f=3&t=100830. After copying the NVRAM file contents, VirtualBox tries to copy the file access rights and the file access and modification times, and a failure to do that also results in the error message you're seeing.
Open a Linux terminal and try investigating with chown, touch and strace. Tell us if you need further assistance with that, and what you discover. I'm curious.