Reasons for using Qemu/VMware/Virtualbox??

linus72 · 04-01-2009, 04:21 PM

OK-everything went fine except this-

Code:

modprobe vboxflt # load the first module
FATAL modprobe vboxflt not found

Other than that everything went fine-no errors
what is vboxflt??

linus72 · 04-01-2009, 04:41 PM

OK-it's cool-
everything is working-I set up a fixed size VHD of 8GB, enabled USB/audio/net and booted off the DSL-4.4.10 iso
But when vbox started my screen went black and then came back on-then the vbox window appeared and I'm now installing dsl to the VHD.
Why did the screen go black and what is vboxflt?
edit that DSL would not load right-what's wrong?

Didier Spaier · 04-01-2009, 05:34 PM

IMHO 8GB is way too much for DSL and my advise is to set up you virtual HDs as of variable size, so you won't waste space. Don't worry, they will expand as needed till they reach the fixed limit.

For the screen going black I don't know, neither what is vboxflt.

To install/launch a new distribution, if it is in an ISO image on your HD:
1) In the File menu select "virtual support managers" -- or something like that, translated from French

2) Go to the "Optical disc images" and add one -- add DSL-4.4.10 iso, for instance
3) Highlight the DSL VM in the menu, then hit Preferences, click Optical disk, check "Insert an optical disk", select the ISO image you just added.
4) Hit Launch.

Same apply for using real CD/DVD instead of ISO image on your HD, but steps 1) and 2) which are not necessary. In step 3) choose your real CD/DVD reader.

And read the Help, it's helpful

linus72 · 04-01-2009, 05:45 PM

Yea-something is wrong-my whole screen goes black when I start the emulator window, then goes black again when it says "press F12 for boot", then goes black again as DSL boots-but I tried another iso and same result-they both hang and freeze during boot...?
So, I guess vboxflt must be important or something....?
Note that I am in Slack 12.2 on sda1.

Didier Spaier · 04-01-2009, 06:18 PM

My fault, I misspelled one of the modprobe commands. As root type:

Code:

modprobe vboxnetflt

Then check that both modules be loaded:

Code:

lsmod|grep vbox

Then restart VirtualBox.

linus72 · 04-01-2009, 06:23 PM

OK-did that-

Code:

root@bz:~# modprobe vboxnetflt
root@bz:~# lsmod|grep vbox
vboxnetflt             88456  0
vboxdrv               114216  1 vboxnetflt
root@bz:~#

Now, do I ave to restart anything?
Or should vbox work now?

Didier Spaier · 04-01-2009, 06:25 PM

VirtualBox should work, but to make sure close it then run it again.

You should not loose your settings.

linus72 · 04-01-2009, 06:34 PM

OK-thanks for all your help Didier!!
Your the man!
the issue with the screen still exists-I click the vbox start button-the entire screen(my screen) goes black-pops back up and vbox window is open-says "press F12 for boot device"
screen again goes full black-pops up again with the dsl boot screen in vbox window-screen goes black again-pops up again and dsl boots fine.
I'm worried cause MY moniter is the one blacking out-not the vbox "window"
Can vbox cause harm to my monitor??

Didier Spaier · 04-01-2009, 06:52 PM

Quote:

Originally Posted by linus72

I'm worried cause MY moniter is the one blacking out-not the vbox "window"
Can vbox cause harm to my monitor??

I don't think so. Remember that if your VM is set-up full screen what you see on the screen is is the VM's display or window. Sometime I don't even remember if what I see is the "real" Slackware 12.2 screen or the "virtual" Slackware-current screen. I have to type "uname -r" to make sure

Anyway fiddle with the VM's menu and see what changes when you go "Full screen" or "Adjust window's size", for instance