Date: Fri, 25 Dec 2009 20:18:22 +0900 From: Daichi GOTO <daichi@ongs.co.jp> To: current@freebsd.org, freebsd-emulation@freebsd.org Subject: JFYI: VirtualBox stable/unstable setteings (3.0.51.r22902), 20091225 updated Message-ID: <4B349F7E.2030407@ongs.co.jp>
next in thread | raw e-mail | index | archive | help
My report is not strict comprehensive, but it's useful and helpful
for everyone who wants to use VirtualBox on FreeBSD.
Revision:
20091223 - first posts
20091225 - updates including some results of powerd(8) investigation
Tested environment:
host os: FreeBSD 9-current amd64 (among 12/2009)
virtualbox: virtualbox-3.0.51.r22902_3
cpu: Intel Core2 Quad Q9550
mem: 8GB
video: GeForce 9800 GT
Kernel settings issues:
- Vimage lets FreeBSD freeze within VirtualBox bridge
networking.
[workaround 1] disable Vimage, you could use bridge feature
[workaround 2] disable bridge feature, you could use Vimage
Driver issues (*2):
- Within certain combination of M/B and NVIDIA graphic
board, NVIDIA driver (x11/nvidia-driver: nvidia-driver-195.22)
and powerd(8) lead FreeBSD freeze non-reproducibly.
[workaround 1] use nv instead of nvidia driver
[workaround 2] stop powerd(8), you could use nvidia driver
relative url:
http://www.nvnews.net/vbulletin/showthread.php?t=142331
http://groups.google.com/group/mailing.freebsd.current/browse_thread/thread/9b7a85504e6b4ba3
VirtualBox settings:
-------------------------------------------------------------
| | effects on the host os stability|
-------------------------------------------------------------
| ACPI | NO |
| IO APIC | NO |
| PAE/NX | (not checked) |
| Core numbers | YES (*2) |
| VT-x/AMD-V | NO |
| nested paging | (not checked) |
| 3D acceleration | (not checked) |
| IDE controller type | NO |
| Additional controller | NO |
| CD/DVD drive host | NO |
| CD/DVD drive image file | NO |
| FDD drive host | (not checked) |
| FDD drive image file | (not checked) |
| Audio | (not checked) |
| Network adapter type | NO |
| Network NAT | NO |
| Network bridge | NO |
| Network inner network | (not checked) |
| Network host only | (not checked) |
| Serial port | (not checked) |
| share folder | (not checked) |
| Guest OS sort | NO |
-------------------------------------------------------------
Hardware health:
- Weakened PC power unit or less-power power unit leads PC
very unstable condition. If you encounter non-reproducible
error or panic, you should better to check your PC power unit.
- Unstable memory leads FreeBSD system panic and fatal trap.
If you encounter "segmentaion fault", "panic" or "fatal trap"
error, shutdown system and check your PC memory health with
memtest86+. (Ubuntu install CD has memtest86+ feature.
Using Ubuntu as memetest86+ checker is reasonable way).
If you have luck, updating BIOS and set DRAM settings for
stable resolves this issue.
- Hard Disk should be health. Check your disk status by
smartmontools (sysutils/smartmontools).
[Recap points]
- Check your PC health first, especially for Power unit,
memory and Hard disk.
- Remove Vimage if you want to use bridge networking feature
of VirtualBox.
- If you want to use nvidia-driver, stop powerd(8) daemon.
If you want to use powerd(8) daemon, then use nv instead of
nvidia driver.
Notes:
(*1) relative url:
http://www.nvnews.net/vbulletin/showthread.php?t=142331
http://groups.google.com/group/mailing.freebsd.current/browse_thread/thread/9b7a85504e6b4ba3
(*2) Multicore attached virtual environment easily and frequently
lets FreeBSD freeze.
--
Daichi GOTO
CEO | ONGS Inc.
81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
LinkedIn: http://linkedin.com/in/daichigoto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B349F7E.2030407>