Is it possible to install Slackware 9.0 on WMware 4?
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.
As a follow-up to this question, I was able to install SW9.0 on VMWare 4.0.2; however, I was not able to boot off the VM --initially. I had to boot off the SW9.0 install CD and at 'boot:' type the following:
scsi.s root=/dev/sda2 noinitrd ro
After that, everything boots up and I can go about my business. Being new to Linux, I don't know where to begin... anyone?
Well, I don't know where to begin to tell you where to begin. Broad generic answer is read a lot of documentation and come to undersand your basic helps and filesystem and tools. If you had some more specific question, like 'how do I...' maybe we could help more. And maybe your background - if you know DOS or are used to working with a DOS box, the Linux CLI will be a lot easier for you than if not. If you're a Windows guru, understanding certain basic stuff will be applicable or easily translated from one system to the next. And if you don't know anything, you won't have to unlearn anything. Advantages to both. But we can't tell you much without maybe insulting you or flying over your head without more knowledge.
Safest answer is type 'mc' at the command line since it's an easy way to flip around through the directory structure just get an overview of what's on your system, maybe combined with reading about the filesystem hierarchy so that you know what you're looking at.
The big problem with installing Slackware, or any Linux for that matter, on VMWare is that, by default, VMWare sets the VM up to use SCSI drives by default when you select "Linux" as the guest OS. Some Linux' handle this alright because their installation kernels are set up to detect SCSI cards and drives and will install just fine but as Slack doesn't have SCSI support built into it's kernel by default (it uses the scsi.s kernel for that as jbrashear pointed out) it can get problematic.
It is possible to install Slackware on a VMWare default Linux VM just use the scsi kernel to install it and when you get to the step where Slack prompts you to install a kernel make absolutely sure the scsi kernel gets copied to the hard disk (From memory you need to select "use the installation boot disks kernel" and then select the scsi one) otherwise your system won't boot properly.
An easier method by far is to tell VMWare that you're installing a Windows of some sort (so that it'll put IDE drives in the VM) and then just install Slackware anyway. That way you'll be able to use the default bare.i kernel and won't have any of the weird module behaviour that can come from using a different kernel.
I type the command scsi.s root=/dev/sda2 noinitrd ro
Then This came out at the end
VFS:Cannot open root device "sda2" or 8:02
Please append a correct "root="boot option
Kernel panic : Unable to mount root fs on 8:02
Originally posted by jbrashear I may have spoken too soon -- I don't see, "From memory you need to select 'use the installation boot disks kernel'". I get to "INSTALL LINUX KERNEL" and I have these choices:
bootdisk, cdrom, floppy, skip (use the default /boot/vmlinuz)
Any ideas? Again, I am using SW9.0...
Obviously, my memory wasn't as good as I thought it was
Anyway, checking my Slackware VM, you need to pick cdrom and then, from the list, pick the scsi.s kernel. That should get you up and running.
Sounds like you got the install worked out. But for those that want to use the bare.i kernel, I have found that if you change the scsi drive to an ide drive it works wonderfully. That way there is no problem with picking the wrong kernel at install time or at least it minimizes problems (I think )