Do not hijack other threads, create your own. Choose your title carefully.
Posted: 27. Feb 2019, 10:16
Please do not hijack unrelated threads, just because it's easy to hit the "Reply" button.
It's equally easy to hit the "NewTopic" one:
You should think twice about where you post, and the title of your thread as well. "VirtualBox problem" doesn't convey your problem well enough to attract knowledgeable readers.
And when you do, please provide a complete VBox.log, from a complete VM run, where the problem occurs:
It's equally easy to hit the "NewTopic" one:
You should think twice about where you post, and the title of your thread as well. "VirtualBox problem" doesn't convey your problem well enough to attract knowledgeable readers.
And when you do, please provide a complete VBox.log, from a complete VM run, where the problem occurs:
- Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.