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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
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) 
