LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-25-2009, 06:23 AM   #1
LordAnta
Member
 
Registered: Apr 2008
Location: Bucharest, Romania
Distribution: Slackware current
Posts: 126

Rep: Reputation: 17
VirtualBox problem in Slackware 12.2


I'm using Slackware 12.2 with the default kernel (2.6.27.7-smp) on my laptop (the specs is in my signature).
Recently I have installed VirtualBox 2.1.2 from the site (virtualbox.org, the VirtualBox-2.1.2-41885-Linux_x86.run) and I have some problems. Everytime I start the virtual machine, my keyboard doesn't respond, not in the host or in the guest OS, only the mouse. Once the virtual machine shutsdown, I can use the keyboard. Never had this problem before the 2.1 version.

Did anybody have this kind of problems and, maybe, have a solution?
 
Old 01-25-2009, 04:17 PM   #2
gmartin
Member
 
Registered: Mar 2003
Location: PA
Distribution: Slackware 13.37 Linux Reg # 341245
Posts: 285

Rep: Reputation: 40
Does pressing the host key (right-ctrl, I think) free up the keyboard?
 
Old 01-25-2009, 09:45 PM   #3
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 797

Rep: Reputation: 247Reputation: 247Reputation: 247
I've had numerous problems with the 2.1.x versions of VirtualBox. I've been using VirtualBox for a long time and I can tell you that until a version gets up to about the n.n.6 stage it is usually quite buggy. I'm using 2.0.6 very successfully with Slackware 12.2 and that's what I recommend that you use if you can.

The main feature missing in the 2.0.6 version is the new network functions and I think they may be part of the problem in 2.1.x. If you want a network adapter on the actual LAN instead of NAT then you need to bridge the VirtualBox network interface.

In case you want to do that here's a simple script that I wrote to bridge "vbox0" to "eth0". If you want a manually configured address then comment out the "dhcpd" lines and un-comment the ones that that set the address and route. Also, make sure that you change the account name "erik" to your account name in the script.

Code:
#!/bin/sh
#
# /etc/rc.d/rc.bridge
#
# Script to set up Ethernet bridge
#

return=$rc_done
case "$1" in

    start)
        echo "Starting bridge br0"  ||  return=$rc_failed
        /sbin/modprobe tun  ||  return=$rc_failed
        dhcpcd -k -o eth0
        brctl addbr br0  ||  return=$rc_failed
        brctl addif br0 eth0  ||  return=$rc_failed
        chown root:vboxusers /dev/net/tun  ||  return=$rc_failed
        VBoxAddIF vbox0 erik  ||  return=$rc_failed
        brctl addif br0 vbox0  ||  return=$rc_failed
        ifconfig eth0 0.0.0.0 ||  return=$rc_failed
        ifconfig br0 up  ||  return=$rc_failed
        dhcpcd -t 30 br0  ||  return=$rc_failed
#        ifconfig br0 192.168.1.11  ||  return=$rc_failed
#        route add default gw 192.168.1.1  ||  return=$rc_failed
        echo -e "$return"
	;;

    stop)
        echo "Stopping bridge br0"  ||  return=$rc_failed
        dhcpcd -k -o br0
        ifconfig br0 down
        brctl delif br0 vbox0  ||  return=$rc_failed
        VBoxDeleteIF vbox0  ||  return=$rc_failed
        brctl delif br0 eth0  ||  return=$rc_failed
        brctl delbr br0  ||  return=$rc_failed
        ifconfig eth0 up  ||  return=$rc_failed
        dhcpcd -t 30 eth0  ||  return=$rc_failed
#        ifconfig eth0 192.168.1.11  ||  return=$rc_failed
#        route add default gw 192.168.1.1  ||  return=$rc_failed
        echo -e "$return"
	;;

    status)
        ifconfig br0
        brctl show br0
        ;;

    restart)
        $0 stop && $0 start || return=$rc_failed
        ;;

    *)
        echo "Usage: $0 {start|stop|status|restart}"
        exit 1
esac

test "$return" = "$rc_done" || exit 1
exit 0
 
Old 01-26-2009, 01:52 AM   #4
LordAnta
Member
 
Registered: Apr 2008
Location: Bucharest, Romania
Distribution: Slackware current
Posts: 126

Original Poster
Rep: Reputation: 17
2.0.6 works well. The problem is that from 2.1.0, they changed the virtual image structure, and nothing below 2.1 can open it. And no backup of the virtual machine. No loss. It was just a machine for testing different things. I was just curios to see if anybody else have this kind of problems, cause I have a tendancy to break systems on a monthly basis .

Thanks Erik_FL for the script. It will be useful.
 
Old 01-27-2009, 03:07 AM   #5
Slacker Steve
Member
 
Registered: Nov 2008
Posts: 85

Rep: Reputation: 16
Using 2.1.2 over here with no problems in slackware 12.2
 
Old 01-27-2009, 06:31 AM   #6
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 924

Rep: Reputation: 94
I also didn't experience problems with 2.1.x (Slack 12.2, upgraded from 12.1). I use the installer from the VBox site.
 
Old 01-27-2009, 10:17 AM   #7
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 797

Rep: Reputation: 247Reputation: 247Reputation: 247
My problems with VirtualBox 2.1.2 were not in Slackware. The main problem I had was that it kept crashing a Vista 64-bit Host OS. Based on my experiences with Vista thus far that could be a Vista bug. It appeared to work with Slackware. I have found in the past that Virtualbox can cause the keyboard input to stop working. I have that problem on an Acer laptop and it gets better or worse depending on the version of VirtualBox.

I like VirtualBox but I've found that I have to cherry pick versions to get one that works for me. That isn't a criticism because the frequency of releases (one per month) is an indication that new features and bug fixes are being released without a great deal of testing. Those who use VirtualBox just have to be aware that some versions are not going to be as solid as others.

My only real complaint is that Sun decided to drop support for a Windows 2000 Host OS. I'm still using an older Innotek version of VirtualBox on that computer. Of course Microsoft dropped support for many of their programs on Windows 2000 long before other companies.
 
Old 01-27-2009, 10:10 PM   #8
$lackn00b
LQ Newbie
 
Registered: Jan 2009
Posts: 4

Rep: Reputation: 0
Smile very new to slack & vbox but

i just installed virtualbox 2 hours ago. no problem as of yet, but i am about to check out vista black on it. so i will post and let you know something soon.but so far no problems. hope i can help. Be Blessed
 
Old 01-28-2009, 12:27 PM   #9
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 797

Rep: Reputation: 247Reputation: 247Reputation: 247
Quote:
Originally Posted by $lackn00b View Post
i just installed virtualbox 2 hours ago. no problem as of yet, but i am about to check out vista black on it. so i will post and let you know something soon.but so far no problems. hope i can help. Be Blessed
If you are testing Vista, here is what didn't work well for me. I ran VirtualBox version 2.1.2 on a Windows Vista Ultimate 64-bit host. The CPU was an AMD Turion dual core at 2.0GHz. The guest OS was Slackware Linux 12.2. The problem that I had was soon after booting Slackware, especially in the KDE GUI the Vista OS would suddenly report an error on a BSOD or the entire computer would restart.

I did not have similar problems running other guest operating systems or running VirtualBox on a Slackware Linux host.

The other problem that I've had with all versions of VirtualBox is on Windows XP hosts. I get an occasional "Delayed Write Failed" error that then corrupts the filesystem containing the virtual disk and causes the file size to be set to zero (the file is in essence deleted). I added an environment variable in Windows XP.

VBOX_DISABLE_HOST_DISK_CACHE = 1

That seemed to eliminate the problem but I haven't done enough testing on XP to know for certain. I haven't seen the problem using a Vista host even without that environment variable set.

When new VirtualBox versions are released I usually test them for a while to see if they work as well as the previous version. If I run into any new problems I usually stick with what I have and wait for the next release. I'm doing my software development work using Windows XP in a virtual machine in VirtualBox so I am more interested in a reliable version that one with a lot of new features. The seamless mode makes it quite convenient to run XP on top of Vista. I use Linux about half the time too, especially for file sharing since Vista has problems with the SMB service going out to lunch under high levels of activity.
 
Old 02-08-2009, 05:22 AM   #10
LordAnta
Member
 
Registered: Apr 2008
Location: Bucharest, Romania
Distribution: Slackware current
Posts: 126

Original Poster
Rep: Reputation: 17
The strangest thing. I replaced kde 3.5.10 with kde4 4.2 and now my keyboard doesn't "freeze" when I start a virtual machine. Must of messed something up in kde before.
 
Old 02-08-2009, 09:35 AM   #11
lumak
Member
 
Registered: Aug 2008
Location: Phoenix
Distribution: Arch
Posts: 799
Blog Entries: 32

Rep: Reputation: 109Reputation: 109
I used the build script at SlackBuilds.org and didn't really have any issues. XP ran fine. However, windows 7 didn't want to install for whatever reason. For the slackbuilds script, you only need the kernel and the ose packages. You do not need the extras as those are for running slackware inside of the virtual machine. You need to download the extras ISO that's for windows XP.
 
Old 04-20-2009, 11:54 PM   #12
vahnx
LQ Newbie
 
Registered: Apr 2009
Posts: 1

Rep: Reputation: 0
I am running the latest VirtualBox with the latest Slackware and I can startx fine, but if I try to open the terminal under either root or (user) or other apps, complete guest OS locks up and I must hard reboot the VM. What gives? Host: Win7.
 
Old 04-21-2009, 11:19 AM   #13
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 797

Rep: Reputation: 247Reputation: 247Reputation: 247
Quote:
Originally Posted by vahnx View Post
I am running the latest VirtualBox with the latest Slackware and I can startx fine, but if I try to open the terminal under either root or (user) or other apps, complete guest OS locks up and I must hard reboot the VM. What gives? Host: Win7.
I'm not using the latest version of VirtualBox because I had too many problems. The versions that work the best for me are these.

1.6.6 or 2.1.4

I try to avoid the x.x.0 releases because they usually have a lot of bugs. By the time they get to x.x.4 or later they are usually more solid.

If you are not using the VirtualBox Guest Additions for your Slackware guest that might help. Also, make sure that you have the correct kernel headers for your kernel. Otherwise the Guest Additions will not build correctly and might crash.

The forums on the VirtualBox.org site are a good place to check for solutions. You might want to report the bug if it isn't already reported by someone else.

I haven't tested with a Windows 7 Host OS. Personally I recommend avoiding Windows 7. It's still basically just Vista with new colors and is a beta release. Many of the known Vista bugs aren't fixed in Windows 7 beta and neither are my complaints about the poor user interface. Either Microsoft has a lot more changes to make or it will result in another big yawn from Windows users. I'm managing to survive with Vista and I'll be damned if I'm going to pay for new colors and bug fixes. If Microsoft offers to give me Windows 7 to replace Vista then I'll consider upgrading. Otherwise Microsoft and all its "partners" will have to support Vista. They sold it.

Meanwhile Linux keeps getting better and I'm using that about as much as I use Vista. If it wasn't for a few good Windows applications that I use I'd probably just quit using Vista. Those applications are slowly getting worse with each new Windows version. The modern approach to Windows software seems to be "Sell it now, fix it later and sell the fixes for more money".

Although I like VirtualBox it has a poor track record of reliability since Sun bought it from Innotek. The releases are too frequent and not tested enough. There is no distinction between "unstable" and "stable" releases. I've had to figure that out on my own. But, maybe there's hope. Oracle may buy Sun.
 
Old 04-21-2009, 02:16 PM   #14
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31
I had some strange usb behavior also in the latest VB non free. For example, my scanner would work...but not my usb keypad! Where can I get VB 2.0.6....I may have a copy on an external somewhere...I'll report back.
 
Old 04-21-2009, 03:54 PM   #15
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 797

Rep: Reputation: 247Reputation: 247Reputation: 247
Quote:
Originally Posted by thezoid View Post
I had some strange usb behavior also in the latest VB non free. For example, my scanner would work...but not my usb keypad! Where can I get VB 2.0.6....I may have a copy on an external somewhere...I'll report back.
Older versions of the free VirtualBox can be downloaded from VirtualBox.org.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Installing VirtualBox from SlackBuild - Slackware 12 - vboxdrv problem Do7AN Slackware 9 01-22-2009 01:58 PM
Slackware 12.2 on VirtualBox 2.1.0 BerzinTehvs Slackware 1 01-10-2009 06:03 AM
Slackware in VirtualBox gmartin Slackware 6 07-03-2008 11:14 AM
VirtualBox on Slackware: How? gargamel Slackware 94 04-26-2008 07:42 AM
virtualbox problem in slackware mahdif Slackware 2 10-25-2007 06:15 AM


All times are GMT -5. The time now is 09:45 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration