danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,504
I know VirtualBox isn't exactly a plugin, but it's kind of like one--hope this forum is a decent place to post.
I'm trying to set up Zoneminder on my FreeNAS 9.3 system. Since the FreeBSD port isn't of the latest version, and the source doesn't compile directly in a jail, I decided to build a Ubuntu VM inside my VirtualBox jail, and install Zoneminder there. I built the VM, installed Ubuntu Server 14.04 LTS, installed all the updates and appropriate packages for zoneminder, and life was good. Except...
I didn't want my recordings chewing up space on the VirtualBox virtual disk file, and I wanted them to be readily accessible outside of the VM, so I set up a dataset on the FreeNAS server, mounted it as storage to the VirtualBox jail, installed the VBox guest additions inside the VM, and mounted two directories from that dataset as shared folders inside the VM. This is working--I can create a file from the FreeNAS CLI, and see it inside the mountpoint in the VM, and vice versa. All peachy keen. Except...
Zoneminder apparently relies on being able to create symlinks within the images and events directories. VirtualBox apparently does not, by default, support symlinks in shared folders. Also apparently (see https://github.com/mitchellh/vagrant/issues/713 and http://stackoverflow.com/questions/...albox-4-3-to-use-symlinks-on-guest-for-meteor), as of VBox 4.1.8, you can set an option to enable symlinks if the host OS supports them (FreeBSD of course does) and the guest OS supports them (which Linux does).
All I need to do, according to those sources, is issue the command
for each shared directory that I want to do this for. And here's the problem--VBoxManage doesn't seem to see that, or any other, VM:
I have only one VirtualBox jail, and I have other VMs running in it at the moment. I feel like I'm probably missing something very simple, but I'm not sure what it is. Any ideas?
Edit: After noticing this ticket against VirtualBox, I did 'su vbox' inside the jail. I was then able to list the VMs and make the change. After restarting the jail and launching the VM, zoneminder appears to be happily recording away, and not complaining about an inability to create symlinks.
I'm trying to set up Zoneminder on my FreeNAS 9.3 system. Since the FreeBSD port isn't of the latest version, and the source doesn't compile directly in a jail, I decided to build a Ubuntu VM inside my VirtualBox jail, and install Zoneminder there. I built the VM, installed Ubuntu Server 14.04 LTS, installed all the updates and appropriate packages for zoneminder, and life was good. Except...
I didn't want my recordings chewing up space on the VirtualBox virtual disk file, and I wanted them to be readily accessible outside of the VM, so I set up a dataset on the FreeNAS server, mounted it as storage to the VirtualBox jail, installed the VBox guest additions inside the VM, and mounted two directories from that dataset as shared folders inside the VM. This is working--I can create a file from the FreeNAS CLI, and see it inside the mountpoint in the VM, and vice versa. All peachy keen. Except...
Zoneminder apparently relies on being able to create symlinks within the images and events directories. VirtualBox apparently does not, by default, support symlinks in shared folders. Also apparently (see https://github.com/mitchellh/vagrant/issues/713 and http://stackoverflow.com/questions/...albox-4-3-to-use-symlinks-on-guest-for-meteor), as of VBox 4.1.8, you can set an option to enable symlinks if the host OS supports them (FreeBSD of course does) and the guest OS supports them (which Linux does).
All I need to do, according to those sources, is issue the command
Code:
VBoxManage setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/SHARE_NAME 1
for each shared directory that I want to do this for. And here's the problem--VBoxManage doesn't seem to see that, or any other, VM:
Code:
root@virtualbox2:/ # VBoxManage setextradata zoneminder VBoxInternal2/SharedFoldersEnableSymlinksCreate/images 1 VBoxManage: error: Could not find a registered machine named 'zoneminder' VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 804 of file VBoxManageMisc.cpp root@virtualbox2:/ # VBoxManage list vms root@virtualbox2:/ #
I have only one VirtualBox jail, and I have other VMs running in it at the moment. I feel like I'm probably missing something very simple, but I'm not sure what it is. Any ideas?
Edit: After noticing this ticket against VirtualBox, I did 'su vbox' inside the jail. I was then able to list the VMs and make the change. After restarting the jail and launching the VM, zoneminder appears to be happily recording away, and not complaining about an inability to create symlinks.
Last edited: