VirtualBox

Ticket #13942 (new defect)

Opened 4 years ago

Last modified 4 years ago

Failed to start the virtual machine when seemingly unreachable

Reported by: and_kors Owned by:
Component: other Version: VirtualBox 4.3.24
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by frank) (diff)

I as a system connected to the virtual media used images located on a network drive. In the case where the network drive is not available, the virtual system can not start.

It would be better to just give a message about the unavailability of the resource, not to block the program.

Attachments

Pic1.png Download (40.9 KB) - added by and_kors 4 years ago.
Error message
Pic2.png Download (193.6 KB) - added by and_kors 4 years ago.
VBoxSVC.log Download (6.1 KB) - added by and_kors 4 years ago.
VBox.log Download (35.5 KB) - added by and_kors 4 years ago.

Change History

Changed 4 years ago by and_kors

Error message

comment:1 Changed 4 years ago by frank

  • Description modified (diff)

I cannot reproduce this problem. If I remove an ISO image and start the VM, I get a runtime warning which can be disabled.

Please attach a VBox.log file of such a VM session when you try to start the VM but the VM wouldn't start because the ISO medium is not available / accessible. Please attach also the corresponding VBoxSVC.log file.

Changed 4 years ago by and_kors

comment:2 Changed 4 years ago by and_kors

The problem is reproduced as follows:

  1. Create CD media in the virtual machine configuration
  2. connect to it a disk image (* .iso in my example), located on a network share (network share drive on another computer)
  3. Verifies that he normally mounted virtual machine startup
  4. unplug the network cord from your computer and run virtual machines.

Changed 4 years ago by and_kors

Changed 4 years ago by and_kors

comment:3 Changed 4 years ago by and_kors

We need to do a network resource unavailable (I discovered the problem when temporarily took away home office computer and the connected resources remain in office network)

comment:4 Changed 4 years ago by frank

The code already contains a check for inaccessible CDROM images. The point is that this check is called once when the VM process is being created. So if the CDROM image is not accessible at this point, the VM will start with the CDROM image detached. However, once the VM is started or, to be more precise, once we passed the initial check, the image must be present, otherwise it can happen that the guest touches into stale data.

Actually when the VM refused to start the first time not being able to access the CDROM image, it should be able to start when you try once again because then the VM process should detect that the image is not accessible and unmount it.

comment:5 Changed 4 years ago by and_kors

No. I ran 4 times again and again the virtual machine and she betrayed me the same error as I prepared for you a picture to the previous message.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use