[opensuse-factory] VirtualBox in Tumbleweed 20170414 - host modules no longer loaded by default
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? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, exactly same behavior here also. Same versions everything up to date.
On Tue, Apr 18, 2017 at 2:41 PM, René Krell
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?
René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne úterý 18. dubna 2017 13:41:15 CEST, René Krell napsal(a):
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?
René
Me too. Since last upgrade, commands 'sudo systemctl enable vboxdrv.service' and 'sudo systemctl start vboxdrv.service' are required. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On Tuesday, 18 April 2017 20:12:18 +08 Vojtěch Zeisek wrote:
Dne úterý 18. dubna 2017 13:41:15 CEST, René Krell napsal(a):
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?
René
Me too. Since last upgrade, commands 'sudo systemctl enable vboxdrv.service' and 'sudo systemctl start vboxdrv.service' are required.
I thought it was just me too. I run "sudo modprobe vboxdrv" before I can launch any of my virtual machines.
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.--
From context, I think you mean Windows 7 guest. If you really mean host, then that is a Windows problem. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-04-19 4:14 GMT+02:00 Larry Finger
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.--
From context, I think you mean Windows 7 guest. If you really mean host, then that is a Windows problem.
Yes, of course, Windows guest, and the host modules are not loaded. Sorry.
Larry
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
participants (6)
-
Chan Ju Ping -
Ken Schneider - Factory -
Larry Finger -
René Krell -
Stratos Zolotas -
Vojtěch Zeisek