Discussions related to using VirtualBox on Linux hosts.
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 15. Aug 2012, 20:44
Hello!
Since the new verson I can not install Virtualbox on Debian. I installed DKMS, the suggested packages and linux headers:
Code: Select all
dpkg -l | grep 3.4.6
ii linux-headers-3.4.6 1.0 i386 Header files related to Linux kernel, specifically,
ii linux-image-3.4.6 1.0 i386 Linux kernel binary image for version 3.4.6
I got the next error:
Code: Select all
vboxdrv: Found 4 processor cores.
BUG: unable to handle kernel NULL pointer dereference at 00000900
IP: [<fcbdcb6a>] VBoxHost_RTR0MemObjFree+0x294/0x294 [vboxdrv]
*pdpt = 0000000031d34001 *pde = 0000000000000000
Oops: 0000 [#1] SMP
Modules linked in: vboxdrv(O+) i915 video drm_kms_helper drm i2c_algo_bit decnet aes_i586 aes_generic ipv6 xfs exportfs it87 sha1_generic ecb ppp_mppe ppp_generic slhc hwmon_vid firewire_sbp2 loop fuse arc4 zd1211rw mac80211 snd_virtuoso snd_oxygen_lib cfg80211 rfkill snd_mpu401_uart snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event acpi_cpufreq mperf snd_rawmidi snd_seq snd_timer snd_seq_device snd soundcore freq_table intel_agp intel_gtt coretemp iTCO_wdt pcspkr agpgart button processor evdev microcode i2c_i801 i2c_core thermal_sys ext3 mbcache jbd usbhid hid firewire_ohci firewire_core ata_generic crc_itu_t uhci_hcd r8169 mii ehci_hcd pata_jmicron usbcore usb_common [last unloaded: scsi_wait_scan]
Pid: 6979, comm: modprobe Tainted: G O 3.4.6 #1 Gigabyte Technology Co., Ltd. H55M-UD2H/H55M-UD2H
EIP: 0060:[<fcbdcb6a>] EFLAGS: 00210293 CPU: 3
EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv]
EAX: f36c9000 EBX: f36c9000 ECX: 336c9000 EDX: 00000002
ESI: fcbf66e8 EDI: 00000900 EBP: 00000000 ESP: f3ad7e9c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
CR0: 8005003b CR2: 00000900 CR3: 31f49000 CR4: 000007f0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Process modprobe (pid: 6979, ti=f3ad6000 task=f3686530 task.ti=f3ad6000)
Stack:
fcbd7fe1 f77d95d0 00000000 f77d95d0 c1038772 f1f750b0 00200292 c103a39d
f1f753a2 00200292 00200202 00200202 00000000 00000008 f3ad7ef8 00000018
00000008 80000000 00000000 f37f6140 00000001 fcbff000 fcbdbc91 f38c2960
Call Trace:
[<fcbd7fe1>] ? supdrvInitDevExt+0xdd/0x72d [vboxdrv]
[<c1038772>] ? ttwu_do_wakeup+0xb/0xa4
[<c103a39d>] ? try_to_wake_up+0x1a4/0x1ae
[<fcbff000>] ? 0xfcbfefff
[<fcbdbc91>] ? VBoxHost_RTMemAllocTag+0xe/0x22 [vboxdrv]
[<fcbdfb29>] ? VBoxHost_RTSpinlockCreate+0xc/0x2f [vboxdrv]
[<fcbff000>] ? 0xfcbfefff
[<fcbff050>] ? VBoxDrvLinuxInit+0x50/0xc7 [vboxdrv]
[<c1001146>] ? do_one_initcall+0x66/0x104
[<c104f298>] ? sys_init_module+0x1288/0x145e
[<c12317d0>] ? sysenter_do_call+0x12/0x26
Code: fe ff ff e9 cf fe ff ff 8b 4a 1c 85 c9 0f 84 47 ff ff ff 8d 34 8d fc ff ff ff 89 4c 24 04 e9 5c ff ff ff 83 c4 08 5b 5e 5f 5d c3 <8b> 0f 8b 47 04 8d 91 00 10 00 00 81 fa ff 1f 00 00 76 45 81 39
EIP: [<fcbdcb6a>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] SS:ESP 0068:f3ad7e9c
CR2: 0000000000000900
Please help me to solve the problem.
TJ
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 15. Aug 2012, 21:04
Where did your VirtualBox come from (debian repo or virtualbox.org) and what is the version?
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 15. Aug 2012, 22:40
I downloaded from virtualbox site the 4.1.18 version.
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 15. Aug 2012, 23:07
Version 4.1.18 should work at least through 3.5-rc1
What is the full name of the download?
When you say you installed packages, what were they?
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 15. Aug 2012, 23:17
Name: virtualbox-4.1_4.1.18-78361~Debian~wheezy_i386.deb
Packages: dkms build-essential
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 15. Aug 2012, 23:21
Post the /var/log/vbox-install.log (as an attachment)
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 15. Aug 2012, 23:35
Here is the file.
Attachments
vbox-install.log
(1.2 KiB) Downloaded 34 times
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 15. Aug 2012, 23:45
Strange. Log says it is installed. Have you tried to reboot the host?
Did you add your <user name> to the vboxusers group?
Also post the results of uname -a
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 15. Aug 2012, 23:50
I give a chance to reinstall and reboot however I tried it.
Code: Select all
tankerjedi@napsugar:~$ groups
tankerjedi lp cdrom audio video postgres scanner vboxusers
Code: Select all
tankerjedi@napsugar:~$ uname -a
Linux napsugar 3.4.6 #1 SMP Fri Jul 27 19:33:47 CEST 2012 i686 GNU/Linux
ps: It did not help. I reached only that it freezed my computer.
Last edited by
TJ on 16. Aug 2012, 00:02, edited 1 time in total.
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 16. Aug 2012, 00:01
This isn't nested is it?
I mean the host is on metal, not another virtualizer.
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 16. Aug 2012, 00:06
This is my simple desktop computer, no other virtual machine. I would like to simply run on my comp VBox.
For years I could upgrade to newer versions without problem, and now olders (4.1.14) do not work too.
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 16. Aug 2012, 00:15
I don't see a reason why it should not work, at least from what I see.
I would try to purge the install and reboot then install again. There must be something that is corrupting the install.
Your guest/s should remain intact but I always suggest backing up first as you should be backing up regularly anyway.
Watch carefully for any error/s on install and post exact errors if you see any.
Worst case you go back to the previous version and post a ticket at
bugtracker
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 16. Aug 2012, 00:24
I purged many times:
Code: Select all
apt-get --purge remove virtualbox-4.1
I got some strange messages. Maybe it means something.
Code: Select all
incorrect gamma=(0/100000)
incorrect gamma=(0/100000)
incorrect gamma=(0/100000)
incorrect gamma=(0/100000)
If I remember well, I tried to install a 4.0 version, but it was the same error after these. Besides before this upgrade, I did not have to install linux-headers and dkms to use older versions of VBox.
Perryg
Site Moderator
Posts: 34369 Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX
Post
by Perryg » 16. Aug 2012, 00:35
I really don't like what I am seeing and hearing.
First linux-headers have always been a requirement because you need them to build the VBox mods. It may have been installed and you didn't know it if you installed using a deb file.
dkms is only needed to keep the headers and the external mod built when your kernel gets upgraded.
What did you use to install VirtualBox? dpkg, gdebi. Etc.?
TJ
Posts: 8 Joined: 15. Aug 2012, 20:40
Post
by TJ » 16. Aug 2012, 08:15
I always used dpkg.
It is very annoying, because I have some imoprtant data in my VBox machine.