VirtualBox

5 年 前 建立

5 年 前 結束

#19160 closed defect (fixed)

VirtualBox 6.1 cannot use old VMs with disc encryption => fixed in 6.1.2

回報者: torafu 負責人:
元件: virtual disk 版本: VirtualBox 6.1.0
關鍵字: encryption 副本:
Guest type: Linux Host type: Windows

描述

I have used disc encryption with my VMs (Windows host, Linux guests), latest ones created with 6.0.14, and some older. When I upgraded to VirtualBox 6.1 (including extension pack), booted the host machine(just to be safe), and tried to run the old VMs they did not anymore ask for disc encryption password, but instead the VM just tried to boot and failed with "No bootable medium found".

Luckily uninstalling 6.1 and installing 6.0.14 (and it's extension pack) worked, and I can again run my VMs.

更動歷史 (4)

comment:1 5 年 前bladesong 編輯

I'll add to this as I have hit this particular issue also. Host Machine : Windows 10

Previously running 6.0.14 using a VM image encrypted via VirtualBox with no issues. Installed 6.1 over the top and now if I try to run the image I get the "No bootable medium found" error. My other image is not encrypted and it runs fine.

Steps taken (all via the VirtualBox GUI):

  • Unecrypted the VM image using v6.1, the image now runs correctly.
  • Encypted the image with v6.1, the image fails to run, with the "No bootable medium found" error occuring.
  • Unecrypt the image again, the image runs correctly again.

If there is anything else you want to to try let me know.

comment:2 5 年 前bladesong 編輯

To add further to this.

I just loaded up a different image I had that was encrypted via 6.0.12. It works as expected. VirtualBox 6.1 asked me for the encryption password and the image loaded up correctly.

The image that still doesn't work if it is encrypted (see previous comment) is a debian based OS image, perhaps that makes a difference?

comment:3 5 年 前geov 編輯

Also sometimes it works until first snapshot.

comment:4 5 年 前aeichner 編輯

摘要: VirtualBox 6.1 cannot use old VMs with disc encryptionVirtualBox 6.1 cannot use old VMs with disc encryption => fixed in 6.1.2
狀態: newclosed
處理結果: fixed

This should be fixed with 6.1.2. The issue would appear as soon as there was a snapshot involved. Please try with 6.1.2 and reopen if this is still an issue and attach at least a VBox.log of the affected VM.

注意: 瀏覽 TracTickets 來幫助您使用待辦事項功能

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