LinuxQuestions.org - slack13 in virtualbox on a ubuntu host

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - slack13 in virtualbox on a ubuntu host (https://www.linuxquestions.org/questions/slackware-14/slack13-in-virtualbox-on-a-ubuntu-host-772428/)

slack13 in virtualbox on a ubuntu host

Hi,
I have no internet on my slackware 13 virtual machine on my laptop running ubuntu.
i thought originally this was either a ubuntu problem or a virtualbox problem, but i dont know now.
A nice chap replied to me on the ubuntu forums (http://ubuntuforums.org/showthread.php?t=1311808) telling me to foward ports actually in slackware. This didnt work either. Does this make sense to anyone here? I'm really sorry if it is in fact a ubuntu/vb issue and not a slackware one.

Thanks,

mute

It is much more likely to be a host problem than a guest problem; the guest OS (Slackware) simply finds a very common NIC and is configured to suit. You can demonstrate this in the guest by running lspci and ifconfig -a.

Which version of VirtaulBox are you running, where did you get it from, how did you install it and how have you configured the virtual machine's network adapter(s)?

Cheers for the reply, i shall get all of this info for you when i get home tonight.
I shall run lspci and ifconfig -a in my slack13 guest, and my other linux VM as well and compare outputs. i'm sure that in terms of networking they are set up the same in virtualbox (i have internet working fine in my other linux vm).

Thanks again mate. i shall find the requested info.

mute

Virtualbox version: 3.0.10 r54097 (PUEL).
Installed from virtualbox website (an ubuntu deb file i seem to recall).
Installed just by double-clicking the deb file.
Network adapter: PCNet-Fast III (NAT). This is the same for my other VM as well (internet works on that one).

I noticed upon booting my host today i get this message whizzing up the screen:

Code:

vboxdrv (3.0.10): Installing module.

.... (bad exit status: 101)

A newer module version than this already exists in this kernel, you can manually install later with --force

could this be it? If so it looks like it might be a host/virtualbox thing, and if so, sorry for posting here :O

mutexe

It looks more like a warning than an error but could be the root cause of the problem; the vboxnetflt module depends on the vboxdrv module. Few netsearch hits on that error message. Can you find where it is coming from? It could be /etc/rc3.d/S20dkms_autoinstaller (favourite) or /etc/rc3.d/S20vboxdrv (but that script does not include that error message and discards error messages from modprobe vboxdrv). You may be able to work out which script the message is coming from by examining the preceding and following boot messages in conjunction with knowing the order of S* boot scripts in /etc/rc3.d.

Do you have any vbox files-or-directories in /etc/dkms?. Is the current VirtualBox the first VirtualBox you have installed on this host?

Meanwhile, if you open up the "Sun VirtualBox" GUI on the host and compare the Network settings for the working and not-working virtual machines, are there any differences?

EDIT: given that the other virtual machine is networking OK, it seems unlikely that the message indicates the root problem so I hope you find a significant Network configuration difference in the VirtualBox GUI.