SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Even virtualbox-kernel works with kernel 6.8.1. But I had to write my own rc.vboxdrv because for some
reason the original rc.vboxdrv script didn't work.
Code:
kernel_requires_modules_signature: command not found
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Original Poster
Rep:
FWIW: The most recent test build and development snapshot will not install (build and install) with the new 6.9-rc1 kernel.
Tomorrow I'll take another run at it.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
FWIW: The most recent test build and development snapshot will not install (build and install) with the new 6.9-rc1 kernel.
Tomorrow I'll take another run at it.
A new test build was released just twenty minutes ago, but, unfortunately, it does
not solve problem, i.e., it will not install/build. https://www.virtualbox.org/wiki/Testbuilds
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
FWIW: The most recent test build and development snapshot will not install (build and install) with the new 6.9-rc1 kernel.
Tomorrow I'll take another run at it.
Quote:
Originally Posted by cwizardone
A new test build was released just twenty minutes ago, but, unfortunately, it does
not solve problem, i.e., it will not install/build. https://www.virtualbox.org/wiki/Testbuilds
OK, a new development snapshot, revision 162463, was released about ten minutes ago and it works. It spit out the same errors while installing, but did work afterwards.
YMMV.
Last edited by cwizardone; 03-26-2024 at 02:22 PM.
OK, a new development snapshot, revision 162463, was released about ten minutes ago and it works. It spit out the same errors while installing, but did work afterwards.
YMMV.
A warning has been issued that there is the possibility of the host crashing when VM's make use of bridged networking et al
ATTENTION: PLEASE REFRAIN FROM UPGRADING TO 7.0.16 FOR NOW. THIS RELEASE HAS AN ISSUE WHICH MIGHT CAUSE HOST OS CRASH WHEN VM IS CONFIGURED TO USE BRIDGED OR HOST-ONLY NETWORKING. WE WILL SEND AN ANNOUNCEMENT TO MAILING LISTS WHEN FIX WILL BE AVAILABLE FOR DOWNLOAD.
I did upgrade yesterday morning before there was a warning. So far it is stable in bridged networking mode but I am willing to restrict my usage of VM's before a fix is available.
I do usually install / upgrade using the script package install
When I installed yesterday morning I did encounter the following when installing:
Code:
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing VirtualBox for Linux installation 100%
VirtualBox Version 7.0.16 r162802 (2024-04-12T20:16:59Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python2.7, installing bindings...
Python found: python3, installing bindings...
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` and ``easy_install``.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://github.com/pypa/setuptools/issues/917 for details.
********************************************************************************
!!
self.initialize_options()
ERROR setuptools_scm._file_finders.git listing git files failed - pretending there aren't any
zip_safe flag not set; analyzing archive contents...
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Original Poster
Rep:
Thanks for the heads up.
I've had some trouble shutting down windowsXp-sp3 in VirtualBox-7.0.16.
Just reverted to 7.0.14 and all has returned to normal.
Last edited by cwizardone; 04-18-2024 at 09:41 AM.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by slack-uke
BEWARE
A warning has been issued that there is the possibility of the host crashing when VM's make use of bridged networking et al
ATTENTION: PLEASE REFRAIN FROM UPGRADING TO 7.0.16 FOR NOW. THIS RELEASE HAS AN ISSUE WHICH MIGHT CAUSE HOST OS CRASH WHEN VM IS CONFIGURED TO USE BRIDGED OR HOST-ONLY NETWORKING. WE WILL SEND AN ANNOUNCEMENT TO MAILING LISTS WHEN FIX WILL BE AVAILABLE FOR DOWNLOAD.
I did upgrade yesterday morning before there was a warning. So far it is stable in bridged networking mode but I am willing to restrict my usage of VM's before a fix is available.
I do usually install / upgrade using the script package install
When I installed yesterday morning I did encounter the following when installing:
Code:
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing VirtualBox for Linux installation 100%
VirtualBox Version 7.0.16 r162802 (2024-04-12T20:16:59Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python2.7, installing bindings...
Python found: python3, installing bindings...
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` and ``easy_install``.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://github.com/pypa/setuptools/issues/917 for details.
********************************************************************************
!!
self.initialize_options()
ERROR setuptools_scm._file_finders.git listing git files failed - pretending there aren't any
zip_safe flag not set; analyzing archive contents...
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
I also install by running their .run file, but I didn't see those errors. The install messages were clean as usual.
IIRC the install said it found python 2.7 and 3.9 (in Slackware64 15.0). That's different from your messages where it said just python 3.
I'm running Slackware64 15.0 with kernel 6.8.7.
VirtualBox 7.0.16 is running OK here two Debian vms with bridged network, but I don't use it often.
Now what they will do? Release a 7.0.16 162803?
Distribution: Slackware 15.0 64-bit & Current 64-bit
Posts: 83
Rep:
Quote:
Originally Posted by Paulo2
I also install by running their .run file, but I didn't see those errors. The install messages were clean as usual.
IIRC the install said it found python 2.7 and 3.9 (in Slackware64 15.0). That's different from your messages where it said just python 3.
I'm running Slackware64 15.0 with kernel 6.8.7.
VirtualBox 7.0.16 is running OK here two Debian vms with bridged network, but I don't use it often.
Now what they will do? Release a 7.0.16 162803?
Apologies I should have clarified my platform -- This occurred on a Slackware64 Current host. I did not get such errors when installing on Slackware64 15.0
The WARNING issued by Oracle on the virtualbox.org website appears to apply to all 7.0.16 hosts BUT there seemed to be a flurry of problems on Hosts running Microsoft Windows 11 as reported on the Virtualbox forums there. It is too early to tell if the Hosting is specific to Windows 11 or across the board. I suspect it will take some days to clearly define the source of the problem and design a fix that then will be needed to be tested before released.
In two days I have not encountered any issues running two VMs (Linux) on the Slackware64 Current host using bridged networking except for the errors generated during installation of Virtualbox 7.0.16 itself. I have not tested any of my MS Windows XP, 2K, or 10 Virtual Guests.
Just installed 7.0.16 here (yes, I read the WARNING before installing).
Win11 guest from the OEM raw disk with NAT booted just fine, activation ok in bare metal (dual boot from Slackware's grub2) and VM (from vbox). Guest additions upgraded to 7.0.16 either. No issues at all in either mode.
EDIT: got the python deprecation messages too. No worries here. vbox devs will need to deal with these warnings at some point.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by slack-uke
Apologies I should have clarified my platform -- This occurred on a Slackware64 Current host. I did not get such errors when installing on Slackware64 15.0
The WARNING issued by Oracle on the virtualbox.org website appears to apply to all 7.0.16 hosts BUT there seemed to be a flurry of problems on Hosts running Microsoft Windows 11 as reported on the Virtualbox forums there. It is too early to tell if the Hosting is specific to Windows 11 or across the board. I suspect it will take some days to clearly define the source of the problem and design a fix that then will be needed to be tested before released.
In two days I have not encountered any issues running two VMs (Linux) on the Slackware64 Current host using bridged networking except for the errors generated during installation of Virtualbox 7.0.16 itself. I have not tested any of my MS Windows XP, 2K, or 10 Virtual Guests.
No problem. I'm on the safe(-stable) side on this Slackware cycle
I do have a spare partition with -current installed to see how things run,
but I don't go there often.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
