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.
Hello to all in this thread! I do not recall participating in this discussion previously, but I have followed it for some time - and thanks for all the helpful info along the way!
Quote:
Originally Posted by Paulo2
Which thing, Master Control Program?
I hope that the systemd absence won't be considered a bug for VirtualBox
Indeed...
I have only become a full time user of VBox during the past 2-3 years, although I have used it as a build environment for much longer. But I have now incorporated it into my daily workflow in multiple ways and would be very disappointed and inconvenienced if it actually did develop into an unmentionable-dependent beastie.
Does anyone have any real sense, expectation or inside knowledge that this is likely to happen, beyond the installer generated messages posted above?
It does give me pause...
Last edited by astrogeek; 09-02-2022 at 03:51 PM.
Reason: ptoys
I am having problems with virtualbox, installed from bin:
1) it fails to start, unless I disable check for update (https://slackalaxy.com/2022/06/09/vi...ck-for-update/)
2) building some stuff like Ugene from SBo always fails (no idea how to fix this, I have an Intel CPU)
3) shared folder between host and guest results in corrupted files in guest (no idea how to fix this either)
that's it, I'm done with this crap. Setting up slackware installation in chroot environment to test my SlackBuilds
The most recent stable release, VirtualBox-6.1.38-153438-Linux_amd64.run
installs and runs as it should with both the 5.19.y and 6.0-rcx kernels.
I tried it with kernel 5.15.63 and it got hung up on the systemctrl command. I removed VirtualBox-6.1.38 and reinstalled 6.1.34 so it is back to its unsatisfactory working condition. I don't know if it is Windows 10 or VirtualBox, but I realize it is actually not important enough for me to spend time on it. If it just worked, I would feel differently. How well does Qemu work?
I tried it with kernel 5.15.63 and it got hung up on the systemctrl command. I removed VirtualBox-6.1.38 and reinstalled 6.1.34 so it is back to its unsatisfactory working condition. I don't know if it is Windows 10 or VirtualBox, but I realize it is actually not important enough for me to spend time on it. If it just worked, I would feel differently. How well does Qemu work?
VirtualBox is a heavily modified variant of an ancient version of qemu. Qemu-7.1.0 must have overtaken VirtualBox by a few light-years with both functionality and performance. Qemu-5.2.0, which I'm using for production, is already more fast and stable than VirtualBox-6.1.38. It took me a few hours to figure out the right command line options to run qemu comfortably, but that's all.
What do you use to connect via IP the multiple virtual images running in quemu?
Not to mention the optional access through the LAN out to 0.0.0.0/0
There are different ways to configure network for qemu:
Socket
Allows multiple virtual machines on the same host to connect to each other on a virtual network.
VDE
Is a way to create virtual network switches to which virtual machines and physical machines can connect. This also allows virtual switches and virtual machines on different hosts to connect to each other.
TAP
Allows a virtual machine to access the network through a network inteface on the host.
User
Creates a virtual network for the virtual machine which might contain things like a virtual DHCP server, DNS server Samba server.
I mostly use the User network, that can be configured without root privileges on the host. The virtual network seems to be behind a NAT firewall and allows the guest to reach resources on the host network. However, the guest will not be able to use privileged ports and for that reason not be able to do NFS mounts from the host network. You can start a samba server on the host with your own privileges and let the guest access that samba server from within the virtual network.
To use TAP you need root privileges on the host machine. Then the guest will get full access to the host network and will be able to do things like mounting NFS.
tl;dr: I have upgraded to this one from 6.1.38 release, and so far it was *much* more stable.
Long version:
No crash, at all, so far. No crash of the GUI, so far, not even in KDE sessions, whereas with previous versions the GUI crashed reliably after a few minutes or actions, while VBox as such continued to consume quite a bit of CPU time and RAM. The crashes were really bad. In fact, my KDE desktop became unresponsive, file system became read-only and the system refused to execute reboot and shutdown commands (in fact, it didn't find them, at all, sometimes). I was always thinking of problems with my harddisks, already.
BTW, the 6.1.39 test build didn't fix those problems, here. But the 7.x development preview does, as it seems, although I just installed it recently. So, fingers crossed that things don't get worse, or that my good experience with that version wasn't just random good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.