ports/144959: VirtualBox breaks after portupgrade
Monty Hall
kungfu_disciple at sbcglobal.net
Mon Mar 22 16:00:11 UTC 2010
>Number: 144959
>Category: ports
>Synopsis: VirtualBox breaks after portupgrade
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 22 16:00:10 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Monty Hall
>Release: 8
>Organization:
>Environment:
FreeBSD XXX.com 8.0-STABLE FreeBSD 8.0-STABLE #10 r205388M: Sat Mar 20 22:26:34 EDT 2010 root at XXX.com:/usr/obj/usr/src/sys/INSPIRON i386
>Description:
=== The following is my post to the FreeBSD forums ===
=== http://forums.freebsd.org/showthread.php?t=12541 ===
*Current virtualbox-ose-3.1.4, not sure what the previous was (though I portupgrade -ar ~2/3 times week).
*When I remove the /tmp/.vbox*, I get the following popup when I try to execute a virtual machine.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {99404f50-dd10-40d3-889b-dd2f79f1e95e}
*Log says:
[code]
00:00:01.341 REM: VBoxREM32
00:00:01.354
00:00:01.354 !!Assertion Failed!!
00:00:01.354 Expression: !((uintptr_t)pvSample & 7)
00:00:01.354 Location : /tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.4_OSE/src/VBox/VMM/STAM.cpp(613) int
stamR3RegisterU(UVM*, void*, void (*)(VM*, void*), void (*)(VM*, void*, char*, size_t), STAMTYPE, STAMVISIBILITY, const char*, STAMUNIT, const
char*)
00:00:01.355 2d22af3c - /REM/TbFlush
[/code]
Code for assertion is here: [url]http://www.virtualbox.org/svn/vbox/trunk/src/VBox/VMM/STAM.cpp[/url]. Looks like some alignment issue.
*I have more than one virtual machine, both don't work
*Work fine for the longest time.
*fwiw: using zfs KVA=512 on a 2GB Machine, just added another drive to the zpool.
*uname:
[code]
FreeBSD XXX 8.0-STABLE FreeBSD 8.0-STABLE #10 r205388M: Sat Mar 20 22:26:34 EDT 2010 root at XXX:/usr/obj/usr/src/sys/INSPIRON i386
[/code]
Come to think of it, I did just compile my kernel after doing an svn update, hope this wasn't the cause of the problem. And since I've made minor changes (KVA=512 -> 500 -> 512) and adding a few device quirks, I don't have the old kernel where things DID work.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list