On 04/22/2017 01:06 PM, Larry Finger wrote:
On 04/18/2017 06:41 AM, René Krell wrote:
Hi all,
after an upgrade from 20170407 to 20170414 I've got trouble with virtualbox. My Windows 7 host does not start at all.
There is none of the vbox* modules loaded by default although virtualbox-host-kmp-default is up to date.
If adding them all four manually by applying 'insmod' all goes fine.
Anyone else or just me?
As you have seen, it is not you. Besides not starting the kernel modules as you report, the automatic mounting of shared folders in openSUSE TW guest VMs also stopped working.
I have just started working on the problem. As Leap 42.2 and Tumbleweed use essentially the same control files to build the RPM, it seems likely that the problem lies somewhere in TW. VirtualBox still uses the old-style /etc/init.d/ files. My first thought is that some update now requires systemctl service files. It should be easy to test this.
Larry
I recently update to VB 5.1.20 and noticed messages regarding systemd links so my guess is that VB has dropped init.d integratio and migrated to systemd support.. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org