virtualbox.org

sometimes my windows 8.1 freezes or resets and it tells me that i should look in the logs

how can i send this data to the virtualbox team so they can keep it in their records and see if they can fix it or look in it, so they can improve virtualbox from crashes information

i want to help them whenever sometimes bad happens to my virtualbox, this in the end will help and improve virtualbox,

but i don't know how i can do my part,

is there somewhere i can send this data to? it happens often on my windows 8.1 guest., not sure why

i am using a linux host and vb 6.0.10

Right-click the guest in the main Virtualbox window and click Show Log. Save Vbox.log, and if the error message mentions a hardening problem, save the Vboxhardening.log too. Put these files in a zip container (zip, rar, etc) and use the forum's Upload Attachment tab to post the zip container.

my windows 10 virtual machine keeps freezing, shutting down on its own, and it often crashes firefox, it also causes the other vm's to crash,


here is my log

00:00:03.168621 VMSVGA3dEnabled <integer> = 0x0000000000000001 (1)
00:00:03.168622 VMSVGAEnabled <integer> = 0x0000000000000001 (1)

According to the manual, VMSVGA is for Linux guests, and VboxSVGA is for Windows guests. Try switching.

00:00:03.168179 NumCPUs <integer> = 0x0000000000000006 (6)
..........
00:00:03.415000 CPUM: Physical host cores: 6

You have the entire host CPU in the guest. Reduce guest cores to 2.

i changed it to VBoxSVGA and i changed it to 4 cores

but it's been 2 hours and the vm crashed by itself

here is the new log

vm_guy wrote:i changed it to VBoxSVGA

Nah, you didn't... Because it was always set to VBoxSVGA.

The strings that 'scottgus1' quoted as evidence for the VMSVGA choice, are part of the "new" vGPUs. For those that are reading the logs, the following lines show up in the "[/Devices/vga/0/Config/]" section (minus the timestamp):

VMSVGA3dEnabled  <integer> = 0x0000000000000001 (1)    <-- VMSVGA and VBoxSVGA
VMSVGAEnabled    <integer> = 0x0000000000000001 (1)    <-- VMSVGA and VBoxSVGA
VMSVGAPciId      <integer> = 0x0000000000000001 (1)    <-- VMSVGA only

So, only if you see the "VMSVGAPciId" the VM is using the VMSVGA. If not, then the VBoxSVGA is in use. If you see none of the above lines, then the older VBoxVGA is used. Yes, it is confusing.

00:00:02.572659   MonitorCount     <integer> = 0x0000000000000002 (2)

Any particular need for 2 monitors? Can you lower it to 1, from the VM Settings » Display » Screen » Monitor Count.

00:00:02.635398 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 1 work area is actually resized to: 5285x1056 x 1680x1017
00:00:02.644472 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 2 work area is actually resized to: 1920x1056 x 1680x1017
00:00:02.656166 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 3 work area is actually resized to: 0x6 x 1920x1047
00:00:02.671752 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 4 work area is actually resized to: 6960x6 x 1680x1050
00:00:02.677326 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 5 work area is actually resized to: 3600x0 x 1680x1050
00:00:02.682145 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 6 work area is actually resized to: 1920x6 x 1680x1050
00:00:02.686760 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:
                Screen 7 work area is actually resized to: 5280x6 x 1680x1050

Do you actually have 7 (SEVEN) monitors?

socratis wrote:only if you see the "VMSVGAPciId" the VM is using the VMSVGA. If not, then the VBoxSVGA is in use. If you see none of the above lines, then the older VBoxVGA is used. Yes, it is confusing.

Sho' nuff! I just compared some of my guests. That is confusing. But I see the pattern. Thanks!

Now want to talk about something confusing? Let's go into that hardening log...

where exactly is the hardening.log

I looked inside the vm's win10 folder but there is no hardening log

is it inside the installatiom folder of virtualbox? I am using a Linux host

vm_guy wrote: I am using a Linux host

And that's exactly why you don't have a VBoxHardening.log, it's a Windows hosts only concept.

Sorry, that reference to the hardening log was to Socratis.
FWIW the second log you posted above for the 2-hour run then crash, is only 26 seconds long. Did you restart the guest after the crash? If so, after a crash, please zip and post both the Vbox.log and the Vbox.log.1.

It's happening to my windows 7 as well,

here is the log when it froze and shut off, and also here is the log after i turned it on again just like you asked