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.
Hi, i've pbs with this simple cli and the boot process stopped with a kernel panic! KVM is enable on my host (core2duo E8500), modules (kvm kvm_intel) loaded and got that message in dmesg:
Code:
vcpu0, guest rIP: 0xffffffff8258069a disabled perfctr wrmsr: 0xc2 data 0xffff
Reading your post it is not clear to me where the kernel panic is happening. Is it happening in your host or guest machine(using Qemu)?
In case the kernel panic is happening using Qemu (guest machine), paste the full command that you are using. Also this may be useful:
Sometimes if not enough ram is being used a kernel panic happens.
Add more ram using the -m switch, ie: -m 1G (to use 1GB of RAM for the virtual machine). If the -m switch is not included only 128MB are used by default.
Hi slac, you're 100% right! Kernel panic is happening in guest machine (qemu), the -m 1G option solved my pb I'm not familiar in booting big iso with qemu but playing and installing old Slackware distros within qemu-2.8 Still installed slackware-pre-1.0-beta and slackware-1.01 on a disk image with (pre-created) floppy images and using the doinstall (installation program)
@dodoLQ, here's what I use. Gives an idea of the whole host of useful options. I set up a BASE image, then a WIP copy-on-write image from that. if somethings goes wrong, I just need to create a clean WIP! https://www.linuxgalaxy.org/files/ut...2_zenityfix.sh
Also, 1GB RAM is a bit thin for 14.2. I'd go 2G for CLI and 4GB to run a DE. But then, I have 32GB on the host....
To increase the usable RAM one may try swapinzram. Sorry I was too lazy to make a standard SlackBuild but just running package-swapinzram.sh should be enough.
Unfortunately this doesn't work during installation as we have to load the kernel and initrd first, and the initrd can be big.
Last edited by Didier Spaier; 04-16-2021 at 05:50 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.