Opened 13 years ago
Closed 8 years ago
#9962 closed defect (obsolete)
Crash when shared folder does not exist on startup
| Reported by: | Wand | Owned by: | |
|---|---|---|---|
| Component: | shared folders | Version: | VirtualBox 4.1.6 |
| Keywords: | crash shared folder missing startup autostart | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description (last modified by )
Host: Win7-SP1-x64 Guest: WinXP-SP3-x32
Guest is set to autologin on startup via TweakUI. Two shared folders have been defined (O:, Z:), located on an external USB disk. These folders have also been "re-shared" because different drive letters than the default set by VBox are required. During startup, if the HDD is not connected, some information messages appear, warning the user that the shared folder does not exist. If OK is not pressed before the guest auto-logs-in, the guest window closes without any warning.
I don't know if if matters, VBox is set on Seamless mode.
Attachments (1)
Change History (3)
by , 13 years ago
comment:1 by , 13 years ago
comment:2 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Note:
See TracTickets
for help on using tickets.
OK, this issue also exists in 4.1.8 and the cause is slightly different that what i had understood. It seems it doesn't have to do with virtual folders. The problem occurs if ANY VBox informational message window (like "A new version of VirtualBox is available") is open during the startup and autologin guest process. In that case, VBox crashes. My guess is that if the guest is set to autologin and the VBox Guest Additions service tries to start inside the guest while a VBox informational message window is visible in the host, something goes the wrong way. Also, maybe the priority of this one should not be "minor" because it's a crash and we can't be certain if the virtual machine gets corrupted due to that crash.