VirtualBox v3.0.X system lock up issue

[Ramshankar]

No this issue is still not resolved two hard locks since updating to 3.0.10. It is pretty frustrating as there appears to be no progress in solving this problem for opensolaris.

Sorry I couldn't read all your previous posts in the long thread, quick question- Guest SMP?

[ljw1]

Yes the guest does have the smp on, 2 cpu set. The weird thing is it rarely hard locks the host when I am actively using the guest, only when it has been sitting a while. Any suggestions?

[jrichards]

I'm running B126, on an i7 860 w/ 8gb of RAM, virtualbox 3.0.10, and still getting lockups after a couple hours. I was getting these lockups on my old 2x dual core Opteron 280 rig as well. I replaced that rig because the i7 is faster, uses 1/3 the power, etc, but I was really hoping that with a fresh install of opensolaris the lockup issues would stop. This seems to have started after the 3d graphics stuff was added. I have tried the guests w/ the 12MB of virtual graphics memory, and with only 4MB (trying to 'disable' the graphics stuff) but that hasn't seemed to help. other notes:

-all guests are windows (2003 32bit)
-single vCPU
-768MB to 1GB ram per guest
-single vdi per guest
-guests started with VBoxHeadless, using VBox's RDP for console (will disable that next)
-usb disabled
-audio disabled

I sure miss the stability of the older version of VBox.

[jrichards]

attached panic message:

Nov 14 05:26:56 sol unix: [ID 836849 kern.notice]
Nov 14 05:26:56 sol ^Mpanic[cpu2]/thread=ffffff000f50dc60:
Nov 14 05:26:56 sol genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff000f50d940 addr=40000000010 occurred in module "unix" due to an illegal access to a user address
Nov 14 05:26:56 sol unix: [ID 100000 kern.notice]
Nov 14 05:26:56 sol unix: [ID 839527 kern.notice] sched:
Nov 14 05:26:56 sol unix: [ID 753105 kern.notice] #pf Page fault
Nov 14 05:26:56 sol unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x40000000010
Nov 14 05:26:56 sol unix: [ID 243837 kern.notice] pid=0, pc=0xfffffffffb8a1563, sp=0xffffff000f50da38, eflags=0x10246
Nov 14 05:26:56 sol unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 26f8<vmxe,xmme,fxsr,pge,mce,pae,pse,de>
Nov 14 05:26:56 sol unix: [ID 624947 kern.notice] cr2: 40000000010
Nov 14 05:26:56 sol unix: [ID 625075 kern.notice] cr3: 4000000
Nov 14 05:26:56 sol unix: [ID 625715 kern.notice] cr8: c
Nov 14 05:26:56 sol unix: [ID 100000 kern.notice]
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] rdi: 40000000010 rsi: 0 rdx: ffffff000f50dc64
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] rcx: 1 r8: ffffff02f7327a30 r9: fffffffffbd07f90
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] rax: 0 rbx: 0 rbp: ffffff000f50da80
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] r10: ffffff017c23a000 r11: 1 r12: 40000000010
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] r13: ffffff02f43b7c28 r14: 40000000000 r15: ffffff02f5dc3bb0
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] fsb: fffffd7fff136a00 gsb: ffffff02d7828500 ds: 4b
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] es: 4b fs: 0 gs: 0
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] trp: e err: 2 rip: fffffffffb8a1563
Nov 14 05:26:56 sol unix: [ID 592667 kern.notice] cs: 30 rfl: 10246 rsp: ffffff000f50da38
Nov 14 05:26:56 sol unix: [ID 266532 kern.notice] ss: 38
Nov 14 05:26:56 sol unix: [ID 100000 kern.notice]
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50d820 unix:die+dd ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50d930 unix:trap+177e ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50d940 unix:cmntrap+e6 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50da80 unix:atomic_cas_ptr+3 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50db50 zfs:arc_evict+1bb ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50db80 zfs:arc_adjust+75 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50db90 zfs:arc_shrink+d5 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50dbd0 zfs:arc_kmem_reap_now+43 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50dc40 zfs:arc_reclaim_thread+f9 ()
Nov 14 05:26:56 sol genunix: [ID 655072 kern.notice] ffffff000f50dc50 unix:thread_start+8 ()
Nov 14 05:26:56 sol unix: [ID 100000 kern.notice]
Nov 14 05:26:56 sol genunix: [ID 672855 kern.notice] syncing file systems...
Nov 14 05:26:56 sol genunix: [ID 904073 kern.notice] done
Nov 14 05:26:57 sol genunix: [ID 111219 kern.notice] dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
Nov 14 05:27:54 sol genunix: [ID 409368 kern.notice] ^M100% done: 284946 pages dumped, compression ratio 2.19,
Nov 14 05:27:54 sol genunix: [ID 851671 kern.notice] dump succeeded
Nov 14 05:55:59 sol genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Version snv_126 64-bit

[Ramshankar]

Is it possible to get a core of such a session?

[ljw1]

The problem with hard locking on my host is still there with multi-processor selected, soon as uni processor is used the crashing disappears. Has this been fixed in the 3.1 beta?

[jrichards]

Ramshankar,

I have since updated to svn_127, and still had lockups. I then went to VBox 3.1.0 beta 1, and still had issues. Next, I found that there is an issue with the rge network drivers (http://defect.opensolaris.org/bz/show_bug.cgi?id=10710) which was supposed to be resolved, however the opensolaris server would consistently loose drop the network under moderate CIFS usage (without VBox running) . I changed the rge driver (http://homepage2.nifty.com/mrym3/taiyod ... t.3.tar.gz) then performed a network load test (copied about 150GB of files around the network for a couple hours using CIFS) and the network issue "seemed" resolved. I fired up VBox (still 3.10.0 beta1) and let it rip but after a few hours, the host was locked up again.

I would love to assist in collecting data to help get a resolution, can you detail what you need collected and how, and I will provide it.

Kind Regards,
Justin

EDIT: corrected "3.10.0 beta 1" to "3.1.0 beta 1"

[ljw1]

So has there been changes to the SMP in the new 3.1 series? It was not immediately clear from the changelog.

[Charlesedwin]

Hello Friends.
I read your entire post I'm having the same issue as well across two Ultra-24s running Solaris 10x86 update 6 and update 7 running both Windows XP 32-bit and Windows 7 64-bit as the guest OS. No single application triggers the crash, sometimes Windows crashes as it's loading and the lock ups take down Solaris entirely. Disabling USB support in the VDI settings did not prevent the lock ups unfortunately. Using the latest 3.0.2 build.