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.
hello i am running slackware 9.1 with the 2.4.26 kernel...
i installed the VMware virtual machine console but when i start it all the options in the menu are greyed out....there are some options available but only stuff in the "view" menu and couple others....
Which version of vmware? And did you compile and load the vmmon module successfully? In the past I've got to the vmware intro screen, but not actually been able to do anything with any virtual machines, because the vmmon module had either failed to compile (although I had still been able to complete the vmware installation), or because I hadn't loaded it with "/etc/rc.d/vmware start".
I can confirm that VMWare does run under Slackware, although it took a little finagling to get it to install correctly. After "installing" the software, you will have to run the "vmware-config.pl" file in order for the modules that Kovacs mentioned to operate correctly. The only trick to getting this configuration script to execute correctly was that I had to create the directories rcX.d (where X is between 0 and 6) under /etc/rc.d. Once the script ran correctly, I checked the contents of these directories and noticed that VMWare put files into several of these folders. I just left them there, started up VMWare and poof, it suddenly was working correctly.
If you can, I would avoid gsx server thing and get the latest workstation 4.5 version. The 4.5 workstation version works great with slack and 2.6, but I've heard of other people having probs with the gsx server version.
You install vmware tools onve your guest OS is up and running, their should be an option to install it under one of the vmware menus.
I use the Linux version of Vmware workstation 4.0.5 and use Slackware 9.1 with the 2.4.22 kernel as my host operating system. Before installing it I was fortunate enough to find a website that gives detailed intructions for installing Vmware under Slackware. It discusses the special tricks for getting it to work under Slackware. It sounds like you have got it working already but here is the website anyway:
My guest operating systems include Windows 2000, Windows XP, Windows NT 4.0, Red Hat 9, Red Hat 8, Red Hat 7.3 and PC DOS 2000. All of my guest operating systems have been installed on virtual disks instead of on a raw physical harddisk partition so I only run them from within the virtual machine. I created a virtual disk and a virtual machine for each version of Windows and then installed Windows inside each virtual machine.
Looking at the manual, I sounds like it is possible to run Windows inside a virtual machine at times and then at other times boot directly into Windows. Is what you want to do? On page 149 of the manual it does seem to describe how to do that with some versions of Windows (but not Windows XP). It says this:
"The general approach for resolving these issues is to set up profiles for each of the two operating environments - the virtual machine and the physical computer. You can choose the appropriate profile when you start the operating system."
The hardware profiles they are refering to is a rarely used feature of Windows that I have never used. Using two different hardware profiles under Windows is needed because the emulated hardware that Windows sees as a guest inside the virtual machine is different than what it would see when run on the real hardware. I have never tried to do that or any of the other stuff so I hope I understand what they are saying. The Vmware manual recommeds against running Windows XP from a raw physical partition. I hope I did not misunderstand what you ment by "get it to start my windows boot".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.