Bug 198071 - emulators/virtualbox-ose-kmod: vboxdrv confusing geom
Summary: emulators/virtualbox-ose-kmod: vboxdrv confusing geom
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-27 11:13 UTC by oklaspec
Modified: 2018-01-09 07:10 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (vbox)

Attachments
failed dmesg dump (9.54 KB, text/plain)
2015-02-27 11:13 UTC, oklaspec 		no flags Details
worked dmesg dump (7.95 KB, text/plain)
2015-02-27 11:13 UTC, oklaspec 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description oklaspec 2015-02-27 11:13:00 UTC 
Created attachment 153577 [details]
failed dmesg dump

Problem concerning only for boot time with the vboxdrv enabled.
Load vboxdrv on loaded system by kldload have success and work fine.
Two discs and hardware ride of them become not very accessible.
Few available - mean that it in /dev are present but partitions is not visible
by bsdlabel and did not see anything. Fdisk - sees bsd mark.
Because of this, the OS does not boot. There was another single disk with
FreeBSD installed, but not connected to any ride is visible fine. 
Here dmesg bring both for comparison. The Kernel is copy of
generic release 9.3 plus built in ipfw and two routing tables in it.

Preview two distinct lines dmesg,
in working:
    GEOM_RAID: NVIDIA-1: Array NVIDIA-1 created.
in a failed:
    GEOM_RAID: Promise: Array Promise created.

Full dmesg from working and filed attached
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2015-02-27 11:13:00 UTC 
Auto-assigned to maintainer vbox@FreeBSD.org
Comment 2 oklaspec 2015-02-27 11:13:53 UTC 
Created attachment 153578 [details]
worked dmesg dump
Comment 3 oklaspec 2015-02-27 11:18:59 UTC 
virtualbox-ose-kmod version is 4.3.22
Comment 4 oklaspec 2015-02-27 13:26:46 UTC 
Now look again, found that vboxdrv loaded in the working case, too, 
but in another stage, after that, as geom make their work, and the
file system mounting done. Apparently at the moment read
/boot/loader.conf. This is achieved by providing in bootloader
not load driver vboxdrv.

And in the failed case, vboxdrv loaded from the folder with the
drivers in a crowd, before geom.
Comment 5 oklaspec 2015-02-27 13:27:55 UTC 
so geom failed... (see attachments)
Comment 6 oklaspec 2015-03-02 11:37:06 UTC 
Workaround is to remove vboxdrv_enable="YES" from loader.conf
The vboxdrv driver will be autoloaded later by virtual box daemons.
Comment 7 Walter Schwarzenfeld 2018-01-09 00:25:18 UTC 
I think this overcome by events, the load commands has changed (and this was on 9.3).