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.
Thanks Old_Fogie. I have a DVD iso for Beta2. I just wanted to see what all the hype was about. I was hoping to be able to do a virtual install. I just can't seem to find the motivation to clear 20 GB of harddisk space required for the install. Update: My WinXP Pro QEMU install on my Slackware desktop did install sucessfully. Now, if only I knew why I did it...
Side note: I realized why my qemu file didnt work when I moved it to fat and then back. I went thru my console and found that I tried running the qcow file for my slackware host and not the img directly. I didnt realize that if you dump your hard drive, or move it, the qcow is no good. Oh well, learn as I go.
I don't want to turn this thread into a M$ basher. They made the Beta2 and will make RC1 available for free for testers, so they can get feedback from "real world" users. It is time limited and it expires next July. I was just curious. I didn't want to commit any actual harddisk space to a Vista install if I can test it on a virtual machine. I agree with your assertions as stated above.
I am as much an advocate of Open Source as anyone (except maybe Richard Stallman). I run Slackware current on my Desktop and Mepis on my laptop (what can I say, Mepis was installed and funcitoning in 8 minutes with very little help from me.) I don't normally boot into a M$ windows environment if I can avoid doing so. However, like most consumers, I bought my first 2 or 3 computers with pre-installed operating systems. That was before I discovered the wonderful world of open source software. During my digital infancy, I found a few commercial programs that have no equal outside of a M$ windows environment. (Although a lot of development progress has been made over last few years.)
Since M$ was allowing testers to download a "nearly" functioning version of their next BE ALL to END ALL operating system, I thought I would give it ago. I am no fan of XP because I think it has done much to dumb-down the average computer user. I still run Win2k w/SP2 on several machines at work. Thanks for the link, I'll check it out. Thanks to all who have posted such valuable information about QEMU in this thread. Please forgive my ramblings.
Apparently I should not post after a long day, made 2 errors.
1. Hey sorry about the URL, I thought I checked/previewed it before posting it. I'll pay greater attention to it.
2. R_Shackleford : Sorry if my post there came off as a poke at you for your trying MS. It wasnt meant to be like that all I truly mean it. What I should have said more thoroughly (as word's don't allways get to the screen as I mean) is that I don't blame you for wanting to try MS to see what the hype is about like you said. That's why I actually went over to that site to see if they had any info for you to see if I could help you get it going. I should have also said it was a shame it didnt work for you, as that is a benefit of the virtualization in pc's and that I don't blame you for not wanting to resize/move partitions, etc as there is always a risk involved. When I posted my list about MS it was really a qeustioning list, tho again I didnt type it out as what was in my head. I've been like many readin about the the new vista. I'm just hard pressedd to find feature benefit that would be compelling, even for non Lin/foss people is all. Many people have those app's now. It actually should have been writen with question marks. Tho the rant of where is service pack 3 yea that remains a small rant, I did mean that. But that's because it takes soooo long to update a windows xp box these days, I actually do want it 2b honest. But I will make a more concerted effort on my words, thanks for bearing with me.
No offense taken, none intended. No harm done. It is so very difficult to convey tongue-in-cheek humor sometimes. I generally think most folks are good natured. I'm thick-skinned and I don't look for ways to be offended. I did want you to know where I was coming from. I appreciate you taking the time to help find info for me. I am going to try to find some disk space and actually try this virtual vista, instead of just talking about it. Not having tried to install vista "normally" I don't know what to expect. A QEMU install should make it even more interesting.
On your wiki you discuss the upcoming versions of the cvs/kqemu here:
This concludes the alterations needed for a performance boost of your Virtual Machines inside QEMU. As I said earlier, running qemu is really simple - it is a single binary with a lot of optional commandline parameters that customize the virtual machine it will setup for use. QEMU will use the kqemu accelerator if it finds the kernel module loaded in memory (and if it’s built with support for kqemu). The newer versions of QEMU and kqemu (at the time of writing, it’s only available in the CVS repository of QEMU, but it will be released as QEMU 0.8.1) provide an additional layer of acceleration called kernel-kqemu. In this acceleration mode, the Guest kernel processes will also be accelerated as opposed to the “regular” functionality of kqemu to only accelerate the Guest’s user processes. You do need to supply an explicit parameter to the qemu commandline:
qemu -kernel-kqemu <other parameters>
Just wondering, Do you know of any neat tricks that are used for kqemu?
Right now I'm simply launching my guest OS's just like you have their in the start up script for example, but didn't know if you might have any special tricks up your sleeve
Do you know of any neat tricks that are used for kqemu?
Well, as long as your fstab has a line similar to
none /dev/shm tmpfs defaults 0 0
and you've installed kqemu and loaded the kernel module, there is not much you can further tweak or tune.
If you run qemu-0.8.1 or later with the "-kernel-kqemu" parameter rou're running QEMU as fast as it can currently run (note that some old OS-es will actually run slower as a guest in QEMU with kernel virtualization acceleration).
To see if kqemu is enabled and working correctly, use the following command in the QEMU monitor:
Try that for instance after having started QEMU with, and without, the "-kernel-qemu" command, or even after starting QEMU with the "-no-kqemu" command.
Earlier this week I upgraded to the most recent testing kernel & rebuilt the kqemu module. (Thanks for the script, Eric.) When I added the "modprobe kqemu" line to rc.modules, I inadvertently commented it out. It took me three or four starts/restarts of QEMU to remember to look at the .err file & find out what was happening, but I did learn that I don't want to run Win2K or Slack in QEMU without the accelerator.
when I run any guest OS with "-kernel-qemu" in the commandline / or my startup script I find the guest OS's fly...however, I get crazy program crashes in my guest OS at times, and I can't duplicate them. I suspect it's becuase I'm too overclocked.
If I just have the module kqemu loading with the pc like Alien Bob's script put in there for us, and the module running in the background I'm fine. But the "-kernel-qemu" so far is not working for me, but wow does it fly. Any of you gent's experience that at all, or is it because it does not like my over-clocking ?
I am having no problems at all & I am running both Win2K & Slack-current in QEMU. I was having the "mouse hits invisible wall" problem, but the upgrade fixed that. Both systems are as stable as a rock & quick as a bunny.
however, I get crazy program crashes in my guest OS at times, and I can't duplicate them.
Bad RAM perhaps, or the overclocking? Fact is, I use QEMU a lot and no strange Guest software crashes.
I had QEMU die on me twice, and then it disappears in a split-second, taking the Guest OS with it... no clue as to what bug I hit upon.
OK I wouldn't doubt it to be the memory timings or overclock. It figures I took out Mepis so now I don't have memtest and linuxpackages and Alien Bob dont either OK I go make one I guess and see. Thanks for the feedback.