Slackware :: Can't Start 13.37 On VirtualBox 4.0.6
May 7, 2011
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.
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
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 have a virtual machine on VirtualBox.I had Fedora 11, all was well.I ran the "preupgrade" tool. It downloaded all successfully, it asked me to reboot.On reboot, it installed everything as it should. It finished by saying it was installed successfully and asked me to reboot one last time.Now when I start it, some text flashes rapidly on the screen. Then it stops.See attached file for screenshot of the last text shown.
Every time I try to start a virtual machine in VirtualBox I get this error:
Code: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. So I run '/etc/init.d/vboxdrv setup' in the terminal as root and I get this:
Recently I had updated the kernel but afterwards I can't run virtualbox because the kernel modules aren't loaded.
Virtual box: 3.1.4 r57640 OpenSuse110-x86_64 Open Suse 11.0 running kernel-default-2.6.25.20-0.7
When I try to start vboxdrv manually I can find the message: kernel: warning: `VirtualBox' uses deprecated v2 capabilities in a way that may be insecure.
After I installed the older kernel-default-2.6.25.20-0.6 version I can start virtualbox.
But, much to my suprise, I also get this message with this kernel level. But still, the kerneldrivers are loaded and I can run virtualbox.
I want to start VB in headless mode. It is possibe to tell VB to run the VM with a useraccount, but i will asked after his password. So it is not possible to run it in runnlevel 2 and 3.
I just installed VB, but I cannot manage it starting.
uname -a output:
Code:
As told in the FAQ on virtualbox.org, I downloaded and run the amd64 version of VB version 3.1.2. (since I have a 64bit CPU) Install worked just fine, but when I'm trying to launch it, I get the following error message:
after upgrading VirtualBox from 3.0.x to VirtualBox-OSE-3.1.2-1.fc12.x86_64 VBox fails to start any virtual machine with error: Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
I get FATAL: Error inserting vboxnetflt (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetflt.ko): Invalid module format FATAL: Error inserting vboxnetadp (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetadp.ko): Invalid module format Kernel is (obviously) kernel-2.6.31.12-174.2.19.fc12.x86_64, but same thing happens with any installed kernel, IE kernel-rt-2.6.31.12-1.rt20.1.fc12.ccrma.x86_64
I reinstalled VBox and kmods got rebuilt but the problem persists.
I can't get Ubuntu v10.10 to start on VirtualBox running under Windows XP. The installation wen smoothly. However when I try to start the machine what I see is a mere black screen... The boot order is fine. However it seems strange that no data is read from the virtual hard drive (which is about 2.15 GB):
I'm running the host server on Ubuntu 10.04 LTS (64bit) . I'm using virtual box. I want to automatically for one of the guest vritualboxes to start on reboot. Following is already done without a success. Please help me in solving this.
1. I have created the following shell script #!/bin/bash /usr/bin/nohup /usr/bin/VBoxHeadless --startvm "VMNAME" 2> /dev/null &
2.From the current logged on user I did a crontab -e and did the following
crontab -e @reboot /bin/sh /home/myaccount/shellscript.sh note that I do not encrypt the home directory and sufficient permissions are there.
I'm preparing a vitualization server (host) with VirtualBox. This machine, running Debian, is intended to run in HeadLess mode, without GUI. I've got some guests VMs running. But I was wondering about the best way to start this guests VMs on startup and shut them down kindly when host is shutdwon.
Virtual Machines run under non-root user. I was thinking about making a script in /etc/init.d/ in order to start certain VMs and to stop every VM running when system is halted. Is this really the simplest and most secure approach? Actually I couldn't find very much on this subject in user manual or googlin' around.
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?
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?
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I have been having some problems with virtualbox starting. So here is the issue: When I start a VM I get the following: Code: Kernel driver not installed (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. reinstall the kernel module by executing
[code]...
I am seeing quite a few entries about the usb. I am not sure if that is common or if its unrelated. I am running x86 11.3, and virtualbox 4.0.4 I have tried to uninstall, and even go back to 3.2
Trying to run windows only apps. I installed Wine first from software center. Most progs I try to run only give me the 'working' icon for 20 seconds then nothing. I did modify properties to allow .exe to run. I Dl'ed & installed the VirtualBox package w sw center and same deal- nothing. No error messages or anythng.
Running Ubuntu maverick. My Cpu is a compaq presario laptop CQ50, dual core intel T3200. Not the best but should at least start the progs yes?
Can't really troubleshoot as I have no feedback at all.
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 am trying to start a VirtualBox VM on a separate X screen (in fullscreen) so I can switch between Linux and Windows XP by doing Ctrl + Alt + F<.
I am basically trying to do something like this:
startx "VBoxManage startvm XP" -- :4 startx "VBoxManage startvm "XP"" -- :4 (is this correct for quotes within quotes??)
I get a "bad command line option "VBoxManage" back from the startx script so obviously I am not understanding the rules for how to write "shell magic".
How can I do this correctly, or perhaps there is a better way of achieving a VirtualBox VM on a separate X screen?
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 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'm trying to compile virtualbox 3.2.10 con slackware current 32bit through sbopkg
I get this error (I'll copy only the end part)
Code: CXX VMMR3 - {C}/src/VBox/VMM/VMMAll/TMAllCpu.cpp cc1plus: warnings being treated as errors In file included from /tmp/SBo/VirtualBox-3.2.10_OSE/src/VBox/VMM/VMMAll/PGMAll.cpp:236:0:
