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.
For Slackware users:
1. Click on the link above for the version you want.
2. On the left side of the page you will see the word, "Downloads." Click on it.
3. In the list of "VirtualBox x.y.z platform packages," click on, "Linux Distributions."
4. In the list of "VirtualBox x.y.z for linux," right click on "All Distributions," and then "save link as" to wherever you want to store it on your computer.
5. Go to wherever you stored it and, as root, run,
sh ./virtualbox-x.y.z.run
Support VirtualBox RDP, disk encryption, NVMe and PXE boot for Intel cards. See this chapter from the User Manual for an introduction to this Extension Pack. The Extension Pack binaries are released under the VirtualBox Personal Use and Evaluation License (PUEL). Please install the same version extension pack as your installed version of VirtualBox.
Today we are announcing the open-source release of our KVM backend for Virtualbox.
Quote:
For the past few months we have been working hard to provide a fast, reliable and secure KVM backend for VirtualBox. VirtualBox is a multi-platform Virtual Machine Monitor (VMM) with a great feature set, support for a wide variety of guest operating systems, and a consistent user interface across different host operating systems.
Cyberus Technology’s KVM backend allows VirtualBox to run virtual machines utilizing the Linux KVM hypervisor instead of the custom kernel module used by standard VirtualBox. Using KVM comes with a number of benefits.
Our customers use virtualization to isolate different security domains from each other. They rely on further hardening of the host system for additional security. This kind of hardening is needed to get certification from government bodies and as a result a hard requirements for our customers.
In client scenarios, Windows is often the guest system of choice. A lot of the security features that get built into Windows rely on virtualization. In cases where Windows is already virtualized, additional support from the Hypervisor is needed to enable those features. KVM provides a lot of the needed support to improve Windows’ security in virtualized environments.
In addition, modern hardware comes with many features that enhance virtualization performance, such as interrupt virtualization. All of the use cases above are currently difficult to support with the stock VirtualBox kernel module. However, the open-source KVM module, which is included in the Linux kernel by default, supports these use cases easily.
I am going to try to compile this when I get home. If anyone gets this to compile reply to this thread. I am interested in seeing how it performs.
So far, my progress. Included --disable-vmmraw in the ./config. Had to utilize the xml.patch from the 7.0 VBox slackbuild. Had to utilize "VBOX_WITH_RAW_MODE := 1" to get past the second failure to build.
I don't have much time to devote to it tonight, I'd be curious how it would go on a multilib system, is this defaulted for both sets of libraries?
So far, my progress. Included --disable-vmmraw in the ./config. Had to utilize the xml.patch from the 7.0 VBox slackbuild. Had to utilize "VBOX_WITH_RAW_MODE := 1" to get past the second failure to build.
I don't have much time to devote to it tonight, I'd be curious how it would go on a multilib system, is this defaulted for both sets of libraries?
I just gave it a try, using the modified SlackBuild provided by ponce here is where I am at. https://pastebin.com/RrnzXA88
So far, my progress. Included --disable-vmmraw in the ./config. Had to utilize the xml.patch from the 7.0 VBox slackbuild. Had to utilize "VBOX_WITH_RAW_MODE := 1" to get past the second failure to build.
I don't have much time to devote to it tonight, I'd be curious how it would go on a multilib system, is this defaulted for both sets of libraries?
I got it to compile, I had to use the xml patch and a gcc 13 patch located here. I used these build options
The post #526 was helpful. It just works out of the box on Slackware64 15.0. Was able to produce a .vdi image with "enable efi" working network and three partitions efi,swap,linuxfilesystem.
The virtual-box slack-build may have some upsides but the VirtualBox-7.0.14-161095-Linux_amd64.run method is straightforward.
Attempting to replace a freebsd droplet on digital ocean by a Slackware one. w-i-p.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
