Slackware :: Libcap Errors When Installing VirtualBox On 13?
Mar 21, 2010
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 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 am trying to run VirtualBox on Ubuntu 11.04 Natty, and when I make a virtual machine it says it is successful. However when I try to run the machine I get this error box. What did I do wrong? What can I do to fix this? I've deleted the virtual machine and made a new one. I've uninstalled and reinstalled virtualbox but nothing I've tried works.
I installed Vista in VirtualBox 2 days ago and all has been well since. However I just started VB tonight and although it started up ok, when I clicked on Start (Vista) I get the following pop-ups. Although one of the errors appears to say what I should do, I don't understand it Could somebody tell me what I need to do to fix it please? Preferably in English
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
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.
Trying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS removing old DKMS module vboxdrv version 3.1.6 Deleting module version: 3.1.6 completely from the DKMS tree. Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source -> /usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found at /lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12. code....
I'm using the latest Vbox on FC15. I'm running a win7 guest and it seems to work ok, but whenever I select "settings" the following error windows is displayed:Failed to access the USB subsystem.Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host
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.
Everytime I try to install Ubuntu 11.04 on my computer it gets stuck at the Keyboards settings and it keep saying "Ready when you are" and then nothing happens.
By the way, I have Windows 7 64bit. Intel i5 2500K 3,3 GHz Quad-core 8GB RAM Sapphire Radeon 5770 HD 1GB
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?
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.
"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:
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 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'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*
[code]...
the devel packages are version 2.6.34.7-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 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
On a previous thread, I explained how I installed Fedora 14 from the live image disk onto a HP 2140 netbook only to find I was missing the development files. Stoat helped me use the more complete install DVD from Fedora 14 to install the development tools (rather than doing a complete reinstall -- which I would do if it made this work).
Unfortunately, I'm still unable to make PartImage 0.6.9 install. When I try, configure says that the bzip2 library (libbz2) is not found or too old. Apparently, this is because it can't get it to respond to BX2_bzopen from within the library. I think because it can't find the library. Inside the config.log file it seems to indicate that from an -lbz2 not found. Now I'm guessing that there is some trick to this, maybe some way of setting the library path to include the location of this and possibly other libraries under Fedora 14. I've checked the library's location and it seems to be in /lib as far as I can tell and bz2 does work, so it's somewhere. Of course it's possible since PartImage is pre-version 1 but doesn't have much if any activity on its forum that something has changed position in Fedora and the install isn't looking for it in the right place.
I've seen one blurb in the PartImage files that indicates that maybe using env to set environment variables on entrance to configure might work, but I'm not sure what variable to set or how to make it find the bz2 library. Note that I've been a UNIX user and administrator in the past, but that was in the System 7 days so that's rusty and I have no prior experience with LINUX of any kind.
I'm new to Linux use, and I'm trying to install new software. However, no matter what I try to install, I always get an error. This includes updates, and extra programs. What am I doing wrong?
I am trying to install gcc 3.2 on linux mint 10 julia . I have gcc 4.4.5 installed already. I am getting errors during the 'make 'stage. I did the following after downloading gcc-3.2.tar.gz
Code: tar xvf gcc-3.2.tar.gz mkdir build-gcc cd build-gcc
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.
