VirtualBox

Opened 3 months ago

Closed 4 days ago

#22308 closed defect (fixed)

VBoxManage unregistervm --delete does not delete VRDEAutoGeneratedCert.pem and VRDEAutoGeneratedPrivateKey.pem

Reported by: amw Owned by:
Component: other Version: VirtualBox-7.1.4
Keywords: Cc: amw
Guest type: other Host type: Linux

Description

If I run VBoxManage unregistervm --delete at the command line VRDEAutoGeneratedCert.pem and VRDEAutoGeneratedPrivateKey.pem are left behind in the machine folder. The problem occurs on a machine running VirtualBox-7.1.4, but not on one using VirtualBox-7.0.18.

I use Vagrant to create VMs in a CI testing environment and this bug has broken the scripts. When recreating a VM, I get:

VBoxManage: error: Could not rename the directory '~/VirtualBox VMs/temp_clone_1738566076708_11622' to '~/VirtualBox VMs/vm_name' to save the settings file (VERR_ALREADY_EXISTS)

Change History (3)

comment:1 by pneumann, 2 months ago

This issue also affects Windows hosts, and it causes similar problems with CI scripts. The issue is still present in VirtualBox 7.1.6.

comment:2 by paulson, 5 weeks ago

Summary: VBoxManage unregistervm --delete doesn not delete VRDEAutoGeneratedCert.pem and VRDEAutoGeneratedPrivateKey.pemVBoxManage unregistervm --delete does not delete VRDEAutoGeneratedCert.pem and VRDEAutoGeneratedPrivateKey.pem

This issue has now been addressed and the fix is available in the Testbuilds today. The fix will also be part of the next maintenance release of 7.1.

comment:3 by paulson, 4 days ago

Resolution: fixed
Status: newclosed

This issue has been addressed in VirtualBox 7.1.8 which was recently released and is available here.

Note: See TracTickets for help on using tickets.

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette