[Fixed] GP Fault in vboxdrv SUPR0QueryVTCaps

Postings relating to old VirtualBox pre-releases
Post Reply
joshuadfvb
Posts: 3
Joined: 2. Jun 2015, 13:08

[Fixed] GP Fault in vboxdrv SUPR0QueryVTCaps

Post by joshuadfvb »

Hi,

I've installed VirtualBox 5.0.0_RC1 on Ubuntu 14.04 running on an Intel i3 4005U which is a Haswell core but does not have IOMMU (VT-d).

The modules compile and load file, but when I attempt to use VirtualBox, I get a general protection fault in what looks like IOMMU query in SUPR0QueryVTCaps.
e.g. run:
sudo VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.0.0_RC1-100731.vbox-extpack

kern.log shows:

Code: Select all

Jun  2 05:59:24 myhost kernel: [ 1236.957059] vboxdrv: module verification failed: signature and/or  required key missing - tainting kernel
Jun  2 05:59:24 myhost kernel: [ 1236.962536] vboxdrv: Found 4 processor cores
Jun  2 05:59:24 myhost kernel: [ 1236.978567] vboxdrv: TSC mode is Invariant, tentative frequency 1696071695 Hz
Jun  2 05:59:24 myhost kernel: [ 1236.978571] vboxdrv: Successfully loaded version 5.0.0_RC1 (interface 0x00230000)
Jun  2 05:59:24 myhost kernel: [ 1236.995312] __add_probed_i2c_device failed to register device 8-4a
Jun  2 05:59:24 myhost kernel: [ 1236.996047] __add_probed_i2c_device failed to register device 8-44
Jun  2 05:59:24 myhost kernel: [ 1236.996058] platform chromeos_laptop: Driver chromeos_laptop requests probe deferral
Jun  2 05:59:24 myhost kernel: [ 1237.182609] VBoxNetFlt: Successfully started.
Jun  2 05:59:24 myhost kernel: [ 1237.184393] VBoxNetAdp: Successfully started.
Jun  2 05:59:24 myhost kernel: [ 1237.186368] VBoxPciLinuxInit
Jun  2 05:59:24 myhost kernel: [ 1237.189124] vboxpci: IOMMU not found (not registered)
Jun  2 06:02:12 myhost kernel: [ 1405.040376] general protection fault: 0000 [#1] SMP 
Jun  2 06:02:12 myhost kernel: [ 1405.040404] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_iso8859_1 ctr ccm dm_crypt joydev cyapa intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp chromeos_laptop kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel dm_multipath scsi_dh arc4 ath9k aesni_intel snd_hda_codec_hdmi ath9k_common aes_x86_64 lrw snd_hda_codec_realtek gf128mul glue_helper ath9k_hw snd_hda_codec_generic ablk_helper cryptd ath mac80211 snd_hda_intel snd_hda_controller snd_hda_codec serio_raw snd_hwdep snd_pcm cfg80211 snd_seq_midi snd_seq_midi_event uvcvideo snd_rawmidi videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common snd_seq ath3k videodev snd_seq_device snd_timer media snd btusb lpc_ich shpchp dw_dmac_pci soundcore i2c_designware_pci tpm_infineon dw_dmac dw_dmac_core 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_platform mac_hid bnep rfcomm bluetooth parport_pc ppdev lp parport btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage i915 i2c_algo_bit drm_kms_helper drm ahci libahci video sdhci_acpi sdhci
Jun  2 06:02:12 myhost kernel: [ 1405.040908] CPU: 2 PID: 5992 Comm: nspr-2 Tainted: G           OE  3.17.6-031706-generic #201412071535
Jun  2 06:02:12 myhost kernel: [ 1405.040949] Hardware name: Acer Peppy, BIOS          08/13/2014
Jun  2 06:02:12 myhost kernel: [ 1405.040975] task: ffff880174573c00 ti: ffff880078e0c000 task.ti: ffff880078e0c000
Jun  2 06:02:12 myhost kernel: [ 1405.041008] RIP: 0010:[<ffffffffc0a566f0>]  [<ffffffffc0a566f0>] SUPR0GetVmxUsability+0x60/0xc0 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041060] RSP: 0018:ffff880078e0fde0  EFLAGS: 00010246
Jun  2 06:02:12 myhost kernel: [ 1405.041084] RAX: 0000000000000007 RBX: 0000000002100800 RCX: 000000000000003a
Jun  2 06:02:12 myhost kernel: [ 1405.041114] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff880078e0fdf7
Jun  2 06:02:12 myhost kernel: [ 1405.041145] RBP: ffff880078e0fde0 R08: 00000000756e6547 R09: 000000000000000d
Jun  2 06:02:12 myhost kernel: [ 1405.041175] R10: 000000006c65746e R11: 0000000049656e69 R12: ffff88007995f028
Jun  2 06:02:12 myhost kernel: [ 1405.041206] R13: 00000000fffff057 R14: ffff8801729c9810 R15: ffffffffc0a950c0
Jun  2 06:02:12 myhost kernel: [ 1405.041237] FS:  00007f4152892700(0000) GS:ffff88017cb00000(0000) knlGS:0000000000000000
Jun  2 06:02:12 myhost kernel: [ 1405.041271] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun  2 06:02:12 myhost kernel: [ 1405.041296] CR2: 00007f4151f859c0 CR3: 0000000078c54000 CR4: 00000000001407e0
Jun  2 06:02:12 myhost kernel: [ 1405.041326] Stack:
Jun  2 06:02:12 myhost kernel: [ 1405.041336]  ffff880078e0fe18 ffffffffc0a5a317 00ffffffc0a68a75 00000001ffffffff
Jun  2 06:02:12 myhost kernel: [ 1405.041370]  000000000000001c ffff88007995f010 000000000000001c ffff880078e0fe90
Jun  2 06:02:12 myhost kernel: [ 1405.041404]  ffffffffc0a5a598 000000000000001c ffff880078e0fe78 ffffffffc0a68a75
Jun  2 06:02:12 myhost kernel: [ 1405.041439] Call Trace:
Jun  2 06:02:12 myhost kernel: [ 1405.041458]  [<ffffffffc0a5a317>] SUPR0QueryVTCaps+0x207/0x2a0 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041493]  [<ffffffffc0a5a598>] supdrvIOCtl+0x1e8/0x2fe0 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041530]  [<ffffffffc0a68a75>] ? rtR0MemAllocEx+0x175/0x240 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041564]  [<ffffffffc0a56547>] VBoxDrvLinuxIOCtl_5_0_0+0x127/0x230 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041598]  [<ffffffff811fc235>] do_vfs_ioctl+0x75/0x2c0
Jun  2 06:02:12 myhost kernel: [ 1405.041623]  [<ffffffff811ea2c8>] ? vfs_read+0x108/0x180
Jun  2 06:02:12 myhost kernel: [ 1405.041650]  [<ffffffff81206795>] ? __fget_light+0x25/0x70
Jun  2 06:02:12 myhost kernel: [ 1405.041675]  [<ffffffff811fc511>] SyS_ioctl+0x91/0xb0
Jun  2 06:02:12 myhost kernel: [ 1405.041699]  [<ffffffff817a65ed>] system_call_fastpath+0x1a/0x1f
Jun  2 06:02:12 myhost kernel: [ 1405.041724] Code: 7c 80 e6 40 75 65 84 c0 0f 1f 00 74 67 31 c0 31 d2 48 85 ff 74 02 88 17 5d c3 90 48 83 c8 07 b9 3a 00 00 00 48 89 c2 48 c1 ea 20 <0f> 30 0f 32 48 c1 e2 20 89 c1 b8 53 f0 ff ff 48 09 d1 31 d2 f6 
Jun  2 06:02:12 myhost kernel: [ 1405.041856] RIP  [<ffffffffc0a566f0>] SUPR0GetVmxUsability+0x60/0xc0 [vboxdrv]
Jun  2 06:02:12 myhost kernel: [ 1405.041893]  RSP <ffff880078e0fde0>
Jun  2 06:02:12 myhost kernel: [ 1405.047556] ---[ end trace c7d5fdc3edebc556 ]---
My /proc/cpuinfo attached as well, anything else I can provide or try out?
Attachments
proc-cpuinfo-i4005U.txt
(3.95 KiB) Downloaded 50 times
Technologov
Volunteer
Posts: 3342
Joined: 10. May 2007, 16:59
Location: Israel

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by Technologov »

Please attach vbox.log (right click on VM->show log) and output of "lsmod | sort".
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by Ramshankar »

Thanks for the report, I'll have a look.

It might be related to your BIOS not setting up the VMX feature MSR properly, will have to investigate.
Oracle Corp.
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by Ramshankar »

I think I found the problem, however I cannot test this easily.

Would you be willing to try a test build?
Oracle Corp.
Technologov
Volunteer
Posts: 3342
Joined: 10. May 2007, 16:59
Location: Israel

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by Technologov »

If he's in a BETA forum, he's already trying a test build.
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all
Contact:

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by michaln »

Technologov wrote:If he's in a BETA forum, he's already trying a test build.
Maybe you could let us decide what's a test build and what's not?
joshuadfvb
Posts: 3
Joined: 2. Jun 2015, 13:08

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by joshuadfvb »

Ramshankar wrote:I think I found the problem, however I cannot test this easily.

Would you be willing to try a test build?

I would be happy to.
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by Ramshankar »

joshuadfvb wrote:
Ramshankar wrote:I think I found the problem, however I cannot test this easily.
Would you be willing to try a test build?
I would be happy to.
Here you go (64-bit linux package), the link will automatically expire in ~14 days:
https://www.virtualbox.org/download/tes ... _amd64.run

Let me know if this helps and thanks a lot for testing!
Oracle Corp.
joshuadfvb
Posts: 3
Joined: 2. Jun 2015, 13:08

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by joshuadfvb »

Ramshankar wrote:
joshuadfvb wrote:
Ramshankar wrote:I think I found the problem, however I cannot test this easily.
https://www.virtualbox.org/download/tes ... _amd64.run

Let me know if this helps and thanks a lot for testing!
This build worked for me, thanks!

Since I've got your attention, I also have a feature request. :)
It would be awesome to have feature detection output, e.g. whether the CPU supports VT-d and so on, especially with 5.0 and PV.
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all
Contact:

Re: GP Fault in vboxdrv SUPR0QueryVTCaps

Post by michaln »

joshuadfvb wrote:It would be awesome to have feature detection output, e.g. whether the CPU supports VT-d and so on, especially with 5.0 and PV.
Everything relevant is in VBox.log, so that's probably not what you're talking about. What are you talking about? What does "feature detection output" mean to you?
Post Reply