Slackware :: Installing 13.37 On VirtualBox From An ISO
May 2, 2011
I have an ISO of 13.37, I have selected the ISO as the booting medium in the Virtual Box and I do get uptil the screen where one is supposed to select the source media. Because I am installing from an ISO what option I am supposed to select out of the 6 present there?
I'm trying to install virtualbox on slackware 13 and I'm running into header issues I think...it says it can't find libcap..any ideas? I downloaded libcap from slackbuild and tried to run make but I get errors (the second code block)
Code: VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_echo VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_cp VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_install VirtualBox-2.1.4_OSE/kBuild/env.sh patching file VBox.sh Checking for environment: Determined build machine: linux.x86, target machine: linux.x86, OK. code....
I installed Slackware 13 in VirtualBox 3.1 (seehere)When I'm logged in as a normal user, I get a mesage that Intel *** (sound device) doesn't work anymore and I hear no sound.But it works very fine when I'm logged in as root.
I currently have vbox 2.0.6 OSE and its been running awesome except I get errors with directx when running 3D apps cause of the video card driver that comes with vbox(at least so far thats I narrowed it down to). So, Im trying to update to 3.2.2 but cant seem to find an easy way to do it. I downloaded the RPM for OpenSUSE 11.1 from Sun's website and when installing it I got errors about files conflicting with the previous version. So I ran a "zypper rm vbox" to remove the current one and then ran the RPM again and it seemed to finish the installation fine, I just cant find it to run it.I currently have the 2.0.6 version installed again just so I can use it... but now am back to trying to get 3.2 installed before looking in another direction.
"Why on earth are you trying to install Vista?!" I know, I know, I'd install XP if I had a disc. My computer came with Vista and I accidentally deleted it when I installed Ubuntu. Now I'm trying to run Vista as a virtual machine with VirtualBox, but I'm having a bit of a problem. I'm running Lucid, everything should be up-to-date. I set up everything in VirtualBox, hit start, and booted up with the CD. That's where the problems begin. First screen reads:
I'm using ubuntu 10.04 (upgraded from 9.10) and I've also got my WinXP Toshiba Rescue CD which i'd like to install in VirtualBox but it just won't go past the 'unpacking' part. When it says that it's completed, the only option i have is clicking OK. Doing that just shuts down the VM then. And when I restart the VM, it just does the unpacking step all over again. Last year when I had a dual boot system (XP and ubuntu 8.10 i think it was), the installation went fine until I realized that my ubuntu partition was way too small. So I could not install XP in a VM. But it still got to the actual windows installation step. I'm still using the same PC the rescue CD came with.
I installed VirtualBox, and I want to install Vista on it. I just have the copy of vista that came with my computer. I made the back up disks for it, and tried to use them to install it in the virtual box, but it said it was unable to install in that machine.
After that I looked in my windows partition and found the product ID for the vista copy. My question is: Can I download a copy of Vista and then use the product ID of my copy to make the installation in the VirtualBox? Are there any technical or legal reasons not to do this?
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
The latest release of VirtualBox (3.1.6) corrects most of the problems that I had with Slackware and KDE. If you have been avoiding VirtualBox or KDE because of those issues you might want to take another look.The only problem that I'm having now is that I have to click somewhere on the desktop to get a proper display when switching VirtualBox into "seamless" mode. The rest of the window display issues appear to be fixed and full screen mode also works correctly.
I downgraded a computer a couple of weeks ago from -current to 13.1. At that point in time the USB support in my Virtualbox stopped working. Since then I have installed Virtualbox on my wife's laptop, which also runs 13.1, and the USB support doesn't work there either. So I tried it on yet another 13.1 box that I have lying around no USB support. Then I upgraded the latter box to -current and USB works! Given that sequence of events, I'm pretty sure this is a Slackware 13.1 problem rather than a Virtualbox problem. what might be causing this?
I'm trying to install the Virtual Box Guest Addition for my openSUSE 11.3 VM, but I'm having some problems. The Virtual Box manual says I need to install the kernel-default-devel package, so I did that, but it also says :
Make sure that your running kernel (uname -a) and the kernel packages you have installed (rpm -qa kernel*) have the exact same version number. Proceed with the installation as described above.So I ran both commands and here is the output :
edgar@linux-t7uc:/> uname -a Linux linux-t7uc 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 athlon i386 GNU/Linux edgar@linux-t7uc:/> rpm -qa kernel*
the devel packages are version 126.96.36.199-0.7.1 and the kernel is version 2.6.34-12. How do I install the correct version of the kernel-default-devel and kernel-devel package with zypper? I thought maybe the versions could be compatible somehow, so I tried to install the Guest Addition and here's the result :
edgar@linux-t7uc:/media/VBOXADDITIONS_4.0.4_70112> sudo sh ./VBoxLinuxAdditions.run root's password: Verifying archive integrity... All good. Uncompressing VirtualBox 4.0.4 Guest Additions for Linux.........
Until yesterday I was living the Linux dream. I had my computer working like a charm but I wanted more and I installed Virtualbox. It asked for some drivers and the kernel source for compiling them. After a reboot VB was working ok but sound was gone.
I've done some tests for solving the problem with no luck:
1. reinstalled all ALSA packages 2. reinstalled all pulseaudio packages 3. reisntalled all phonon packages 4. regenerated /etc/alsa-conf 5. rechecked all sound settings under YAST (volume), everything looks good but there is no sound 6. rechecked all sound settings under System preferences > Multimedia > phonon (gstreamer and xine are installed, gstreamer is the default engine) 7. executed /usr/sbin/alsa-info.sh [url] 8. tried $speaker-test -Dplug:front -c2 -l5 -twav and other commands from SDB:Audio troubleshooting - openSUSE with this output
I'm not sure if this is a Debian question or a VirtualBox question, so I'm posing here and will likely pose it on the VBox forums as well.When I install Debian into a new VirtualBox VM, it always installs Ext3 as the file system. I've tried the Advanced installer, but there does not seem to be a way to specify Ext4 as the file system.My questions are:- Is Ext3 the default for Debian 6?- Can I specify Ext4 as the file system at install? Should I even care? I know Ext4 is faster, but would that performance boost be meaningful for a laptop/cloud user?I know I can convert from an Ext3 to Ext4, but that's clearly a lot more work than just installing it during initial setup.VirtualBox does support Ext4, as I have installed Ubuntu 11.04 with Ext4 and it boots and operates fine.
I updated my system to the latest version - 5.5. After that I could not install VirtualBox. I was thinking, trying to fix, googling... it over for hours... Finally I found the reason. VirtualBox installer searches for the source kernel at /lib/modules/2.6.18-194.17.4.el5/build, and it can not. Look into /lib/modules, I have some kernels such as:
- 2.6.18-194.17.4.el5 - 2.6.18-194.17.4.el5debug - 2.6.18-194.17.4.el5xen ... and more old ones.
At that time, I booted on 2.6.18-194.17.4.el5 kernel. But inside that directory, there is no build or source (directory/ file). Then I looked into 2.6.18-194.17.4.el5debug, and it had. So I typed: ln -s /lib/modules/2.6.18-194.17.4.el5debug/build /lib/modules/2.6.18-194.17.4.el5/build
Installed 13.1 as a guest in VirtualBox with Debian Lenny 5 64bit as host. The mouse, gpm, and the keyboard work alright at the black screen but in the graphical thing, forget its name.....Xsomething, not KDE, there is no mouse or keyboard; for example the screensaver just goes on and on and nothing will stop it.
Since my upgrade to 13.37 + VirtualBox 4.0.4 (from SBo) I'm having trouble with one of my VMs containing a PostgreSQL installation (also from SBo) which has been running fine before on 13.1 + VBox 3.2.10.
This is what happens: I'm starting an I/O heavy job on the DB that should take about an hour but never finishes because the virtual disk stops working after 10 to 40 minutes.
Code: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen ata1.00: failed command: READ FPDMA QUEUED ata1.00: cmd 60/00:00:e8:11:44/01:00:02:00:00/40 tag 0 ncq 131072 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) lots of these
Just grabbed Slackware64-current and installed on my laptop. Also put Alien Bob's multilib on.need it for my Absoft fortran compiler.The problem I'm having is that VirtualBox-3.1.6 doesn't install. I've looked at other problems on the list related to this and I don't think that any of the ones that I've seen applies to my situation. My feeling is that there is an incompatibility problem with gcc. The stock kernel was compiled with gcc-4.4.3 which comes with Slackware64-current. However, Bob's multilib backdates this to gcc-4.3.3. So, when the Virtualbox installation procedure runs it sees a kernel compiled with a version of gcc that is different from the one that is currently installed and chokes. recompile the kernel with the current gcc. Haven't done a kernel compile in a long time though and I'd like to get it right. So, my question is "Is the stock .config file in the linux source folder the one used to configure the default kernel?". I like the stock kernel and would like to recompile with all the bells 'n whistles in the stock kernel.
I have Fedora14. I have added virtualbox repository. On going through virtualbox.org site, I learned that virtualbox-4.1 released. I tired to update by yum update on 19.0.2011. No new package. I tried to download it from virtualbox.org (VirtualBox-4.1 Fedora14-i386). It failed on 19.0.2011 giving message that link is not operational. Today i.e. on 20.07.2011, I tired once again yum update. No new package. I tried to download from virtualbox.org. download succeed but it did not installed giving error message regarding conflicting files. Till not in repository?
I tried installing virtualbox on a redhat 5.3 (32 bit) on an intel box. It cannot find prereq libSDL-1.2.so.0 while trying to install the rpm with yum. I have looked for someplace to download the prereq and cannot find it. Does anyone know where I can find the prereq?
I'm trying to install Sid in Virtualbox using debian-testing-amd64-businesscard.iso : Expert install, Sid mirror, Standard system utilities....So far, so good. After that I want to install a minimum gnome, but this time ( I've done it before with success ) I got stuck :
I tried to build the virtualbox 3.1.6 kernel using the files from slackbuilds.org and I got this error that says it cannot find the kernel include directory. My current kernel is 188.8.131.52 (slack 13.1).
I tried SOME_VAR=/usr/include --> (I forgot the exact variable name, but I used the variable name I saw in the error message) just a guess , but it didn't work of course.
Is it at /usr/src/linux-184.108.40.206/include or something like that? Or is there anything wrong with the slackbuild script?
I plan to install SlackBuild: virtualbox-ose (3.2.10) on my stand alone laptop.The following are excerpts from the SlackBuild Readme file and I was hoping that someone might have the time to clarify a few things: "By default VirtualBox will be compiled with hardening enabled. That means all binaries will be run suid root, which is the default behaviour of upstream packages. However, you are still able to disable this by passing HARDENING=no to the script."Why would I want to do this? If I did want to do this, how do I pass 'HARDENING=no' to the script? What script?
Edit: I found something on this and see that I'll just include my user in the proper group and I should be ok.'To compile virtualbox without the Qt4 GUI pass QT4=no to the script'I have a package called: qt-4.6.2_2d3d3e5-i486-1 installed - does this mean that I have Qt4 installed?'To enable the webservice pass WEBSERVICE=yes to the script. This adds gsoap to the list of required dependencies.'Why would I want to do this? If I did want to do this, how do I pass 'WEBSERVICE=yes' to the script? Also, to do this I would have to install gsoap first, right?'If you want to attach VirtualBox to a VDE network you will need vde2.I don't need this for my stand alone world, right?This requires acpica, and the virtualbox-kernel package is needed at runtime.'Does this mean that VDE network requires acpica or that this SlackBuild require acpica?
pretty comfortable at the command line and in kde. found 2 'supplementary kernel drivers' for virtualbox at slackbuild (thank you heinz!). followed the how-to at slackbuild and built and installed both packages, but additions weren't working. (i thought they were standalone) noticed the 'supplemental' in their description, and so installed the guest additions for linux from vbox site. additions still not working. at this point i start restarting my slackware vm, and redoing everything in various sequences. finally, additions work! but i'm not sure why! critical pieces and sequence for getting guest additions working once i have slackware installed?
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3 telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
I installed in my Slackware 13.1 with generic kernel 220.127.116.11-smp VirtualBox packages taken from SlackBuilds.org (acpica, virtualbox-ose and virtualbox-kernel). Then for testing purposes I installed in VirtualBox Windows XP using CD-ROM drive connected to USB port. It's a lot of fun to see Windows as an application in Linux!
Now I'm trying to install in VirtualBox Linux Mint using either USB flash drive prepared with unetbootin or mere ISO image. Without success. It seems VirtualBox 3.2.10 OSE doesn't recognize either USB flash drives or ISO images though it recognizes CD-ROM drive connected to USB port. I found some advices searching Internet but all of them are useless.
I need to evaluate PostBooks, an accounting packages that's 32-bit only,needs PostgreSQL and I only have Slackware 64-bit boxes available, I don't really want to install multilib, so I'm thinking VirtualBox for a quick and dirty (got the DVD, got 32-bit, got PostgreSQL, what the heck). Then I got to wondering -- before I screw something up, do you write to the virtual drive MBR or is there a better way?
I am running Windows XP in VirtualBox. I generally only use it for iTunes and some light browsing occassionally. Downloads only occur on iTunes, but it does have internet access. And my wife will still only use Windows, so if she uses this particular machine it is available to her, and she occassionally goes to facebook on this machine.
Should I install an anti-virus? Is it really necessary? I am pretty certain my Linux install would be unaffected even if a virus or other malware did occur in VirtualBox.
I'm having trouble compiling virtualbox-ose.SlackBuild 3.1.6 on Slackware64 13.0 with multilibs made from the Slackware64 13.0 dvd iso. I've changed arch to x86_64 and libdirsuffix to "". acpica.SlackBuild built successfully and virtualbox-ose.SlackBuild is attempted built after running ". /etc/profile.d/32env.sh" as specified in the multilib documentation. All is well until..
connect my Ubuntu 10 edition to internet through nokia 5630 xpressmusic. also i am not at all aware of the commands used in ubuntu.. if any body having help file abount basic installation commands. install virtualbox inside Ubuntu10. i downloaded the package fro site.but it shows dependance error..
I'm trying to get Virtualbox up an running. So I have added virtualbox in my repo and added the key, looks fine so far. but afeter downloading I get this:
VirtualBox-3.0.8_53138_rhel5-1.x86_64 Creating group 'vboxusers'. VM users must be member of that group! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Compilation of the kernel module FAILED! VirtualBox will not start until this problem is fixed. Please consult /var/log/vbox-install.log to find out why the kernel module does not compile. Most probably the kernel sources are not found. Install them and execute /etc/init.d/vboxdrv setup as root.
For some reason, when I click on the Slackbuild link for virtualbox-kernel (3.1.6) for virtualbox-kernel-3.1.6.tar.xz , it downloads as virtualbox-kernel-3.1.6.tar.tar. The file is misnamed. If it is renamed virtualbox-kernel-3.1.6.tar.xz , the SlackBuild works just fine.
I download "VirtualBox-3.1.2-56127-Linux_amd64.run" and installed it, and got a messages like this " virtualbox have been installed successfully in my system", but when I run virtualbox, I've been told "/etc/init.d/vboxdrv setup" something like that. And I run virtualbox in terminal, got this:
Warning: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (18.104.22.168) or it failed to load. Please recompile the kernel module and install it by sudo /etc/init.d/vboxdrv setup You will not be able to start VMs until this problem is fixed.
I run "/etc/rc.d/rc.vboxdrv start" as a root, got messages like this : Starting VirtualBox kernel module ...failed! (modprobe vboxdrv failed.)
I installed slackware 13.37 32 bit in a virtualbox vm for httpd web site testing. I am running the guest in slackware 13.37 64bit host with host only networking.
I can ping the guest and access the pages hosted via a web browser on the host. However I want to upload new sites to test via ftp to a dir on the guest at location such as /home/user/public_html and access them via the host. Vsftp is enabled. But how would I set it up to be able to do this?