Opened 9 years ago
Closed 8 years ago
#14549 closed defect (obsolete)
Guru meditation when reading CD
Reported by: | Janus Troelsen | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 5.0.2 |
Keywords: | cd | Cc: | |
Guest type: | other | Host type: | Linux |
Description
VDI: http://lazybrowndog.net/freedos/virtualbox/FreeDOS_1.1beta-network.zip
Using the VDI from above and the default DOS VM config, I get a Guru Meditation when listing the contents of a CD-ROM in DOS. I believe it is independent of the ISO, but I can provide the image if necessary.
When booting, be sure to choose the second option with CD-ROM support.
Attachments (3)
Change History (9)
by , 9 years ago
Attachment: | 2015-09-06-13-02-17.077-VirtualBox-11393.log added |
---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Thanks for the log. I adapted a few VM settings to be closer to your VM configuration but unfortunately I'm still not able to reproduce this problem.
by , 9 years ago
Attachment: | crashingimage.iso.xz added |
---|
unxz'ing and then "d:" and then "dir" with this image in the virtual cd-drive causes guru meditation (CAUTION: executing "dir d:" works)
comment:3 by , 9 years ago
Thanks for the quick reply frank. I tested with another ISO image, and it did not crash. I produced an ISO image that causes the crash (when executing "dir"). The crash does not happen with QEMU. I think it may be a problem between FreeDOS 1.1 and VirtualBox, as the crash happens when executing "dir".
comment:4 by , 9 years ago
If there is anything else that I can do to help you reproduce the problem, I would very much like to help you. I may be able to prepare a Docker image that contains a VirtualBox build, config, VM and all necessary files. Please tell me if this would be helpful to you.
comment:5 by , 9 years ago
With the latest 5.0.x build the guest just hangs (no Guru Meditation). Are you sure this setup works on real hardware?
comment:6 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Cannot reproduce. Please attach the VBox.log release log file which you can found in the VM machines directory.