Hi, folks:
I've been utilizing Virtualbox from our ports to do some virtualization work for quite a long time, and feel it's so handy and easy to use. However, I might bump into one strange thing occasionally, not always, which signifies that, if I put the vboxdrv entry into /boot/loader.conf, like this:
then my box will halt at the boot time and refuse to proceed! If I remove this entry, wow, nothing odd, everything is OK. More precisely, however, to my surprise, the vboxdrv module works like a charm once loaded after boot via kldload() utility. So, has anyone here suffered from the similar quirk? If so, how do you handle it?
P.S.: I use 9.0 RC2 currently, and here is a screenshot of the cease at boot stage, taken by my very-old-and-small mobile phone, not so clear but still useful to this topic:
I've been utilizing Virtualbox from our ports to do some virtualization work for quite a long time, and feel it's so handy and easy to use. However, I might bump into one strange thing occasionally, not always, which signifies that, if I put the vboxdrv entry into /boot/loader.conf, like this:
Code:
vboxdrv_load="YES"then my box will halt at the boot time and refuse to proceed! If I remove this entry, wow, nothing odd, everything is OK. More precisely, however, to my surprise, the vboxdrv module works like a charm once loaded after boot via kldload() utility. So, has anyone here suffered from the similar quirk? If so, how do you handle it?
P.S.: I use 9.0 RC2 currently, and here is a screenshot of the cease at boot stage, taken by my very-old-and-small mobile phone, not so clear but still useful to this topic
: