Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Bug 208204] emulators/virtualbox-ose: Current Virtualbox almost unusable if host has > 4 cores

0 views
Skip to first unread message

bugzilla...@freebsd.org

unread,
Apr 4, 2016, 7:13:21 AM4/4/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208204

Mark Linimon <lin...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|freebsd-ports-bugs@FreeBSD. |vb...@FreeBSD.org
|org |
Summary|Current Virtualbox almost |emulators/virtualbox-ose:
|unusable if host has > 4 |Current Virtualbox almost
|cores |unusable if host has > 4
| |cores

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulat...@freebsd.org"

bugzilla...@freebsd.org

unread,
Apr 6, 2016, 11:38:45 AM4/6/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208204

--- Comment #3 from Maurizio <mauriz...@gmail.com> ---
You can try to use CPUSET(1) to start the VMs as explained in:
https://lists.freebsd.org/pipermail/freebsd-emulation/2012-November/010209.html

On an Intel Core i7-3930K based PC I am starting a Windows 7 VM with the
command :
# cpuset -l 4-7 VBoxHeadless --comment "Win7;5901" --startvm "Win7;5901"

bugzilla...@freebsd.org

unread,
Jul 27, 2016, 4:22:12 PM7/27/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208204

--- Comment #4 from r...@wintek.com ---
I recently upgraded to 10.3-STABLE r303336, and I decided to try upgrading
virtualbox to the newly committed 5.0.26 at the same time.

Hyperthreading is enabled, so FreeBSD reports having 12 cores to play with.

It now seems to work fine!

My Win7 VM (which hadn't been touched since I filed this bug report back in
March) is now perfectly usable. Unless some stability issues show up (it's been
running for almost 3 hours now), it looks to me like this ticket can be closed.

bugzilla...@freebsd.org

unread,
Jul 27, 2016, 4:56:11 PM7/27/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208204

Jung-uk Kim <jk...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jk...@FreeBSD.org
Resolution|--- |Overcome By Events
Status|New |Closed

--- Comment #5 from Jung-uk Kim <jk...@FreeBSD.org> ---
VirtualBox 5.0.26 fixed the issue. Closing.
0 new messages