VirtualBox

Opened 5 years ago

Closed 5 years ago

#18423 closed defect (fixed)

Shared folders unavailable after guest restore from saved state

Reported by: waldner Owned by:
Component: other Version: VirtualBox 6.0.4
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

This happens mostly with a windows 8.1 guest (host is archlinux, virtualbox 6.0.4 r128164, same version of guest utilities on the guest). When booting the guest from powered down, shared folders are accessible. I usually save the guest state, then shut down the host. When the host is started again and the guest restored from the saved state, shared folders are no longer accessibile. Shutting down the guest and booting it again makes the shared folders available again.

Change History (5)

comment:1 by Socratis, 5 years ago

Possibly a duplicate of #18151, #18220, #18373, #18437.

comment:2 by Reiner Brodbeck, 5 years ago

I don't think it is a duplicate of these tickets:

#18220 is related to v6.0.0 and I experienced exactly the same behaviour with that version, but now in v6.0.4 automount is okay, as long as there is no process on the guest, that writes to the mount point at an early stage after restore.

#18151, #18373, #18437 are related to Windows guests. there behaviour is different. I added logs to #18373 concerning problems I saw.

comment:3 by waldner, 5 years ago

Most definitely #18220 and #18373, reading through it I realize that I have the same symptoms (including randomly duplicated shared folders). I'll subscribe to that one, you can close this.

in reply to:  3 comment:4 by Reiner Brodbeck, 5 years ago

Replying to waldner:

Most definitely #18220 and #18373, reading through it I realize that I have the same symptoms (including randomly duplicated shared folders). I'll subscribe to that one, you can close this.

I no longer have duplicated shared folders in the Linux guest using v6.0.4. In my guest it's only the symptom described above.

comment:5 by bird, 5 years ago

Resolution: fixed
Status: newclosed

This should've been fixed in 6.0.8 or 6.0.6. Closing it, but if it is still an issue, just reopen, attach a VBox.log and describe how to reproduce.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use