Tossing VirtualBox in the UbuntuLinux System

I was looking for a new topic for managing the UbuntuLinux system. First, a video card is accelerated. Then we can see the VBox. I always wanted to install a virtual machine, so sudoapt-getinstallvirtualbox was directly installed and can be run. However, when creating a new virtual machine, the system prompts no kernelModule: VirtualBoxkerneldrivernotinstalled. Thevboxdrvkernelmo

I was looking for Ubuntu Linux system management, and I want to change the topic. First, a video card is accelerated. Then we can see the VBox. I always wanted to install a virtual machine, so I directly

Sudo apt-get install virtualbox

It can be run, but the prompt "No kernel Module: VirtualBox kernel driver not installed" is displayed when the VM is created. the vboxdrv kernel module was either not loaded or/dev/vboxdrv was not created for some reason. please install the virtualbox-ose-modules package for your kernel and execute '/etc/init. d/vboxdrv start' as root.

Therefore, first try: sudo/etc/init. d/vboxdrv setup or start

No. We had to re-compile the kernel by following the following source code:

Sudo apt-get install virtualbox-ose-source

Sudo tar-xjvf virtualbox *. bz2

Cd modules/virtualbox-ose

Sudo./build_in_tmp install

The headers and module corresponding to the Linux kernel source code are required in the last step. Reuse

Sudo apt-get install linux-headers-$ (uname-r)

Sudo apt-get install linux-restricted-modules-$ (uname-r)

The former is not. It's a little weird. But I don't think much about it, but I just installed it. It seems that the linux-headers-2.6.22-14-rt is also prompted to depend on the linux-headers-2.6.22. The latter can be apt, which is much simpler.

But the VBox still cannot be compiled. I thought the newly installed kernel needs to be restarted. However, Gnome cannot be started after restart. The log shows that the cause is Failed to load module "wfb" (module does not exist, 0), which eventually leads to no screens found. Without the graphic interface, I had to go back to Windows and know that this was a Bug: the library used by nVidia-gxl was not found in 2.6.les of 2.6.22. But the website shows that this Bug has been fixed. Isn't the apt source too old? I changed the official source, and there was no nVidia-gxl.

Later, I gradually discovered that I had never distinguished feisy gutsy and hard, which correspond to ubuntu7.04 7.1 and 8.04 respectively. I went back and looked at the original sources. list and used hard. It's no wonder apt-get often has some strange problems. After correction, both modules and nVidia-gxl are installed. This is why headers cannot be found. Ignorance reminds me of a sentence from Gump: Stupid people do stupid things.

Then, the VBox and OK are compiled smoothly. I am also prompted about the file access permission problem, so I am entangled in the-G parameter of The usermod command, and finally found that it is better to directly modify/etc/group.

Install XP successfully. It was easy to set up file sharing between the host and the client, but I didn't understand at first what VBox did to put the plug-in to the XP Virtual optical drive to install VirtualBox Guest Additions iso, later, I thought that I had to install it in XP. Then it is easy to set a shared folder in VirtualBox, and then map the folder to the network drive in XP. It seems that the Host and Guest share files in a virtual network?

As a result, I copied a video and played it at a speed similar to that in windows, but the screen was too small to be full-screen. Let's talk about it later. It seems that video card acceleration is still effective. It turns out that many firefox cards won't work, but now it's much better.