LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Slackware (http://www.linuxquestions.org/questions/forumdisplay.php?f=14)
-   -   virtual windows under Slackware64? (http://www.linuxquestions.org/questions/showthread.php?t=4175413812)

tramni1980 06-28-2012 05:45 AM

virtual windows under Slackware64?
 
Dear Slackers,
I need to run Windows 7 virtualy under Slackware64. What are my options, has someone
already implemented that, is there a handy step-by-step how to somewhere?

wildwizard 06-28-2012 05:55 AM

https://www.virtualbox.org/

tronayne 06-28-2012 09:14 AM

As suggested by @wildwizard, VirtualBox may be your best bet.

Go to https://www.virtualbox.org/wiki/Downloads. You're going to be downloading two files, both for VirtualBox 4.1.18.

On this page, you want VirtualBox 4.1.18 Oracle VM VirtualBox Extension Pack, click the link for all platforms to download it.

Above the Extension Pack is a list of binaries, click the link VirtualBox 4.1.18 for Linux Hosts then on the page that opens scan down the list to All Distributions and select the link AMD64; that file is roughly 75M.

Before you go any further, consider where you want your virtual machine installed (not the VirtualBox software -- that gets installed in /opt) -- the Win7 virtual machine. VirtualBox defaults to install virtual machines in your home directory; you will need to allocate at least 30GB to Win7 to make it useable (more likely 50GB or more depending upon what you're going to do with it -- Win7 is a disk hog).

If you've got enough room for 30-50G in /home that's OK; however, you may want to use a spare disk drive or an unused disk partition for your virtual machine(s). You don't need to do that to install VirtualBox, but you will have to decide before you install Win7.

You need to add a group, vboxusers and you need to add that group to your user ID, that's done below.

You can install VirtualBox now:
Code:

Log in as root (or use su - or sudo)
groupadd vboxusers
usermod -a -G vboxusers your-login-name
cd wherever your download files are
sh VirtualBox-4.1.18-78361-Linux_amd64.run
log out from root if you logged in as root

That installs it.

The manual is included in the downloaded file, it's at /opt/VirtualBox/UserManual.pdf (it's also on-line at the VirtualBox web site). Be a Real Good Idea to crack it open and read the Installation chapter just to get familiar with what's going below here.

If you're using KDE, click the KDE menu, then System and look for Oracle VM VirtualBox, click that to start VirtualBox.

That opens a window, Oracle VM VirtualBox Manage.

In that window, click on File, Preferences. The first display is General that shows the Default Machine Folder; the first part of that will be in your home directory. If you've got enough disk space in /home to install Win7, don't fiddle with it; otherwise, choose the absolute path to where you've got enough disk space (you may need to create a directory named virtual somewhere in your file system before you do this and you will need to modify permissions to it.

For example, I have my virtual machines in /var/lib/virtual (virtual is a mounted file system). The entry in /etc/fstab looks like this:
Code:

/dev/sda8        /var/lib/virtual ext4        defaults        1  2
That's a lot of fooling around but you may need to do it if you don't have space in /home. In /var/lib,
Code:

drwxrwxr-x  5 root      vboxusers 4096 Mar 14  2011 virtual/
That is,
Code:

su -
chmod 775 /var/lib/virtual
chgrp vboxusers /var/lib/virtual

You do not need to put your virtual machines in /var/lib, they can be in your home directory (if you've got space in /home that is), they can be in /usr/local or wherever you've got space.

Next thing is to install the Extension Pack that you downloaded. If the Manage is not still open, open it again, select File then Preferences then Extensions.

Click the diamond-shaped icon with an orange triangle on it to the top right of the Action-Name-Version window. That opens a window titled Select an extension package file, navigate to where you downloaded the extension pack -- it's named Oracle_VM_VirtualBox_Extension_Pack-4.1.18-78361.vbox-extpack. Double-click it (open it) and get it installed.

After you've done all that, you're ready to install your Win7 guest (and wait for almost 200 critical updates; don't you just love Windows?). You don't need to do any partitioning for Win7, that'll get done as you go, but you will need to set some things, the name of the virtual machine (Win7 is good) and the amount of RAM allocated to the virtual machine -- if you've got 4G RAM, let Win7 have half of that but no more. If you've got 2G RAM, give it half and so on. Read the manual pages for recommendations for other settings, accepting the defaults in most cases but refer to the manual and the little hints that pop up when you slide the cursor over a selection.

After you've done all that, started Win7, let all the critical updates download and install, register the thing, all that there is one final step: you need to install the Guest Additions (they're included with the download).

You must install the Guest Additions in safe mode; i.e., boot Win7, hold down f8 and select safe mofe. You can select "Install Guest Additions" from the Devices drop down when Win7 is running (sometimes I've had that not work) or select Computer then double click on CD Drive D:VirtualBox Guest Additions -- I've had more luck with that, YMMV. Then reboot and you ought to be good.

Hope this helps some.

dlachausse 06-28-2012 02:24 PM

VirtualBox is also available from http://slackbuilds.org/. Note that you will need a multilib setup for your Slackware64 and a few other dependencies which are already part of SlackBuilds.org. I also recommend SBoPkg for working with SlackBuilds.org.

ReaperX7 06-28-2012 02:36 PM

The Oracle Proprietary package didn't require the multilib setup last time I used it like the Open Source edition did. Plus the OSE at SlackBuilds doesn't have support for USB 2.0 devices and other advanced driver features as the Oracle version.

Both are free however, so its just a pick and choose issue. Free Proprietary or Free open source. If you don't need USB 2.0 devices supported just stick to the OSE version.

tramni1980 06-29-2012 01:47 AM

Quote:

Originally Posted by dlachausse (Post 4714366)
VirtualBox is also available from http://slackbuilds.org/. Note that you will need a multilib setup for your Slackware64 and a few other dependencies which are already part of SlackBuilds.org. I also recommend SBoPkg for working with SlackBuilds.org.

Just because of that I am asking. I saw virtualbox in salckbuilds.org, but it requires multilib, which I do not want. I found xen in slackbuilds, which is can be compiled from sources. Has anyone had success configuring xen in Slackware64?

zakame 06-29-2012 02:05 AM

The other option is to go libvirt with a QEMU/KVM backend. qemu-kvm and libvirt are already available in slackbuilds.org and they're pretty straightforward to install, no need for multilib. For creating the VM itself, look at virtinst and virt-viewer slackbuilds for lightweight VM provisioning.

ponce 06-29-2012 02:42 AM

Kvm doesn't have a complete support for windows 7 guests (I was testing it in these days, it gets stuck at boot): things will probably get better with kernel 3.6.

Alien Bob 06-29-2012 03:45 AM

Quote:

Originally Posted by ponce (Post 4714771)
Kvm doesn't have a complete support for windows 7 guests (I was testing it in these days, it gets stuck at boot): things will probably get better with kernel 3.6.

Oh? I have been running a Windows 7 guest in qemu-kvm for over a year now. No issues with installing from an ISO, no issues running it.

Eric

ponce 06-29-2012 04:11 AM

here I seem to have hit this and in my comment I was referring to this: as it's ok for you, maybe it depends on something specific of my setup/cpu, or it can be also I got it all wrong :D (in this case, sorry :) )

Alien Bob 06-29-2012 04:35 AM

Quote:

Originally Posted by ponce (Post 4714827)
here I seem to have hit this and in my comment I was referring to this: as it's ok for you, maybe it depends on something specific of my setup/cpu, or it can be also I got it all wrong :D (in this case, sorry :) )

Perhaps it is because I only buy AMD CPU's for my virtualizing hosts, no Intel ;-)

Eric

chrisretusn 06-29-2012 05:00 AM

VirtualBox works just fine on Slackware64. I have been using it for quite sometime without AlienBOB's multilib. I have several virtual machines, including Window XP, Windows 7 and Windows 8.

The simplest and easiest method and the one I use, is to use VirtualBox's installer.

You can get the installer here. Linux_Downloads – Oracle VM VirtualBox. First thing to do on that page is download the "VirtualBox 4.1.18 Oracle VM VirtualBox Extension Pack" Next on that page look for "All distributions i386 | AMD64" and download either the i386 (32-bit) or the AMD66 (64-bit) file. File names VirtualBox-4.1.18-78361-Linux_x86.run or VirtualBox-4.1.18-78361-Linux_amd64.run respectively. I of course use the 64-bit one, multilib is not required. I do not have that installed.

The installer takes care of almost everything, just run it as root. It will install to /opt/VirtualBox/

When it is finished, add your self to the vboxusers group (as root of course).

Code:

~# usermod -a -G vboxusers LOGIN
If you are doing all of the root stuff from a terminal window in your regular account, I would recommend logging out and back in again to ensure that adding your account to the vboxusers group takes effect.

When you first start VirtualBox, from the File menu, select Preferences, then Extensions and add the extension pack.

Next thing I "recommend" is to change the Default Machine Folder (File, Preferences, General) from the default "VirtualBox VMs" to VirtualBoxVMs. I am not a fan of spaces in file, directory names, it can and does cause problems. Up to you though, as I said it is a recommendation.

With the Preferences window still open select Extensions and install the Extension Pack you downloaded.

Now are ready to install your first VM. Once installed be sure to install the Guest Additions.

One thing I should mention, as it comes up from time to time, if the kernel gets upgrade in Slacware you will have to reinstall VirtualBox.

tronayne 06-29-2012 07:14 AM

I might note that I run 64-bit VirtualBox on 64-bit Slackware (stable), no Multilib, and have installed and used XP, 32-bit Win7 and 64-bit Win7. XP is now gone as is 32-bit Win7; 64-bit Win7 works just fine, thank you. I'm using QuickBooks daily with no problems whatsoever. The only problem I've had was with this year's TurboTax (so have lots of other folks -- it won't run -- but it seems to be associated with Win7 .NET stuff last I heard). I've installed Adobe Reader in Win7, works just fine (no need for Multilib on the Slackware side).

I have tried the SBo build (well, two years ago) which did not support USB and other handy stuff and I stick with the binary download (the *.run one) which, as far as I can tell, fully supports everything I need to do to get stuff in or out of Win7 (like flash drives and DVDs). Sound works (using the OSS audio driver). Solitaire and Spider work with all the flashy card dealing and sound effects (thanks to the Guest Additions).

Everything works if you let it.

zsd 07-26-2012 01:19 PM

Quote:

Originally Posted by chrisretusn (Post 4714860)

One thing I should mention, as it comes up from time to time, if the kernel gets upgrade in Slacware you will have to reinstall VirtualBox.

That's not true, you only need to rebuild the kernel modules by running
/etc/rc.d/rc.vboxdrv setup
as root.

Cheers.

BlackRider 07-26-2012 01:36 PM

It has been roughly a year since I last booted my virtual Windows, but...

I think most options have already been mentioned. VirtualBox OSE is good enough for most simple software tasks. Proprietary VirtualBox has USB support, but last time I tried it was pretty lame and slow.

Standalone Qemu is plain slow since Kqemu modules were dropped. KVM is nice, but you need a processor able to handle it, so if you have a crappy processor you are out of luck.

Being a FOSS sectarian, I have forgotten about Oracle VirtualBox. USB drives can be "cheated" in the OSE version, while printers and such have always worked sub-optimally. Qemu is too slow and my processor won't run KVM. That leaves me with VirtualBox OSE.

If you want a quality experience, just run a true OS instead of a virtual one, seriously. Or do as I do and use no Windows at all :-)


All times are GMT -5. The time now is 08:01 AM.