VMs won't start after Update to 9.10.1-U1

[Moppen]

Aloha,

after installing the 9.10.1-U1 Update my out-of-the-Box VirtualBox-Jail won't start any of the VMs that very running happily before:

Maybe someone can help, because I have simply no idea what is going on:

Code:

Exception Object
(
  [message:protected] => The virtual machine 'Windows 10 (FTP)' has terminated unexpectedly during startup with exit code 1
  [string:Exception:private] =>
  [code:protected] => 0
  [file:protected] => /usr/local/www/phpvirtualbox/lib/vboxconnector.php
  [line:protected] => 2382
  [trace:Exception:private] => Array
  (
  [0] => Array
  (
   => /usr/local/www/phpvirtualbox/lib/vboxconnector.php
  [line] => 928
  [function] => remote_progressGet
  [class] => vboxconnector
  [type] => ->
  [args] => Array
  (
  [0] => Array
  (
  [progress] => df0a4b5c50770452-00000000000000e7
  [_persist] => Array
  (
  [vboxHandle] => df0a4b5c50770452-00000000000000e5
  )

  [fn] => progressGet
  )

  )

  )

  [1] => Array
  (
   => /usr/local/www/phpvirtualbox/lib/ajax.php
  [line] => 309
  [function] => __call
  [class] => vboxconnector
  [type] => ->
  [args] => Array
  (
  [0] => progressGet
  [1] => Array
  (
  [0] => Array
  (
  [progress] => df0a4b5c50770452-00000000000000e7
  [_persist] => Array
  (
  [vboxHandle] => df0a4b5c50770452-00000000000000e5
  )

  [fn] => progressGet
  )

  [1] => Array
  (
  [0] => Array
  (
  [data] => Array
  (
  [responseData] => Array
  (
  [progress] => df0a4b5c50770452-00000000000000e7
  [info] => Array
  (
  [completed] => 1
  [canceled] =>
  [description] => Starting VM
  [operationDescription] => Creating process for virtual machine "Windows 10 (FTP)" (headless)
  [timeRemaining] => Array
  (
  )

  [timeElapsed] => Array
  (
  [days] => 17071
  [hours] => 17
  [minutes] => 57
  [seconds] => 44
  )

  [percent] => 0
  )

  )

  [success] => 1
  [key] => 53474945cfd7ac0bf8114767c209c2a6
  )

  [errors] => Array
  (
  )

  [persist] => Array
  (
  )

  [messages] => Array
  (
  )

  )

  )

  )

  )

  )

  [2] => Array
  (
   => /usr/local/www/phpvirtualbox/lib/ajax.php
  [line] => 309
  [function] => progressGet
  [class] => vboxconnector
  [type] => ->
  [args] => Array
  (
  [0] => Array
  (
  [progress] => df0a4b5c50770452-00000000000000e7
  [_persist] => Array
  (
  [vboxHandle] => df0a4b5c50770452-00000000000000e5
  )

  [fn] => progressGet
  )

  [1] => Array
  (
  [0] => Array
  (
  [data] => Array
  (
  [responseData] => Array
  (
  [progress] => df0a4b5c50770452-00000000000000e7
  [info] => Array
  (
  [completed] => 1
  [canceled] =>
  [description] => Starting VM
  [operationDescription] => Creating process for virtual machine "Windows 10 (FTP)" (headless)
  [timeRemaining] => Array
  (
  )

  [timeElapsed] => Array
  (
  [days] => 17071
  [hours] => 17
  [minutes] => 57
  [seconds] => 44
  )

  [percent] => 0
  )

  )

  [success] => 1
  [key] => 53474945cfd7ac0bf8114767c209c2a6
  )

  [errors] => Array
  (
  )

  [persist] => Array
  (
  )

  [messages] => Array
  (
  )

  )

  )

  )

  )

  )

  [previous:Exception:private] =>
)

 

[Dunay]

Hi,

I have the same problem, the same Exception. The VM runs Debian 64 bit and has a bridged network adapter (on epair1b).

After the update to 9.10.1-U1 in the Virtualbox jail /home/vbox/.config/VirtualBox/VBoxSVC.log contains the bellow lines.

Any Idea?

Code:

00:00:01.111419 nspr-2   Failed to open "/dev/vboxdrvu", errno=2, rc=VERR_VM_DRIVER_NOT_INSTALLED                                   
00:00:01.113105 nspr-2   failed to create vboxnet0, error (0x80004005)       

 

[danb35]

Sounds like a bug should be reported, probably attaching a debug file from your system. Easiest way to do that is the Support button in the web GUI.

 

[m0nkey_]

Sounds like 9.10.1-U1 is missing the VirtualBox kernel module. I'm firing up a test machine and will update shortly.

Update: Tested and verified kernel module is loaded. Keep in mind, this was a fresh install, not a upgrade.

 

[Muddro]

Same issue here. Rebooted back into the previous boot environment and everything is working again. Someone should submit a ticket and wait for a fix before upgrading.

 

[andreas ahlsdorf]

Same issue here. Bootet also back into 9.10-1.

 

[Orris]

Hi,

I have the same problem, the same Exception. The VM runs Debian 64 bit and has a bridged network adapter (on epair1b).

After the update to 9.10.1-U1 in the Virtualbox jail /home/vbox/.config/VirtualBox/VBoxSVC.log contains the bellow lines.

Any Idea?

Code:

00:00:01.111419 nspr-2   Failed to open "/dev/vboxdrvu", errno=2, rc=VERR_VM_DRIVER_NOT_INSTALLED                                  
00:00:01.113105 nspr-2   failed to create vboxnet0, error (0x80004005)      

I have the same issue with the same Logs. VBoxHeadless also moaning about Kernel Driver Not Installed

Sounds like 9.10.1-U1 is missing the VirtualBox kernel module. I'm firing up a test machine and will update shortly.

Update: Tested and verified kernel module is loaded. Keep in mind, this was a fresh install, not a upgrade.

Tried kldload vboxdrv on host, says that is loaded fine. Also tried to add "add path 'vbox*' unhide" to devfs.rules with no luck

Back to 9.10.1 and everything works

 

[diskdiddler]

Can I ask a stupid question,.......


When a bug like the one here is found (or any bug, even quite a nastier one) if I DON'T upgrade my box, then wait for the patch, then choose update. Would the bad piece of code be removed from the patch queue or in the very least the fixed piece of code be written over the top of the bad one shortly after as the patches install sequentially?

I am sometimes wanting to hold off, just to be sure with these bugs.

 

[danb35]

Someone should submit a ticket

You're someone, aren't you?

 

[Stefan Krieger]

Glad to see someone is reporting my problem. Reverted back to prior version for now. Will I eventually need to rebuild by VMs , at least for 10?

 

[m0nkey_]

Things won't get fixed unless somebody files a bug report at https://bugs.freenas.org. Don't expect others on this forum to report the bug for you. You're the one with the logs, access to the box, etc.

 

[danb35]

Will I eventually need to rebuild by VMs , at least for 10?

I think there's a plan to migrate jails into FN10, and IIRC it involves creating a VM which will house your current jails. For a VirtualBox jail, that strikes me too many layers of virtualization--FreeNAS -> VM -> jail -> VM. I'd expect there's a way to migrate a VM from VirtualBox to bhyve, but I don't know what that way is.

 

[JoshDW19]

Sorry to be the bearer of bad news: https://bugs.freenas.org/issues/15928

As Jordan mentioned iohyve may be an option going forward.

 

[danb35]

https://bugs.freenas.org/issues/15928

Am I reading that bug correctly as saying that support for the VirtualBox jail has been removed beginning in 9.10.1-U1? Or that this is going to happen with -U2? Seems like a pretty drastic change to make in a sub-point release (which, unfortunately, is far from unheard-of with FreeNAS).

 

[JoshDW19]

Am I reading that bug correctly as saying that support for the VirtualBox jail has been removed beginning in 9.10.1-U1? Or that this is going to happen with -U2? Seems like a pretty drastic change to make in a sub-point release (which, unfortunately, is far from unheard-of with FreeNAS).

Yes I believe you are reading that correctly. The virtualbox jail template was broken and not maintained so it has been removed. My understanding is that the jail template is still out there and available, but it will be a "use at your own risk" type of thing considering it's now unsupported / not included in FreeNAS 9.10.x. It will be up to the user to locate the template and set it up on their system. Sorry guys.

 

[danb35]

And this is iXSystems' idea of a STABLE software version? One that in a sub-point release suddenly and without warning drops support for significant features? And yes, the ability to run arbitrary operating systems in a VM with a nice GUI to manage them is a pretty significant feature. bhyve/iohyve aren't close to being a replacement--even if bhyve is a better hypervisor, guest OS support is much narrower (compare https://wiki.freebsd.org/bhyve with https://www.virtualbox.org/wiki/Guest_OSes), there's no clear way to migrate a VM from VirtualBox to bhyve, and there's no web or other GUI.

Fail, folks. This is not a way to encourage your users to keep up-to-date.

 

[adrianwi]

I was contemplating upgrading to the 9.10 train from 9.3.1. Not anymore :(

 

[JoshDW19]

I use virtualbox pretty regularly for my virtualization and testing needs, so I can understand the frustration. The problem as I understand it is this was a user contributed feature that is no longer maintained. It's grown out-of-date over time, and is breaking key features of FreeNAS.

I'd encourage those that depend on this feature to speak up. I can't guarantee it will change anyone's minds (as I don't make the decisions on this), but I'll make sure to ask the development team to review this thread after others have a chance to respond.

Thanks for the feedback everyone.

 

[danb35]

It'd be interesting to see how many FreeNAS users use the VirtualBox jail. The telemetry information FreeNAS sends should have this information, or at least a good proxy for it, in the included 'zfs list' (which would include the dataset for the VirtualBox jail). Of course, that would only count the users who haven't disabled telemetry (I'm pretty sure it's enabled by default), but it'd be a start.

 

[depasseg]

As a user who doesn't use VB, this doesn't affect me. However, as a user who uses freenas, the fact that a feature that is in use by many others can be dropped without any warning or communication concerns me greatly. Or perhaps I missed the notice that it was being removed (other than reading the bug of course).