virtualbox.org

Hello everyone,

On a Mac (OS X10.14.6) with VM (Windows 10), there are errors when closing VM.
The VM also poses a lot of problems with the mouse and some characters like hooks "[ ]"

Would you have a little idea ? Thanks for your help.

Error' s message in attached file

Jmd.

You posted a crash log. Do you see the VM process go down really hard with a crash when you're closing a VM? How do you close that VM, from the "x" widget on the top-left? From within the guest?

We need to see 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 or recreate the 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. ZIPPING It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...

Hello,

Please find in attached document the log file. We cannot add memory video over 256ko. Perhaps also a problem ??

Thanks for your help

Very best

Jmd

Please read my signature and try again...

If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

You wouldn't do that to your doctor when submitting your blood results to help them diagnose what's wrong with you, would you?

Plus, I asked you some questions, didn't get an answer. Here's how the whole thing works:

1. You come here for help.
2. We ask for specific evidence to help us figure out (remotely and blindfolded) what's wrong with your setup.
3. You provide the information asked. Answers to our questions, and unfiltered complete logs.
4. We then try our hardest to figure out (hopefully), what's wrong with your setup. Remotely and blindfolded. If you're adding more hurdles on top of that, we're not going to go very far...

Jmd wrote:We cannot add memory video over 256ko. Perhaps also a problem ??

No, that's the VRAM limit for your virtual GPU, there's no point to having more than that.

Hello,
Thank you for your reply.
I had no intention of not satisfying your request properly to help him.

• I launched the VM
• I stopped it and looked for the VBox.log file in the "Journal".
• I zipped this file and posted it to the forum.

I will try again to repeat the same operation.

I'm sorry.
Very best

Jmd

I forgot to tell you that the problem encountered by launching the software under windows on which we work together, sometimes blocks the VM and also blocks the MAC (bought in 2019 with a graphics card with a definition of more than 4000 pixels on the width). The only possible way is to stop the MAC and there is no VBox.log created. The mouse and the keyboard are also going crazy.

If you start the VM and close Windows without running a program, you get the error message of the MAC crash.

This could look like overflow memory.

The Windows software worked very well with its old MAC and the VM that was installed there. Virtual Box does not seem to manage an element of this new computer.

Very Best

Jmd

Hello,

Using the right mouse button and clicking "Journal", I got the same type of .Log file I sent the first time.

I did some testing by setting the video card to 640 X 480 with 8 bit colors and there were no errors but it is therefore impossible to use the software under such conditions.

As I thought, and unless I'm mistaken, The VM can not manage the video card of this new MAC with a definition of 4096 pixels in width.

Very best

Jmd

Jmd wrote:and clicking "Journal"

Where are you clicking that says "Journal"? I gave you very specific instructions, please follow them.

Jmd wrote:I got the same type of .Log file I sent the first time.

So, you mean to tell me that this below is the name of your VDI? Are you trying to actually tell me that you did not modify the log? Seriously now?

'/Users/c................../VirtualBox VMs/c......... g........ 3/s10.vdi'

Please try again. This time I want the log "as is". No modifications, no replacements, no changes.

@Jmd, see https://security.stackexchange.com/ques ... bad/216319
You will not get hacked only from showing your PC user name. You're being hacked already. You stand even less chance of being hacked from revealing your guest's Virtualbox name.

As Socratis says, Security is good, paranoia, not so much.

scottgus1 wrote:You will not get hacked only from showing your PC user name.

I've been thinking about that, and there might be people out there that would be afraid to pay with a credit card, because the employee of a gas-station/tavern/pub/bar/coffee-shop/super-market/grocery-store/hardware-store/<NameIt> would have their credit card number!

In reality, no one is afraid to pay with a credit card, i.e. give the equivalent of their "username", the public key. It's the PIN (the private key) that is securing the whole thing. That's the equivalent of the "password", and mind you, that PIN is only 4-digits long! Yet no one is afraid.

I honestly don't know where that mentality of hiding/obfuscating one's username came from, but I have a feeling that it's from those scareware security companies and their click-bait informative articles...

Hello,

It's not my computer. It's the friend's computer. He prefers like that. Its's only his problem and I respect his decision.

I don't think it's a problem to try to help us. All the other parameters are in the file log.

We will try with "Parallels" and see if we encounter the same problems. Sorry, we must quickly find a reliable solution.

Very best

Jmd

Jmd wrote:It's not my computer. It's the friend's computer. He prefers like that.

OK, you have to abide by your friend's wish. Give him a little laugh, rap him on the shoulder, tell him his tin-foil hat is a bit too snug then try Parallels.

If you can't get things going, come back, we'll try to help.

Please note that the Virtualbox video card is virtual, not the Mac's physical video card. The Virtualbox video card's capabilities are said to be circa 1995, way before 4000-pixel-wide displays were around. You may need to drop back to 1920x1080 max with the max 256MB Vram when 3D acceleration is on, and use the Scaling function to zoom the guest screen up. If you can get by without 3D acceleration you'll be limited to 128MB max memory but some glitches that the devs are working on may go away.