VirtualBox

Ticket #11157 (new defect)

Opened 18 months ago

Last modified 18 months ago

Page fusion cause Guru Meditation on Windows 7 x64

Reported by: noteirak Owned by:
Priority: major Component: other
Version: VirtualBox 4.2.4 Keywords: page fusion guru windows
Cc: Guest type: Windows
Host type: Linux

Description

When creating at least two VMs with Windows 7/2008 x64 and having them running at some point together, they always end up in Guru Meditation after doing random things (logoff the user, lanch applications, crash others). There is obviously some memory sharing/corruption issues.

The guests have the 4.2.4 additions installed and I can reproduce this crash at will on a Windows 7 x64 and Linux Debian based x64 aswell.

I have tried with and without large pages on. This bug was already in previous versions (at least from 4.1.x).

I will post a minidump & coredump ASAP.

Attachments

VBox.log Download (351.2 KB) - added by noteirak 18 months ago.
log of the Guru'ed VM
VBox.2.log Download (95.7 KB) - added by noteirak 18 months ago.
Log of the other running VM
VM01.zip Download (45.1 KB) - added by noteirak 18 months ago.
VM02.zip Download (441.4 KB) - added by noteirak 18 months ago.
pagefusion-crash02.zip Download (57.6 KB) - added by noteirak 18 months ago.
More crashin' & burnin'

Change History

Changed 18 months ago by noteirak

log of the Guru'ed VM

Changed 18 months ago by noteirak

Log of the other running VM

comment:1 in reply to: ↑ description Changed 18 months ago by noteirak

To make it clear : this bug happens on linux & windows x64 hosts with a windows 7 & 2008 x64 guests.

comment:2 Changed 18 months ago by noteirak

Some update on this :
I cannot recreate this bug under Ubuntu 12.10 with Gnome3.
I cannot recreate this bug under Debian Wheezy with testing packages.

I can recreate the behaviour (but not a guru meditation) under Windows 7 64 bits SP1 host with two Windows 7 64 bits SP1 guests.

What I did in order :

  • Created 2 VMs
  • Changed RAM to 1024Mb and gave more than one core
  • Installed Windows 7 (rebooted several times)
  • Installed the 4.2.4 additions
  • Rebooted after additions install
  • Shutdown of the VMs.
  • Take a snapshot (this bug caused my VDI to get corrupted several times which stopped windows to boot)
  • Enabled page fusion on both VMs.

I have then started both VMs and simply waited for them to boot.
The first one was extremely slow to boot, much more than usual when I boot 2 Win7 VMs
The second actually made it and rebooted at some point during the boot.

Once both VMs were booted, they frooze from time to time for while, programs like IE, Notepad and Explorer got display artfacts (not displaying a part of the window was always happening) until they both crashed with a BSOD.

Finally, the VM 02 gave up, explorer crashed with a memory read/write error and went berzek by constantly sending garbadge on the vNIC.

You will find two zips (VM01.zip & VM02.zip) both with the vbox.log aswell as the minidumps from the BSOD. You will also find a screenshot of VM 02 with the memory error.

Note that if I shutdown both VMs, restore the snapshot to recover from the VDI corruption, disable page fusion then reboot, everything is fine. No part of the behaviour described above appear.

Last edited 18 months ago by noteirak (previous) (diff)

Changed 18 months ago by noteirak

Changed 18 months ago by noteirak

comment:3 Changed 18 months ago by noteirak

Update : the same behaviour also happens with only one VM with page fusion ON and both VMs running.

Last edited 18 months ago by noteirak (previous) (diff)

Changed 18 months ago by noteirak

More crashin' & burnin'

comment:4 Changed 18 months ago by noteirak

Added another run. The scenario and behaviour :

  1. Start VM01, login to desktop, wait until disk is "idle".
  2. Start VM02, login to desktop, wait until disk is "idle".
  3. With VM01, go with IE on google, search for youtube, go on it take any video, start playing.
  4. With VM02, go with Chrome on google, search for youtube, go on it take any video, start playing.
  5. VM01 guest froze and rebooted.
  6. VM02 guest froze but never came back alive anymore, had to poweroff the VM.
Version 0, edited 18 months ago by noteirak (next)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use