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.
It takes a lot of time to compile all the targets even here with a core i7, and additionally the resulting package is very huge. If you just want to build Android-x86 I think you don't need all the targets.
Qemu compiled and is now installed. I also just installed "aqemu". Though it uses qt5. I may go back to virt-manager. I need to download Android-x86 and test it. Wish me luck.
Actually it's a mix -- 60% Slackware/40% Salix. Since Salix is inactive, I am using more and more Slackware packages over time. Using slapt-get/slapt-src (with Slackware repositories).
Qemu did install. Then I followed this tutorial: kvm_libvirt
Used both Virsh & Virt-manager. But I don't understand what the hell I'm doing.
Virt-manager does not allow me to use "localhost", instead it forces me to use "Qemu-KVM" which is not available to use. So I am confused.
Last edited by chaz_bro1972; 01-23-2020 at 01:20 PM.
Reason: new Problems with Qemu & Virt-Manager
Actually it's a mix -- 60% Slackware/40% Salix. Since Salix is inactive, I am using more and more Slackware packages over time. Using slapt-get/slapt-src (with Slackware repositories).
Qemu did install. Then I followed this tutorial: kvm_libvirt
Used both Virsh & Virt-manager. But I don't understand what the hell I'm doing.
Virt-manager does not allow me to use "localhost", instead it forces me to use "Qemu-KVM" which is not available to use. So I am confused.
With a processor without kvm support this can't work I guess.
Just use Qemu commands or if you prefer a GUI install aqemu. There is no point using libvirt to manage just one VM anyway.
Last edited by Didier Spaier; 01-24-2020 at 03:41 AM.
I already did install QT5 (a long time ago), so installing aqemu wasn't so hard. I mentioned I already got it earlier. But now I need to figure out how to use aqemu + install the new Android-x86 (iso) I already downloaded.
aqemu can be problematic with qemu-4.x since is hasn't received for many years. Some of qemu command line options have changed quite a bit. qemu has a simple built in GTK GUI.
The x86 and arm targets are built by defualt. For Android-x86 you do not need to compile with TARGETS=all
Even on a CPU with kvm, you can still leave '-enable-kvm' in the configure script. KVM is enabled/disabled when you run qemu. The 'qemu-kvm' is just a symlink to 'qemu-system-$ARCH, where $ARCH is either x86_64 or x86 depending on which Slackware you did the build.
Since you are trying to run android-x86 on a x86 CPU, 'cpu host' should work, otherwise 'qemu-kvm -cpu help' to find one. "-smp n' selects 'n' host CPUs so adjut as needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.