Hi, Am 16.09.2011 19:47 schrieb "Alex Viskovatoff" <[email protected]>: > > On Fri, 2011-09-16 at 10:21 +0200, Ewald Ertl wrote: > > I've a laptop running since an OpenSolaris build and just upgraded to > > each version. > > Now I've updated to the latest dev-il Package Repository and switched > > the sfe repository and upgraded. > > > > I still have problems with the kvm module, so I'm using VirtualBox and > > unload the kvm module, because otherwise VirtualBox didn't start. > > > > But "suddenly " ( I do not know whats the real reason ) VirtualBox > > stops with the attached Screenshot. > > Hi Ewald, > > That's very interesting. We were aware of this problem, and have our own > workaround, described here: > http://wiki.openindiana.org/oi/Spec+Files+Extra+Repository > Thanks for your hint. I've seen the page, but have not recogniced the described problem.
> But I can confirm that the workaround described in the link you give > (http://www.virtualbox.org/ticket/1840) also works, although on amd64 > systems, the file VBoxSVC that needs to be modified is now in > /opt/VirtualBox/amd64. > > This problem is indeed caused my your using the new SFE repository, > specifically, installing runtime/gcc. This VirtualBox bug is the only > problem we have run into so far with runtime/gcc placing symbolic links > in /usr/lib, so that old VirtualBox bug report is very useful, in that > it may help us understand what is going wrong with VirtualBox here. Fine to hear, that it is for help. Thanks to all for their good work. Ewald > > Regards, > Alex > > > _______________________________________________ > OpenIndiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
