Ian, Thanks for your message. I found multiple reports of running VirtualBox in a non-global zone on Solaris. Most of these referred to old(er) VirtualBox versions, so I’m not sure myself where things stand today.
BTW: No need for a tarball version - SmartOS pkgtrans can break up the IPS package no problem. Generating an install script from the files and directories is thus a non issue. What remains is injecting/loading the drivers into the global zone and passing them through to the native zone via zonecfg. That’s why I asked for suggestions on how to best integrate drivers into SmartOS… I built my own usb key images in the past but that was always a rather complicated process. Wonder whether the same could be accomplished via e.g. a script in /opt/custom… Thanks, Peter > Am 26.09.2016 um 01:00 schrieb Ian Collins <[email protected]>: > > On 26/09/16 10:32 am, Peter Kelm wrote: >> I need some more advanced „hardware“ (Q35 chipset, UEFI instead of a >> traditional BIOS) than what the (aging) QEMU/KVM supports (QEMU seems to be >> stuck at version 0.14.1). So instead of leaving SmartOS behind (and going >> with something inferior) I’m trying to get VirtualBox up and running on >> SmartOS in a native zone. >> >> - What is the best way to add drivers to a native zone? > > I don't think you can due to the zones being "sparse". The VB install needs > pkgadd and access to / as well as driver install. VB works fine in a Solaris > zones, but if I remember correctly, only in a whole root zone. There used to > be a tarball version of the VB download, but that appears to have been > dropped long ago. > > Cheers, > Ian. > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
