LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   current on virtualbox (http://www.linuxquestions.org/questions/slackware-14/current-on-virtualbox-4175420422/)

mcnalu 08-05-2012 02:49 AM

current on virtualbox
 
I created a DVD iso (using mirror_slackware_current from alien bob) and booted up a 1GB virtual machine in virtual box OSE 4.1.14 and it halted almost immediately due to lack of PAE. I turned that on for the VM (via the GUI) and tried again. Now starting it failed later in the boot and with a message about directly accessing the hardware. I tried a few more times, without changing anything, and then it booted up fine and now the installer is trundling along just fine.

Anyone else encountered similar?

UPDATE: Installed fine, but same problem when booting off the (virtual) hard disk. Error message is:
"atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying access [sic] hardware directly."

UPDATE2: Fiddling with virtual hardware settings didn't get me anywhere.

tronayne 08-05-2012 09:05 AM

Did you install the extension pack (in VirtualBox before you install a virtual machine)? Did you try installing the guest additions?

mcnalu 08-05-2012 10:08 AM

Yes, I have the extension pack.

Don't I need to have the OS booted up before I can install the guest additions?

tronayne 08-05-2012 05:44 PM

Quote:

Originally Posted by mcnalu (Post 4746398)
Don't I need to have the OS booted up before I can install the guest additions?

Yes, you install guest additions after boot, the extension pack before install/boot..

Seems like 1G is a little on the tight side -- maybe at least 5G to give it some elbow room?

If the ISO you used brings you up to a prompt (so you can add partitions with, say, cfdisk) did you add a swap partition and (at least) a root partition?

Did you allocate enough RAM to the virtual machine? On my boxes I give the virtual machine at least 4096 so they'll run (2G ought to be enough, 1G might be a little tight) out of 8G system RAM.

Slackware will pretty much install and work properly in VirtualBox without too much twiddling as long as you give it disk space, at least swap and root partitions and a fair-sized RAM allocation.

kingbeowulf 08-06-2012 03:08 AM

From personal experience, 1GB RAM per guest is plenty to run Slackware in VirtualboX or qemu as long as the host has >2GB RAM. Just be sure you use the generic kernelafter installation to free up a bit of ram inside the guest VM.

mcnalu 08-06-2012 01:56 PM

Thanks for the replies. Apologies if I wasn't clear on one point - I am having a tough time booting from the install DVD or CD iso and from the virtual HD I managed to install to, so any post-boot solutions aren't going to help me.

@troyane I routinely run slackware 13.37 with only 512MB memory with no problem at all and KDE worked quite happily on my 1GB eee pc with slackware 13.x so I doubt it's memory related. My host has 3GB.

I'm running slackware-current on my desktop machine using qemu-kvm now so I'll give up on virtual box for the moment on my laptop - perhaps it is something odd about that laptop and/or that version of virtual box that's causing my troubles.

ppr:kut 08-07-2012 04:49 AM

I had a chat with upstream and it sounds like the suspect is the kernel we are using in -current these days. So something you could try (I know this is rather tricky) is to change the kernel and see if it helps. Hint: you can also include a custom kernel on the install disk which should make things a bit easier.
Other than that I will have a look at 4.2beta1 asap and put links here to the SlackBuilds once I have them done. There's a slight possibility that it's fixed there already.

mcnalu 08-07-2012 06:08 AM

OK, thanks for investigating it. I was using the most up to date set of packages for -current on each attempt, but that made no difference. I'll give it another look again today.

I know how to switch to a custom kernel etc and will try that as soon as I can, though I'll be in a place with little internet for a few days (yes, such places still exist!).

chrisretusn 08-07-2012 11:41 AM

2 Attachment(s)
I am guessing you are referring to the packages from SlackBuilds.org. As a suggestion.

You might try removing that OSE 4.1.14 install and use the VirtualBox installation program. VirtualBox is currently at version 4.1.18. You can get it here: https://www.virtualbox.org/wiki/Linux_Downloads

I have been using the VirtualBox provided installer in Slackware for several years. I find it simpler to use than the Slackbuilds.org packages. I am running both Slackware64-current and Slackware-current as guest (installed with iso's created with AlienBOB's mirror-slackware-current.sh script) in VirtualBox with Slackware64-current as the host. Slackware-current works just fine with the default virtual machines settings (Enable PAE/NX not checked), exceptions; I have Memory set to 1024MB and NIC set to Bridged.

Aside from that. The default 8GB hard drive size for Linux is a tad small for Slackware these days. Especially if you added a swap partition. Give it 16GB, it's dynamic anyway so it will only take what Slackware needs (about 7.1GB with the recommended install)

DasFox 08-07-2012 06:28 PM

Quote:

Originally Posted by chrisretusn (Post 4748185)
I am guessing you are referring to the packages from SlackBuilds.org. As a suggestion.

You might try removing that OSE 4.1.14 install and use the VirtualBox installation program. VirtualBox is currently at version 4.1.18. You can get it here: https://www.virtualbox.org/wiki/Linux_Downloads

I have been using the VirtualBox provided installer in Slackware for several years. I find it simpler to use than the Slackbuilds.org packages. I am running both Slackware64-current and Slackware-current as guest (installed with iso's created with AlienBOB's mirror-slackware-current.sh script) in VirtualBox with Slackware64-current as the host. Slackware-current works just fine with the default virtual machines settings (Enable PAE/NX not checked), exceptions; I have Memory set to 1024MB and NIC set to Bridged.

Aside from that. The default 8GB hard drive size for Linux is a tad small for Slackware these days. Especially if you added a swap partition. Give it 16GB, it's dynamic anyway so it will only take what Slackware needs (about 7.1GB with the recommended install)


I have the same problem, Slackware guest will run on an AMD CPU, but if I try to run it on my new box that has a i3 core it will not work and I get that same kernel issue.

Also I can't even boot the Slackware CD/DVD...

Where is this VirtualBox provided installer in Slackware you are talking about?

I'm not running current I run 13.37, so what can I do to fix this problem?

I've tried this on the last 3 versions of VirtualBox with no success... :(


THANKS

tronayne 08-08-2012 09:23 AM

The VirtualBox installer is at https://www.virtualbox.org/wiki/Downloads. You want the Binary, VirtualBox 4.1.18 for Linux Hosts -- click that link, the select either the 32-bit or 64-bit from "All Distributions."

The download file (for 64-bit) is VirtualBox-4.1.18-78361-Linux_amd64.run, it's 78734802 bytes. You'll also need Oracle_VM_VirtualBox_Extension_Pack-4.1.18-78361.vbox-extpack (it's one level up from the directory where you download the binary file).

If you've compiled and installed the package from SBo, remove it then, as root, execute the ".run" file to install VirtualBox (don't worry, there's an uninstall.sh placed in /opt/VirtualBox so you can remove the binary if you need to).

After VirtualBox installs, install the Extension Pack.

Like chrisretusn, I've been running VirtualBox for some years, always the binary, it works just fine.

Hope this helps some.

DasFox 08-08-2012 10:17 PM

Quote:

Originally Posted by tronayne (Post 4748932)
The VirtualBox installer is at https://www.virtualbox.org/wiki/Downloads. You want the Binary, VirtualBox 4.1.18 for Linux Hosts -- click that link, the select either the 32-bit or 64-bit from "All Distributions."

The download file (for 64-bit) is VirtualBox-4.1.18-78361-Linux_amd64.run, it's 78734802 bytes. You'll also need Oracle_VM_VirtualBox_Extension_Pack-4.1.18-78361.vbox-extpack (it's one level up from the directory where you download the binary file).

If you've compiled and installed the package from SBo, remove it then, as root, execute the ".run" file to install VirtualBox (don't worry, there's an uninstall.sh placed in /opt/VirtualBox so you can remove the binary if you need to).

After VirtualBox installs, install the Extension Pack.

Like chrisretusn, I've been running VirtualBox for some years, always the binary, it works just fine.

Hope this helps some.


Well if I'm not mistaken the binary is suppose to be the official version that is better supported...


THANKS

dr.s 08-09-2012 12:25 AM

Same problem here, occurs in both 4.1.18 and 4.2 beta.

ReaperX7 08-09-2012 12:34 AM

Check your VirtualBox settings to ensure that you have option "Enable PAE/NX" enabled.

DasFox 08-10-2012 01:04 AM

Quote:

Originally Posted by ReaperX7 (Post 4749548)
Check your VirtualBox settings to ensure that you have option "Enable PAE/NX" enabled.

It's enabled by default, last time I checked, I'm going to compile the OSE and get back...

From what I read today after 4.x OSE and Binary are pretty much the same?

https://www.virtualbox.org/wiki/Editions

THANKS


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