[arch-general] [VirtualBox] Sudden reboots and freezes with latest kernel
I wonder if anyone else is experimenting sudden reboots and freezes while trying to run VirtualBox with latest kernel. Arch: x86_64 Kernel: [core/kernel26 2.6.35.4-1] DE/WM: both KDE SC 4.5 and Awesome 3. On KDE everytime I want to launch a VM PC reboots all of a sudden, on Awesome simple freezes :S Video driver: [catalyst/catalyst 10.8-2] with xorg-server-backclear 1.8.1.902-1, xvba-video 0.7.3-1 and lib32-catalyst-utils 10.8-2 installed. VirtualBox: [aur/virtualbox_bin 3.2.8-1] v. 3.2.8r64453 /var/log/errors.log tail's: Aug 30 01:51:13 localhost sudo: pam_unix(sudo:auth): conversation failed Aug 30 01:51:13 localhost sudo: pam_unix(sudo:auth): conversation failed Aug 30 01:51:25 localhost kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance Aug 30 01:51:25 localhost kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent Aug 30 01:51:25 localhost kernel: vboxdrv: the usage of hardware performance counters by Aug 30 01:51:25 localhost kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: VirtualBox/9282/0x00000002 Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: VirtualBox/9254/0x00000003 Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: X/8725/0x00000003 Aug 30 01:54:34 localhost NetworkManager[3623]: nm_setting_ip4_config_get_dhcp_hostname: assertion `NM_IS_SETTING_IP4_CONFIG (setting)' failed /var/log/kernel.log tail's: Aug 30 01:58:49 localhost kernel: EXT4-fs (sda6): re-mounted. Opts: commit=0 Aug 30 01:58:49 localhost kernel: EXT4-fs (sdb2): re-mounted. Opts: commit=0 Aug 30 01:58:50 localhost kernel: EXT4-fs (sdc5): re-mounted. Opts: commit=0 Aug 30 01:58:50 localhost kernel: EXT4-fs (sdc1): re-mounted. Opts: commit=0 Aug 30 01:58:52 localhost kernel: Bluetooth: Core ver 2.15 Aug 30 01:58:52 localhost kernel: NET: Registered protocol family 31 Aug 30 01:58:52 localhost kernel: Bluetooth: HCI device and connection manager initialized Aug 30 01:58:52 localhost kernel: Bluetooth: HCI socket layer initialized Aug 30 01:59:07 localhost kernel: fuse init (API version 7.14) Aug 30 02:02:13 localhost kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) I can't seem to find errors in the other log files (kernel, syslog and dmsg). -Martín "Un buen antivirus, no debería dejar cargar Windows y sugerir instalar GNU/Linux xD" - omar_uy@#parabola@freenode
Yes I experanced the same situation yesterday. I ran /etc/rc.d/vbox setup and then reboot, seemed resolved. Except that of of my vm in a saved session can no more resotre, i have to discard and boot as fresh, not hurting much. On Mon, Aug 30, 2010 at 1:16 PM, Martín Cigorraga <martosurf7600@gmail.com>wrote:
I wonder if anyone else is experimenting sudden reboots and freezes while trying to run VirtualBox with latest kernel.
Arch: x86_64 Kernel: [core/kernel26 2.6.35.4-1] DE/WM: both KDE SC 4.5 and Awesome 3. On KDE everytime I want to launch a VM PC reboots all of a sudden, on Awesome simple freezes :S Video driver: [catalyst/catalyst 10.8-2] with xorg-server-backclear 1.8.1.902-1, xvba-video 0.7.3-1 and lib32-catalyst-utils 10.8-2 installed. VirtualBox: [aur/virtualbox_bin 3.2.8-1] v. 3.2.8r64453
/var/log/errors.log tail's: Aug 30 01:51:13 localhost sudo: pam_unix(sudo:auth): conversation failed Aug 30 01:51:13 localhost sudo: pam_unix(sudo:auth): conversation failed Aug 30 01:51:25 localhost kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance Aug 30 01:51:25 localhost kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent Aug 30 01:51:25 localhost kernel: vboxdrv: the usage of hardware performance counters by Aug 30 01:51:25 localhost kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: VirtualBox/9282/0x00000002 Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: VirtualBox/9254/0x00000003 Aug 30 01:53:12 localhost kernel: BUG: scheduling while atomic: X/8725/0x00000003 Aug 30 01:54:34 localhost NetworkManager[3623]: nm_setting_ip4_config_get_dhcp_hostname: assertion `NM_IS_SETTING_IP4_CONFIG (setting)' failed
/var/log/kernel.log tail's: Aug 30 01:58:49 localhost kernel: EXT4-fs (sda6): re-mounted. Opts: commit=0 Aug 30 01:58:49 localhost kernel: EXT4-fs (sdb2): re-mounted. Opts: commit=0 Aug 30 01:58:50 localhost kernel: EXT4-fs (sdc5): re-mounted. Opts: commit=0 Aug 30 01:58:50 localhost kernel: EXT4-fs (sdc1): re-mounted. Opts: commit=0 Aug 30 01:58:52 localhost kernel: Bluetooth: Core ver 2.15 Aug 30 01:58:52 localhost kernel: NET: Registered protocol family 31 Aug 30 01:58:52 localhost kernel: Bluetooth: HCI device and connection manager initialized Aug 30 01:58:52 localhost kernel: Bluetooth: HCI socket layer initialized Aug 30 01:59:07 localhost kernel: fuse init (API version 7.14) Aug 30 02:02:13 localhost kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
I can't seem to find errors in the other log files (kernel, syslog and dmsg).
-Martín
"Un buen antivirus, no debería dejar cargar Windows y sugerir instalar GNU/Linux xD" - omar_uy@#parabola@freenode
-- Arch Linuxer, Pythoner, Geek --> Blog: http://apt-blog.net
On 08/30/2010 08:16 AM, Martín Cigorraga wrote:
I wonder if anyone else is experimenting sudden reboots and freezes while trying to run VirtualBox with latest kernel.
because the kernel config was changed and we had to rebuild all modules too. i think i replied too on the kernel signoff thread -- Ionuț
Yes you did reply, thank you very much. -Martín "Un buen antivirus, no debería dejar cargar Windows y sugerir instalar GNU/Linux xD" - omar_uy@#parabola@freenode
participants (3)
-
Ionuț Bîru
-
Martín Cigorraga
-
PT M.