virtualbox.org

Dear all,
today I could not open my Win7 64 bit (4 Gb) guest on MacOS 10.13.4 (8 Gb) host.
Virtual box 5.2.8 r121009 (Qt5.6.3)
The virtual machine is stuck in Guru meditation during win7 update.
Please, find attached the zipped log file.

Thanks for your help

VBox.log wrote:

00:00:02.418167 Host RAM: 8192MB (8.0GB) total, 4423MB (4.3GB) available
00:00:02.590577 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:02.591079 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)

You haven't quite run out of RAM (assuming my maths is any good) but you are getting very close to it. Windows 7 will probably be OK with either 2GB or 3GB RAM allocated to it which will give your host a bit more breathing space.

Your specific guru meditation (VINF_EM_TRIPLE_FAULT) is typically an indication that your guest OS has done something bad.

-Andy.

You: MBP11,1 with OSX 10.13.4
Me: MBP11,5 with OSX 10.11.6

Unless 10.13.4 plays a factor, we have really similarly configured VMs, so it's not easy to tell why you're getting a Guru, except two things:

00:00:02.976023 CPUM: Physical host cores: 2
00:00:02.590573 NumCPUs   <integer> = 0x0000000000000002 (2)
...
00:00:02.418167 Host RAM: 8192MB (8.0GB) total, 4423MB (4.3GB) available
00:00:02.590577 RamSize  <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:02.591079 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)

You are assigning CPUs and RAM to your guest, that are barely available. The host is going to run low on resources. I would suggest 1 CPU and 2048 MB of RAM. See if that improves the situation.

Edit: andyp73 beat me to the punch, but I'll keep mine as well for two reasons; you have two independent set of eyes, plus the CPUs. andyp73, it's a race!

Thank you for your prompt response.
I tried decreasing ram to 2Gb and CPU to 1 (this configuration has been working properly for months). The problem is still there. The update stops at 72% as before changing settings (see screenshot attached). Any further suggestion?
Is there a way to check the integrity of the vdi file?

During win7 launch (before freeze) I get an error saying "impossible to execute Autochk", see attached screenshot (italian). Could this be the problem? Any suggestion on how to fix it?

@Moradan
Could you please crop your image to the area that's important? We don't need to scroll all of the desktop to see something interesting. Just use the Preview.app to crop the image to the important stuff and replace the existing image. Thanks...

Now, I was about to suggest that something is going on inside the guest. Win7 is one of the most widely used guests, so I don't know what you have installed in that Win7 that makes it behave like that. As I said, we both have similar Macs, similar configuration, almost identical logs, except yours is going Guru! You have me stumped.

Can Win7 start in safe mode?

BTW, you are in front of the host, right? No remote desktop or anything like that, right? And no antivirus or anything like that, right? Can you post the output of this command from the Terminal:

• kextstat | grep -v com.apple

Thank you, Socratis. I'll stick to your suggestion about cropping.
Win7 does not start in safe mode, either: it takes a lot of time (minutes) to load all the .sys files in the windows\System32\drivers dir and then eventually halts (without any guru warning).
No remote desktop on the host.
Kaspersky Endpoint Security is installed on the host (but it has been there for a long time and never had problems).
Here is the requested output:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  141    0 0xffffff7f80ed8000 0x13000    0x13000    com.kaspersky.kext.kimul (46) A8797394-1582-3199-B848-57168A700E56 <5 4 3 1>
  142    0 0xffffff7f80dab000 0x1e000    0x1e000    com.kaspersky.kext.klif (3.5.2a8) C5C80763-4AD4-3655-8DD6-6DC659C92C83 <25 5 4 3 1>
  143    0 0xffffff7f80c4e000 0x5b000    0x5b000    com.kaspersky.nke (2.3.4a11) 946BD7DA-97CF-31BA-B5A5-D19B79C51342 <15 7 5 4 3 1>
  152    3 0xffffff7f837cb000 0x64000    0x64000    org.virtualbox.kext.VBoxDrv (5.2.8) E68480EC-6423-30BA-9728-D1B0B5D606FE <7 5 4 3 1>
  160    0 0xffffff7f8382f000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.8) 6D97A7F9-6650-3AF5-9477-144D758EB0F0 <159 152 52 7 5 4 3 1>
  162    0 0xffffff7f83839000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.8) 324CE487-51AE-38A0-AED2-8F8DED2CFD8F <152 7 5 4 3 1>
  163    0 0xffffff7f8383e000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.8) 85257673-062A-35FB-9221-8AB980E0CE5A <152 5 4 1>
  164    0 0xffffff7f80da8000 0x2000     0x2000     com.kaspersky.kext.mark.1.0.6 (1.0.6) 9E31771B-3AA7-3BC0-92CB-FE1EACCD6985 <4 1>

Thank you