SlackwareThis Forum is for the discussion of Slackware Linux.
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.
my fstab before running this is slightly different, I have my fstab setup the way ATI wants it
tmpfs /dev/shm tmpfs defaults 0 0
maybe qemu wants me to leave out the left-hand side most 'tmpfs' and leave it as blanK?
As long as there is a mounted tmpfs it's OK for the kqemu kernel module and it will use it. When such is unavailable and you do start QEMU with the kqemu kernel module loaded, you will receive a warning about kqemu not being able to use a memory filesystem and reverting to the MUCH slower /tmp directory to create it's virtual machine's RAM image.
i tried qemu too and then after i see nykey post about vmware i tried that too and got network unlike in qemu. my only problem is the sound. i don't have /dev/dsp . why is that ? i have latest kernel 18.104.22.168 compiled by hand using the config from Pat's 22.214.171.124 + some modifications. i have latest alsa-1.0.11. how can i activate /dev/dsp ? after i add Sound Device at the drop-down list i only have Autodetect, no /dev/dsp and when i start virtual server i get error that no sound device exists. sound is working on the host (slackware). any ideeas please ?
I'd just like to give you some feedback from someone who never did this before, and new to linux Eric.
There just things that went thru my head, questions concerns that you may ( or may not) want to touch on in the wiki.
Nothing is major here as I got thru it in notime, except for my stupidity on the root account owning my isos...omg.
As if you did not have enough to do right, lol.
1. I get this echo'd in console loading up qemu:
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
So I guess I'll write a sudo script to let me do this in your launch script.
2. Maybe telling people, (as stupid as this sounds) how to properly close the guest host. for instance, I wasn't sure if it were ok to just "x" out of slackware as guest, or tell the guest/slackware to shutdown.
3. My first time running qemu it went full screen, for whatever reason I dont know. So i just went into qmenu and hit help and was fine, but may be worth mentioning.
4. How to verify kqemu is doing something? Is the fact that it is modprobed mean it's working for me? Anything like "kqemu --status" kind of like what we have in "wpa_cli --status" , etc?
5. When I first made my slackware guest, I realized I wanted the image to sit on a different partition as it's permanent home. I was not sure if I could move it about on the hard drive, or to a separate physical drive. simple copy/paste worked for me.
6. maybe mention about my question above about changing size of the guest if need be down the road.
7. this may be more confusing, but i was not sure if I started by using cd1 of slackware to start the installer, and then later use an "iso" for cd2 on the install. the fact that you can mix/match. for me I had disc one of slackware, but no iso for it. trial and error prevailed, but was a question.
8. Maybe tell people that they can use a program like alcohol to make an iso of slackware cd's if they are in windows, or can use k3b in slackware and that k3b is in /extra.
I didnt know how to make an iso in linux to be honest. I tried my nero in windows that came with my burner...but was then stuck with an 'nrg' file, which that didnt work either. I tried nrg2iso but get segmenation faults. Probably this is beyond the scope but thought I'd mention it.
9 the ctrl+alt work for me only with the ctrl+alt keys on the left side of my keyboard. the ctrl+alt keys on the right side of my keyboard don't do anything. maybe worth mentioning. I'm lefty so I went to the ctrl+alt on my right side of my keyboard to get to qmenu and was confused at first.
10. it appears the qemu is kernel independant, and kqemu is kernel dependent so upgrades to kernel will require rebuild of the kqemu. something like dont forget to remake a new kqemu if you upgrade your kernel.
11. you mention using a group for qemu. personally, I dont know how to do that. so i'm gonna go read my slackware book and find out how to.
hope this helps, and again thank you for the build script and wiki.
A truckload of notes there! I think I can try and address some in the Wiki page. I'm glad you solved most of those for yourself though (you're not the newbie you like to pose as you know :-) )
You can have a look at the rc script I wrote for the case you want to have a better networking experience than the default usermode networking (which is fine, too, if you have no intention of connecting TO the guest inside the Virtual Machine, and instead are satisfied with just connecting out FROM the guest OS): http://www.slackware.com/~alien/slac.../rc.vdenetwork
It is part of the Slackware package for VDE which I also mention in my Wiki page. Maybe you can still pick out a couple of worthwhile morsels there even if you don't want to use VDE to provide the networking glue for QEMU.
Presently I dont get any network on the slackware guest, but, that's no big deal as I plan to do the same thing that you do, make packages, kernels, etc in the virtual slackware. Actually, that's probably better that I dont have networking on the slackware now that I think of it.
one last thing regaring the wiki: when i was putting slackware in, I made a guess, to add a swap partition and another partition for the slackware's "/" and when it came to the lilo, telling slackware to use the master boot record option too. I was not sure what to do but it worked out well.
Ok, so I've tested VMware, it is quite impressive. I actually managed to get my Video Card up to 64MB (maximum supported is 128MB but I tought not to push the note for now, but will try that too). Alien, I would like still to get the hold of QEMU too, mostly to compare these two, but first I want to know, is it possible with QEMU to enlarge the Video Card memory ? Cause in QEMU the default memory for the Video Card is 4MB. With 64/128 in VMware I'm actually able to play games, and performance is quite acceptable.
when it came to the lilo, telling slackware to use the master boot record option too. I was not sure what to do but it worked out well.
The Guest OS inside QEMU runs in an emulated hardware environment. That includes emulated disks. The MBR to the Guest is just another sector in the virtual disk image file that you prepared for QEMU. Your Guest OS will not be able to address any physical hardware components directly (apart from USB devices for which such a translation from guest to host is made). You will not be able to harm your host computer (nor it's host OS) by doing weird things in the Guest, unless of course you hit a bug in QEMU :-)
yeah, I know it's not meant for games, and thats not my intention of using it, but still, at 4MB I have such a lousy resolution and it moves like crap because of the Video Card. I actually keep VMware at 32MB and it's working just fine (btw I tried 128MB, and it worked too)... and in VMware Direct3D is available too when adding video ram. But, still no answer... can I do the same in QEMU ? "Add" more RAM to the video card ?