LinuxQuestions.org - Virtualbox driver

- SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)

- - Virtualbox driver (https://www.linuxquestions.org/questions/suse-opensuse-60/virtualbox-driver-593253/)

VirtualBox
I have got VirtualBox working and Win98 installed in it. I'm still having problems getting USB drivers to work to try out my scanner. Seems the devices in the PC are not naturally seen by the VM.

I have also have a problem finding a display driver that will get the VM display up to SVGA. Have found Display Doctor and that seems to work but seems to be a trial program. I couldn't get a downloaded VESA driver to come out of VGA mode. What other drivers are recommended?

Regarding the Processor speeds and overheating, I see their are warnings on this for Win 98. Is this a problem?

About Vmware Player and Qemu.
I now have downloaded Vmware Player and Qemu. Must I also download the accelerator kqemu? How do these two programs relate? Reading the notes on qemu it seems to be an independent virtual machine manager.

Virtualbox works great in suse 11; but suse 11 does not play nice with the yast virtualbox install. There are problems with the yast install in suse 11.0 - I dont remember what they are but they are discussed in the opensuse forum.

Use the suse 10.3 rpm from the virtualbox website - it works just fine in opensuse 11.0.

Also after you install suse 11 make sure that you have the kernel headers installed.

Forget everything I said about suse 11 - since you are running 10.3.

Your problem with usb, is that one of the suse developers removed the traditional method of supporting usb from the suse kernel. That screwed up a number of applications. There is a long bugzilla thread about this. After a lot of kicking and screaming, the damage was finally undone. If you have a current kernel for suse 10.3 then you should be able to get usb working.

Here is an excerpt from the VirtualBox user manual:

Quote:

11.5.7 USB not working
If USB is not working on your Linux host, make sure that the current user has permis-
sion to access the USB ﬁlesystem (usbfs), which VirtualBox relies on to retrieve valid
information about your host’s USB devices.
As usbfs is a virtual ﬁlesystem, a chmod on /proc/bus/usb has no effect. The
permissions for usbfs can therefore only be changed by editing the /etc/fstab ﬁle.
For example, most Linux distributions have a user group called usb or similar, of
which the current user must be a member. To give all users of that group access to
usbfs, make sure the following line is present:
# 85 is the USB group
none /proc/bus/usb usbfs devgid=85,devmode=664 0 0
Replace 85 with the group ID that matches your system (search /etc/group for “usb”
or similar). Alternatively, if you don’t mind the security hole, give all users access to
USB by changing “664” to “666”.
The various distributions are very creative from which script the usbfs ﬁlesys-
tem is mounted. Sometimes the command is hidden in unexpected places.

I am running 11.0 not 10.3. Looking at /etc/fstab or /etc/group and looking into my user and group security setup in YAST I don't have any USB references to allocate to any user. My USB does however work fine normally with my printer and with other plugins like flash drives.

I'm going to start trying out 1kyle's Player and qemu to see if they set up better. I can't understand why a packaged system like VirtualBox isn't tested out by Novell. Why package it if it has problems?