VirtualBox

Ticket #822 (new defect)

Opened 6 years ago

Last modified 22 months ago

Error handling when shared folder is missing or broken => Improved with 1.6.6

Reported by: ronnystandtke Owned by:
Priority: major Component: VM control
Version: VirtualBox 1.6.4 Keywords:
Cc: Guest type: other
Host type: other

Description

Here is a scenario where the error handling of VirtualBox is broken: 1) add a shared folder to a virtual machine 2) remove the "real" directory while vbox is not running 3) restart VirtualBox

The user gets the following error message: "The snapshot folder of a machine with snapshots cannot be changed (please discard all snapshots first)."

First of all, the error message has absolutely nothing to do with the real problem (non-existance of a specified shared folder) and is very misleading.

Secondly, a missing folder is no fatal situation, it should be possible for a user to recover from this situation without manually editing some obscure XML files.

Change History

comment:1 Changed 6 years ago by frank

At least the current version 1.5.4 shows in that case 'VM not accessible' because 'the shared folder host path ... is not accessible'. This is still not what you want (the VM should start anyway perhaps after warning the user) but a little bit better than the original behavior.

We will improve the behavior in later versions.

comment:2 Changed 6 years ago by frank

  • Component changed from other to VM control

comment:3 Changed 6 years ago by sandervl73

  • Version changed from VirtualBox 1.5.0 to VirtualBox 1.6.2

comment:4 Changed 6 years ago by frank

  • Version changed from VirtualBox 1.6.2 to VirtualBox 1.6.4
  • Summary changed from Error handling when shared folder is missing is broken to Error handling when shared folder is missing or broken

comment:5 Changed 6 years ago by kookyman

Just ran into this bug tonight.

When this situation occurs, not only does the virtual machine become unable to start, it becomes completely locked out from the VB Control panel.

This creates an impossibility to correct the issue. To correct the issue tonight, I had to rebuild the directory tree so that the directory once again existed, then immediately deleted the shared folder setting from the VBox Control panel. (The main GUI that starts on execution in Windows.)

In the event of a fatal error, of any kind in addition to this specific one, you should always have access to the settings of the virtual machine to remove or correct the flaw. The sole exception to this would be in the event that the VM configuration files themselves are unavailable, in which it shouldn't display in VBox in the first place.

comment:6 Changed 6 years ago by frank

  • Summary changed from Error handling when shared folder is missing or broken to Error handling when shared folder is missing or broken => Improved with 1.6.6

In VBox-1.6.6 we weakened this condition a bit. If a shared folder vanishes, the VM will no longer became inaccessible. Currently, no warning is displayed, the folder is just not accessible. This condition should be handled well by all guest additions. In future versions we have to fix this in a way that at least a runtime warning is displayed.

comment:7 Changed 6 years ago by maletin

Does a documentation exist, how to recover from this problem (especially if some files are lost forever)?

comment:8 Changed 6 years ago by frank

Lost files in the shared folder? That does not matter, the guest will get an error message when trying to access such files. If a whole shared directory is lost then you have to create a dummy directory with the same name to satisfy current versions of VirtualBox and to be able to start the VM. Starting from 1.6.6, the guest will receive an error message in this case. This is currently not documented as we have to improve this handling further.

comment:9 Changed 22 months ago by adji

It is still broken in 4.1.8

Version 0, edited 22 months ago by adji (next)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use