host resets on starting guest machine in virtualbox/crouton #1211

Closed
MikRoscope opened this Issue Nov 22, 2014 · 12 comments

Comments

Projects
None yet
4 participants
@MikRoscope

I just changed the ssd on my Acer C720 and did a clean chromeos recovery all the way to virtualbox installation in crouton with trusty xfce.
vitrualbox drivers are loaded as far as I can check with sudo /etc/init.d/vboxdrv start .
There is no OS installed on the guest machine, it's merely a predefined configurations for winxp. Simply trying to start the guest machine resets the chromebook. There is no log file in ~/VirtualBox VMs. Is there somewhere a log file written by crouton?

@divx118

This comment has been minimized.

Show comment
Hide comment
@divx118

divx118 Nov 22, 2014

Contributor

Anything in dmesg output when you start the guest machine?
With cat /proc/modules you can see if the kernel drivers are loaded. Also no interesting logs in /var/log in the chroot?

Contributor

divx118 commented Nov 22, 2014

Anything in dmesg output when you start the guest machine?
With cat /proc/modules you can see if the kernel drivers are loaded. Also no interesting logs in /var/log in the chroot?

@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Nov 22, 2014

sorry for being stupid, but when I start the guest machine chromebook resets immediately and I only have dmesg after system reboot and logging into chroot again:

$ dmesg | grep vbox
[   34.224046] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxdrv.ko" pid=13786 cmdline="modprobe vboxdrv"
[   34.238995] vboxdrv: Found 2 processor cores.
[   34.239649] vboxdrv: fAsync=0 offMin=0x1a0 offMax=0x1664
[   34.240136] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   34.240149] vboxdrv: Successfully loaded version 4.3.20 (interface 0x001a0008).
[   34.241563] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxpci.ko" pid=13788 cmdline="modprobe vboxpci"
[   34.243094] vboxpci: pci-stub module not available, cannot detach PCI devices
[   34.243107] vboxpci: IOMMU not found (not compiled)
[   34.244642] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetadp.ko" pid=13789 cmdline="modprobe vboxnetadp"
[   34.248276] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetflt.ko" pid=13790 cmdline="modprobe vboxnetflt"
$ cat /proc/modules | grep vbox
vboxnetflt 23697 0 - Live 0x0000000000000000 (O)
vboxnetadp 25443 0 - Live 0x0000000000000000 (O)
vboxpci 19047 0 - Live 0x0000000000000000 (O)
vboxdrv 304421 3 vboxnetflt,vboxnetadp,vboxpci, Live 0x0000000000000000 (O)

I have one item in /var/log modified at the reset time with zero bytes

-rw-rw-r--  1 root utmp        0 Nov 22 15:15 wtmp

sorry for being stupid, but when I start the guest machine chromebook resets immediately and I only have dmesg after system reboot and logging into chroot again:

$ dmesg | grep vbox
[   34.224046] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxdrv.ko" pid=13786 cmdline="modprobe vboxdrv"
[   34.238995] vboxdrv: Found 2 processor cores.
[   34.239649] vboxdrv: fAsync=0 offMin=0x1a0 offMax=0x1664
[   34.240136] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   34.240149] vboxdrv: Successfully loaded version 4.3.20 (interface 0x001a0008).
[   34.241563] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxpci.ko" pid=13788 cmdline="modprobe vboxpci"
[   34.243094] vboxpci: pci-stub module not available, cannot detach PCI devices
[   34.243107] vboxpci: IOMMU not found (not compiled)
[   34.244642] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetadp.ko" pid=13789 cmdline="modprobe vboxnetadp"
[   34.248276] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetflt.ko" pid=13790 cmdline="modprobe vboxnetflt"
$ cat /proc/modules | grep vbox
vboxnetflt 23697 0 - Live 0x0000000000000000 (O)
vboxnetadp 25443 0 - Live 0x0000000000000000 (O)
vboxpci 19047 0 - Live 0x0000000000000000 (O)
vboxdrv 304421 3 vboxnetflt,vboxnetadp,vboxpci, Live 0x0000000000000000 (O)

I have one item in /var/log modified at the reset time with zero bytes

-rw-rw-r--  1 root utmp        0 Nov 22 15:15 wtmp
@divx118

This comment has been minimized.

Show comment
Hide comment
@divx118

divx118 Nov 22, 2014

Contributor

Hmm well I guess the reboot is because of a kernel panic, would be interesting to know why. Normally there also should be a log from virtualbox in the hidden dir ~/.VirtualBox from starting the guest.
Else see if you can play with some settings of the guest machine, disabling some stuff until it starts.

Contributor

divx118 commented Nov 22, 2014

Hmm well I guess the reboot is because of a kernel panic, would be interesting to know why. Normally there also should be a log from virtualbox in the hidden dir ~/.VirtualBox from starting the guest.
Else see if you can play with some settings of the guest machine, disabling some stuff until it starts.

@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Nov 22, 2014

I think the guest doesn't even start since there is no hidden directory or any log. I only have this:

$ ls -la  ~ | grep tual
drwxrwxr-x  3 ***  ***     4096 Nov 22 11:27 VirtualBox VMs

I purged virtualbox and installed it again with dpkg -i. Now I have

$ find /lib/modules -name vboxdrv.ko
/lib/modules/3.8.11/misc/vboxdrv.ko
/lib/modules/3.8.0-31-generic/misc/vboxdrv.ko

with uname -r being 3.8.11. If I purge virtualbox again, 3.8.0-31-generic will be also removed. Now with two kernels, rc.local does not work so following our previous discussion here, I removed the unused kernel. Then rc.local works and vbox drivers load. However it is still causing the reboot.

I think the guest doesn't even start since there is no hidden directory or any log. I only have this:

$ ls -la  ~ | grep tual
drwxrwxr-x  3 ***  ***     4096 Nov 22 11:27 VirtualBox VMs

I purged virtualbox and installed it again with dpkg -i. Now I have

$ find /lib/modules -name vboxdrv.ko
/lib/modules/3.8.11/misc/vboxdrv.ko
/lib/modules/3.8.0-31-generic/misc/vboxdrv.ko

with uname -r being 3.8.11. If I purge virtualbox again, 3.8.0-31-generic will be also removed. Now with two kernels, rc.local does not work so following our previous discussion here, I removed the unused kernel. Then rc.local works and vbox drivers load. However it is still causing the reboot.

@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Nov 22, 2014

While playing with guest machine configuration, I remembered that I could not select VT-x option previously with a message like "Virtualization is disabled in your BIOS". Back then I followed the instructions to repack kernel to Enable VT_x. With the old ssd, virtualbox and VT-x was working.
However, now after changind the ssd and installing everything from scratch I see that in virtualbox, VT-x is still selectable. I followed the steps in the guide above while replacing disablevmx=off with disablevmx=on in step 6 in order to disable VT-x again (not sure that's the way to do it). But after reboot, VT-x option is still selectable in the virtualbox without any error or warning. I want to disable VT-x completely to see whether that causes the reboot or not.

While playing with guest machine configuration, I remembered that I could not select VT-x option previously with a message like "Virtualization is disabled in your BIOS". Back then I followed the instructions to repack kernel to Enable VT_x. With the old ssd, virtualbox and VT-x was working.
However, now after changind the ssd and installing everything from scratch I see that in virtualbox, VT-x is still selectable. I followed the steps in the guide above while replacing disablevmx=off with disablevmx=on in step 6 in order to disable VT-x again (not sure that's the way to do it). But after reboot, VT-x option is still selectable in the virtualbox without any error or warning. I want to disable VT-x completely to see whether that causes the reboot or not.

@divx118

This comment has been minimized.

Show comment
Hide comment
@divx118

divx118 Nov 22, 2014

Contributor

You can always select VT-x in VirtualBox, it just doesn't work if you don't
do the workaround.

On Sat, Nov 22, 2014 at 5:10 PM, MikRoscope notifications@github.com
wrote:

While playing with guest machine configuration, I remembered that I could
not select VT-x option previously with a message like "Virtualization is
disabled in your BIOS". Back then I followed the instructions to repack
kernel to Enable VT_x
https://github.com/dnschneid/crouton/wiki/Repack-kernel-to-Enable-VT_x-for-Virtualbox.
With the old ssd, virtualbox and VT-x was working.
However, now after changind the ssd and installing everything from scratch
I see that in virtualbox, VT-x is still selectable. I followed the steps in
the guide above while replacing disablevmx=off with disablevmx=on in step
6 in order to disable VT-x again (not sure that's the way to do it). But
after reboot, VT-x option is still selectable in the virtualbox without any
error or warning. I want to disable VT-x completely to see whether that
causes the reboot or not.


Reply to this email directly or view it on GitHub
#1211 (comment).

Contributor

divx118 commented Nov 22, 2014

You can always select VT-x in VirtualBox, it just doesn't work if you don't
do the workaround.

On Sat, Nov 22, 2014 at 5:10 PM, MikRoscope notifications@github.com
wrote:

While playing with guest machine configuration, I remembered that I could
not select VT-x option previously with a message like "Virtualization is
disabled in your BIOS". Back then I followed the instructions to repack
kernel to Enable VT_x
https://github.com/dnschneid/crouton/wiki/Repack-kernel-to-Enable-VT_x-for-Virtualbox.
With the old ssd, virtualbox and VT-x was working.
However, now after changind the ssd and installing everything from scratch
I see that in virtualbox, VT-x is still selectable. I followed the steps in
the guide above while replacing disablevmx=off with disablevmx=on in step
6 in order to disable VT-x again (not sure that's the way to do it). But
after reboot, VT-x option is still selectable in the virtualbox without any
error or warning. I want to disable VT-x completely to see whether that
causes the reboot or not.


Reply to this email directly or view it on GitHub
#1211 (comment).

@drinkcat

This comment has been minimized.

Show comment
Hide comment
@drinkcat

drinkcat Nov 22, 2014

Collaborator

@MikRoscope : You can double check if disablevmx parameter is set or not using cat /proc/cmdline.

Also, can you have a look at sudo cat /dev/pstore/console-ramoops after a reset? This should contain the kernel logs from the previous reboot, including the panic message.

Collaborator

drinkcat commented Nov 22, 2014

@MikRoscope : You can double check if disablevmx parameter is set or not using cat /proc/cmdline.

Also, can you have a look at sudo cat /dev/pstore/console-ramoops after a reset? This should contain the kernel logs from the previous reboot, including the panic message.

@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Nov 22, 2014

@drinkcat I double checked as you said. Right now it's on disablevmx=on. I tried disablevmx=off as well, in both cases system reboots.

$ cat /proc/cmdline
cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=3fab1bc0-c8b8-de41-ba0f-53ba462e4931/PARTNROFF=1 hashtree=PARTUUID=3fab1bc0-c8b8-de41-ba0f-53ba462e4931/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=3897918e4d421c10a12ab9246bc6750c302daba7 salt=74af5461f14c59db05156c0d064155837f4f30bfa3973aca7dae33cabf935a02" noinitrd vt.global_cursor_default=0 kern_guid=3fab1bc0-c8b8-de41-ba0f-53ba462e4931 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3  disablevmx=on

Thanks for the tip, finally there are some logs before reboot. It says kernel panic! I think I copied the part from starting chroot until reboot:

$ sudo cat /dev/pstore/console-ramoops
[ 4352.121281] systemd-logind[27079]: New seat seat0.
[ 4352.131681] systemd-logind[27079]: New session c1 of user root.
[ 4352.219229] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxdrv.ko" pid=27115 cmdline="modprobe vboxdrv"
[ 4352.235329] vboxdrv: fAsync=0 offMin=0x23e offMax=0xbaa
[ 4352.235426] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 4352.238068] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxpci.ko" pid=27117 cmdline="modprobe vboxpci"
[ 4352.240823] vboxpci: pci-stub module not available, cannot detach PCI devices
[ 4352.240837] vboxpci: IOMMU not found (not compiled)
[ 4352.242311] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetadp.ko" pid=27118 cmdline="modprobe vboxnetadp"
[ 4352.245488] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetflt.ko" pid=27119 cmdline="modprobe vboxnetflt"
[ 4352.270002] systemd-logind[27079]: Removed session c1.
[ 4352.281937] systemd-logind[27079]: New session c2 of user bigfoot.
[ 4378.970768] systemd-logind[27079]: Removed session c2.
[ 4378.980841] systemd-logind[27079]: New session c3 of user root.
[ 4530.637598] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 4531.037412] systemd-logind[28088]: New seat seat0.
[ 4531.051005] systemd-logind[28088]: New session c1 of user root.
[ 4531.141934] systemd-logind[28088]: Removed session c1.
[ 4531.157774] systemd-logind[28088]: New session c2 of user bigfoot.
[ 4545.580807] systemd-logind[28088]: Removed session c2.
[ 4545.593265] systemd-logind[28088]: New session c3 of user root.
[ 4960.475354] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 4960.886038] systemd-logind[29181]: New seat seat0.
[ 4960.901865] systemd-logind[29181]: New session c1 of user bigfoot.
[ 4960.989114] systemd-logind[29181]: Removed session c1.
[ 4961.006278] systemd-logind[29181]: New session c2 of user bigfoot.
[ 4961.111767] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0
[ 4963.915279] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold
[ 4977.879443] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 4980.643065] BUG: unable to handle kernel NULL pointer dereference at 0000000000000024
[ 4980.643100] IP: [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.643138] PGD 4d1a6067 PUD 619ef067 PMD 0 
[ 4980.643167] Oops: 0000 [#1] SMP 
[ 4980.645546] gsmi: Log Shutdown Reason 0x03
[ 4980.645560] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxpci(O) vboxdrv(O) i2c_dev snd_hda_codec_realtek memconsole snd_hda_codec_hdmi snd_hda_intel snd_hda_codec isl29018(C) snd_hwdep snd_pcm snd_page_alloc industrialio snd_timer zram(C) lzo_compress lzo_decompress zsmalloc(C) fuse nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ath9k_btcoex ath9k_common_btcoex ath9k_hw_btcoex ath mac80211 cfg80211 ath3k btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev ppp_async ppp_generic slhc tun
[ 4980.645864] CPU 1 
[ 4980.645878] Pid: 29614, comm: VirtualBox Tainted: G         C O 3.8.11 #1
[ 4980.645900] RIP: 0010:[<ffffffffc025a197>]  [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.645937] RSP: 0018:ffff88006188fbf0  EFLAGS: 00010202
[ 4980.645952] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 00000000002b3332
[ 4980.645970] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800624a20c8
[ 4980.645988] RBP: ffff88006188fc18 R08: 0000000000000000 R09: 0000000000000000
[ 4980.646005] R10: fefefefefefefeff R11: 0000000000000fe0 R12: ffff8800624a2000
[ 4980.646023] R13: ffff8800624a20c8 R14: ffffffffb0a400f0 R15: ffff88004884b838
[ 4980.646041] FS:  00007f5884575740(0000) GS:ffff880100300000(0000) knlGS:0000000000000000
[ 4980.646061] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4980.646077] CR2: 0000000000000024 CR3: 0000000061929000 CR4: 00000000000407e0
[ 4980.646095] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4980.646113] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4980.646131] Process VirtualBox (pid: 29614, threadinfo ffff88006188e000, task ffff8800619624e0)
[ 4980.646151] Stack:
[ 4980.646161]  00000000002b3332 ffffffffc02864d0 ffff8800624a2000 0000000000000038
[ 4980.646197]  ffffffffb0a400f0 ffff88006188fc28 ffffffffc025a20b ffff88006188fc60
[ 4980.646232]  ffffffffb066c702 ffff8801002b2700 0000000000000000 ffff88004884b838
[ 4980.646271] Call Trace:
[ 4980.646296]  [<ffffffffc025a20b>] VBoxDrvLinuxCreateSys+0x1a/0x1c [vboxdrv]
[ 4980.646322]  [<ffffffffb066c702>] misc_open+0x12b/0x190
[ 4980.646342]  [<ffffffffb04eb853>] chrdev_open+0x14c/0x187
[ 4980.646361]  [<ffffffffb04eb707>] ? cdev_put+0x23/0x23
[ 4980.646381]  [<ffffffffb04e664b>] do_dentry_open+0x18b/0x23d
[ 4980.646401]  [<ffffffffb04f16a6>] ? __inode_permission+0x73/0x81
[ 4980.646421]  [<ffffffffb04e6730>] finish_open+0x33/0x3d
[ 4980.646440]  [<ffffffffb04f3379>] do_last.isra.38+0x806/0x9cc
[ 4980.646461]  [<ffffffffb04f3619>] path_openat.isra.39+0xda/0x359
[ 4980.646482]  [<ffffffffb04f441b>] do_filp_open+0x4b/0xa6
[ 4980.646504]  [<ffffffffb08b1338>] ? _raw_spin_unlock+0xe/0x10
[ 4980.646524]  [<ffffffffb04fecc9>] ? __alloc_fd+0xf0/0xff
[ 4980.646544]  [<ffffffffb04e75eb>] do_sys_open+0x82/0x161
[ 4980.646563]  [<ffffffffb04e76eb>] sys_open+0x21/0x23
[ 4980.646581]  [<ffffffffb08b2142>] system_call_fastpath+0x16/0x1b
[ 4980.646597] Code: 8b 75 d8 8b 70 18 48 8b b8 90 00 00 00 e8 50 97 22 f0 41 89 86 84 06 00 00 eb 2c 65 48 8b 04 25 c0 b8 00 00 48 8b 80 48 04 00 00 <8b> 70 24 48 8b b8 90 00 00 00 e8 ea 96 22 f0 85 c0 0f 84 6c ff 
[ 4980.646930] RIP  [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.646962]  RSP <ffff88006188fbf0>
[ 4980.646974] CR2: 0000000000000024
[ 4980.647026] ---[ end trace da403b211a75e3c7 ]---
[ 4980.655864] Kernel panic - not syncing: Fatal exception
[ 4980.655888] Kernel Offset: 0x2f400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 4980.656015] gsmi: Log Shutdown Reason 0x02
[ 4980.664758] ACPI MEMORY or I/O RESET_REG.

@drinkcat I double checked as you said. Right now it's on disablevmx=on. I tried disablevmx=off as well, in both cases system reboots.

$ cat /proc/cmdline
cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=3fab1bc0-c8b8-de41-ba0f-53ba462e4931/PARTNROFF=1 hashtree=PARTUUID=3fab1bc0-c8b8-de41-ba0f-53ba462e4931/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=3897918e4d421c10a12ab9246bc6750c302daba7 salt=74af5461f14c59db05156c0d064155837f4f30bfa3973aca7dae33cabf935a02" noinitrd vt.global_cursor_default=0 kern_guid=3fab1bc0-c8b8-de41-ba0f-53ba462e4931 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3  disablevmx=on

Thanks for the tip, finally there are some logs before reboot. It says kernel panic! I think I copied the part from starting chroot until reboot:

$ sudo cat /dev/pstore/console-ramoops
[ 4352.121281] systemd-logind[27079]: New seat seat0.
[ 4352.131681] systemd-logind[27079]: New session c1 of user root.
[ 4352.219229] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxdrv.ko" pid=27115 cmdline="modprobe vboxdrv"
[ 4352.235329] vboxdrv: fAsync=0 offMin=0x23e offMax=0xbaa
[ 4352.235426] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 4352.238068] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxpci.ko" pid=27117 cmdline="modprobe vboxpci"
[ 4352.240823] vboxpci: pci-stub module not available, cannot detach PCI devices
[ 4352.240837] vboxpci: IOMMU not found (not compiled)
[ 4352.242311] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetadp.ko" pid=27118 cmdline="modprobe vboxnetadp"
[ 4352.245488] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.8.11/misc/vboxnetflt.ko" pid=27119 cmdline="modprobe vboxnetflt"
[ 4352.270002] systemd-logind[27079]: Removed session c1.
[ 4352.281937] systemd-logind[27079]: New session c2 of user bigfoot.
[ 4378.970768] systemd-logind[27079]: Removed session c2.
[ 4378.980841] systemd-logind[27079]: New session c3 of user root.
[ 4530.637598] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 4531.037412] systemd-logind[28088]: New seat seat0.
[ 4531.051005] systemd-logind[28088]: New session c1 of user root.
[ 4531.141934] systemd-logind[28088]: Removed session c1.
[ 4531.157774] systemd-logind[28088]: New session c2 of user bigfoot.
[ 4545.580807] systemd-logind[28088]: Removed session c2.
[ 4545.593265] systemd-logind[28088]: New session c3 of user root.
[ 4960.475354] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 4960.886038] systemd-logind[29181]: New seat seat0.
[ 4960.901865] systemd-logind[29181]: New session c1 of user bigfoot.
[ 4960.989114] systemd-logind[29181]: Removed session c1.
[ 4961.006278] systemd-logind[29181]: New session c2 of user bigfoot.
[ 4961.111767] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0
[ 4963.915279] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold
[ 4977.879443] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 4980.643065] BUG: unable to handle kernel NULL pointer dereference at 0000000000000024
[ 4980.643100] IP: [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.643138] PGD 4d1a6067 PUD 619ef067 PMD 0 
[ 4980.643167] Oops: 0000 [#1] SMP 
[ 4980.645546] gsmi: Log Shutdown Reason 0x03
[ 4980.645560] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxpci(O) vboxdrv(O) i2c_dev snd_hda_codec_realtek memconsole snd_hda_codec_hdmi snd_hda_intel snd_hda_codec isl29018(C) snd_hwdep snd_pcm snd_page_alloc industrialio snd_timer zram(C) lzo_compress lzo_decompress zsmalloc(C) fuse nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ath9k_btcoex ath9k_common_btcoex ath9k_hw_btcoex ath mac80211 cfg80211 ath3k btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev ppp_async ppp_generic slhc tun
[ 4980.645864] CPU 1 
[ 4980.645878] Pid: 29614, comm: VirtualBox Tainted: G         C O 3.8.11 #1
[ 4980.645900] RIP: 0010:[<ffffffffc025a197>]  [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.645937] RSP: 0018:ffff88006188fbf0  EFLAGS: 00010202
[ 4980.645952] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 00000000002b3332
[ 4980.645970] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800624a20c8
[ 4980.645988] RBP: ffff88006188fc18 R08: 0000000000000000 R09: 0000000000000000
[ 4980.646005] R10: fefefefefefefeff R11: 0000000000000fe0 R12: ffff8800624a2000
[ 4980.646023] R13: ffff8800624a20c8 R14: ffffffffb0a400f0 R15: ffff88004884b838
[ 4980.646041] FS:  00007f5884575740(0000) GS:ffff880100300000(0000) knlGS:0000000000000000
[ 4980.646061] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4980.646077] CR2: 0000000000000024 CR3: 0000000061929000 CR4: 00000000000407e0
[ 4980.646095] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4980.646113] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4980.646131] Process VirtualBox (pid: 29614, threadinfo ffff88006188e000, task ffff8800619624e0)
[ 4980.646151] Stack:
[ 4980.646161]  00000000002b3332 ffffffffc02864d0 ffff8800624a2000 0000000000000038
[ 4980.646197]  ffffffffb0a400f0 ffff88006188fc28 ffffffffc025a20b ffff88006188fc60
[ 4980.646232]  ffffffffb066c702 ffff8801002b2700 0000000000000000 ffff88004884b838
[ 4980.646271] Call Trace:
[ 4980.646296]  [<ffffffffc025a20b>] VBoxDrvLinuxCreateSys+0x1a/0x1c [vboxdrv]
[ 4980.646322]  [<ffffffffb066c702>] misc_open+0x12b/0x190
[ 4980.646342]  [<ffffffffb04eb853>] chrdev_open+0x14c/0x187
[ 4980.646361]  [<ffffffffb04eb707>] ? cdev_put+0x23/0x23
[ 4980.646381]  [<ffffffffb04e664b>] do_dentry_open+0x18b/0x23d
[ 4980.646401]  [<ffffffffb04f16a6>] ? __inode_permission+0x73/0x81
[ 4980.646421]  [<ffffffffb04e6730>] finish_open+0x33/0x3d
[ 4980.646440]  [<ffffffffb04f3379>] do_last.isra.38+0x806/0x9cc
[ 4980.646461]  [<ffffffffb04f3619>] path_openat.isra.39+0xda/0x359
[ 4980.646482]  [<ffffffffb04f441b>] do_filp_open+0x4b/0xa6
[ 4980.646504]  [<ffffffffb08b1338>] ? _raw_spin_unlock+0xe/0x10
[ 4980.646524]  [<ffffffffb04fecc9>] ? __alloc_fd+0xf0/0xff
[ 4980.646544]  [<ffffffffb04e75eb>] do_sys_open+0x82/0x161
[ 4980.646563]  [<ffffffffb04e76eb>] sys_open+0x21/0x23
[ 4980.646581]  [<ffffffffb08b2142>] system_call_fastpath+0x16/0x1b
[ 4980.646597] Code: 8b 75 d8 8b 70 18 48 8b b8 90 00 00 00 e8 50 97 22 f0 41 89 86 84 06 00 00 eb 2c 65 48 8b 04 25 c0 b8 00 00 48 8b 80 48 04 00 00 <8b> 70 24 48 8b b8 90 00 00 00 e8 ea 96 22 f0 85 c0 0f 84 6c ff 
[ 4980.646930] RIP  [<ffffffffc025a197>] vboxdrvLinuxCreateCommon.isra.1+0x98/0xd9 [vboxdrv]
[ 4980.646962]  RSP <ffff88006188fbf0>
[ 4980.646974] CR2: 0000000000000024
[ 4980.647026] ---[ end trace da403b211a75e3c7 ]---
[ 4980.655864] Kernel panic - not syncing: Fatal exception
[ 4980.655888] Kernel Offset: 0x2f400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 4980.656015] gsmi: Log Shutdown Reason 0x02
[ 4980.664758] ACPI MEMORY or I/O RESET_REG.
@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Nov 25, 2014

Just wanted to say that I have again a working vbox. I did a clean recovery and crouton installation again. Things that I did different this time:

  1. I selected the precise release (last time it was trusty).
  2. Instead of building the kernel headers myself, I used this script (Kudos to @divx118)
  3. Instead of installing vbox with sudo dpkg -i vbox.deb and fixing the dependencies with apt-get install -f, I installed vbox with apt-get as it is explained on https://www.virtualbox.org

Just wanted to say that I have again a working vbox. I did a clean recovery and crouton installation again. Things that I did different this time:

  1. I selected the precise release (last time it was trusty).
  2. Instead of building the kernel headers myself, I used this script (Kudos to @divx118)
  3. Instead of installing vbox with sudo dpkg -i vbox.deb and fixing the dependencies with apt-get install -f, I installed vbox with apt-get as it is explained on https://www.virtualbox.org
@divx118

This comment has been minimized.

Show comment
Hide comment
@divx118

divx118 Nov 25, 2014

Contributor

Maybe something went wrong with the build of the kernel headers... I have virtualbox on trusty and tried the package from the site and the one from ubuntu repo in the past. Both worked for me.

Contributor

divx118 commented Nov 25, 2014

Maybe something went wrong with the build of the kernel headers... I have virtualbox on trusty and tried the package from the site and the one from ubuntu repo in the past. Both worked for me.

@MikRoscope

This comment has been minimized.

Show comment
Hide comment
@MikRoscope

MikRoscope Mar 16, 2015

My virtualbox stopped working again. It's hard to know when since I only use it occasionally. I did a release upgrade from precise to trusty in between and there were several updates from google for chromeos. I did sudo sh -e ~/Downloads/crouton -n <chroot_name> -u after each of these updates.
My question is on which circumstances one needs to build the kernel headers again? perhaps with the script from @divx118. After a chromeos update? after Ubuntu release upgrade? or never?

My virtualbox stopped working again. It's hard to know when since I only use it occasionally. I did a release upgrade from precise to trusty in between and there were several updates from google for chromeos. I did sudo sh -e ~/Downloads/crouton -n <chroot_name> -u after each of these updates.
My question is on which circumstances one needs to build the kernel headers again? perhaps with the script from @divx118. After a chromeos update? after Ubuntu release upgrade? or never?

@divx118

This comment has been minimized.

Show comment
Hide comment
@divx118

divx118 Mar 16, 2015

Contributor

@MikRoscope See divx118/crouton-packages#10 I just update the kernel headers last weekend. Normally they don't need to be updated often. Please post any issues regarding virtualbox on my github. We don't want to clutter up issues here, it is not crouton "related" in the meaning it is a bug in crouton.

Contributor

divx118 commented Mar 16, 2015

@MikRoscope See divx118/crouton-packages#10 I just update the kernel headers last weekend. Normally they don't need to be updated often. Please post any issues regarding virtualbox on my github. We don't want to clutter up issues here, it is not crouton "related" in the meaning it is a bug in crouton.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment