Do not hijack other threads, create your own. Choose the title carefully.

Discussions related to using VirtualBox on Windows hosts.

Do not hijack other threads, create your own. Choose the title carefully.

Postby socratis » 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:

    Image
Otherwise you're running the danger of your question being lost in the noise, ignored.

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.
Image
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 23780
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Alex 777, Baidu [Spider] and 38 guests