VT-x does not survive S3 ACPI sleep.

[Clemens Fruhwirth]

Restarting tasks ... <0>invalid opcode: 0000 #1 PREEMPT SMP last sysfs file: /sys/power/state CPU 2 Modules linked in: rfcomm l2cap btusb bluetooth vboxdrv i915 drm xt_tcpudp xt_state nf_conntrack iptable_filter ip_tables x_tables bridge stp llc fuse coretemp tun loop sha1_generic cpufreq_userspace snd_pcm_oss snd_mixer_oss rtc_cmos rtc_core rtc_lib gspca_zc3xx snd_hda_intel snd_usb_audio snd_usb_lib snd_pcm gspca_main snd_rawmidi compat_ioctl32 snd_hwdep snd_timer videodev intel_agp snd e1000e psmouse v4l1_compat soundcore 8250_pci 8250_pnp i2c_i801 snd_page_alloc 8250 i2c_core serial_core nfs lockd sunrpc dm_snapshot dm_mirror dm_region_hash dm_log usbhid ohci_hcd uhci_hcd usb_storage scsi_wait_scan Pid: 19319, comm: VirtualBox Not tainted 2.6.28-gentoo-64-intel #7 RIP: 0010:[<ffffffffa03217f7>] [<ffffffffa03217f7>] g_abExecMemory+0x69b7/0x180000 [vboxdrv] RSP: 0018:ffff8800a6ae1d90 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa0311090 RDX: 00000000fffff054 RSI: 000000008005003b RDI: 0000000000006c00 RBP: ffff8800a6ae1dc8 R08: 0000000000000002 R09: 0000000007c2d8a4 R10: 0000000000000002 R11: 0000000000000246 R12: ffffc200108a5000 R13: 0000000000000040 R14: 0000000000010202 R15: 0000000041d14000 FS: 0000000041d13950(0063) GS:ffff88013b805880(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 00000000aa049000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process VirtualBox (pid: 19319, threadinfo ffff8800a6ae0000, task ffff8800645f9640) Stack:

ffffffffa0323fa1 0000000000000000 ffff8800645f9a70 0000000000010202 0000000041d14000 00000000fffff054 ffffc200108a5000 ffff8800a6ae1df8 ffffffffa0321103 ffffc200108a5a60 ffffc200108a5000 0000000000000000

Call Trace:

[<ffffffffa0323fa1>] ? g_abExecMemory+0x9161/0x180000 [vboxdrv] [<ffffffffa0321103>] g_abExecMemory+0x62c3/0x180000 [vboxdrv] [<ffffffffa0326fed>] g_abExecMemory+0xc1ad/0x180000 [vboxdrv] [<ffffffffa031192b>] supdrvIOCtlFast+0x5b/0x70 [vboxdrv] [<ffffffffa03110da>] ? VBoxDrvLinuxIOCtl+0x4a/0x1d0 [vboxdrv] [<ffffffff802349fb>] ? finish_task_switch+0x2b/0xd0 [<ffffffff802aa90f>] ? vfs_ioctl+0x2f/0xa0 [<ffffffff802aaca3>] ? do_vfs_ioctl+0x323/0x450 [<ffffffff802aae19>] ? sys_ioctl+0x49/0x80 [<ffffffff8020b81c>] ? sysret_signal+0x14/0x1f [<ffffffff8020ba97>] ? ptregscall_common+0x67/0xb0 [<ffffffff8020b79b>] ? system_call_fastpath+0x16/0x1b

Code: c0 0f 30 58 8e d8 58 8e c0 5b 41 5c 41 5d 41 5e 41 5f b8 5b f0 ff ff e9 e9 fe ff ff cc cc cc cc b8 ff ff ff ff 48 21 c7 48 31 c0 <0f> 79 fe 73 06 b8 5f f0 ff ff c3 75 05 b8 60 f0 ff ff c3 cc cc RIP [<ffffffffa03217f7>] g_abExecMemory+0x69b7/0x180000 [vboxdrv]

RSP <ffff8800a6ae1d90>

---[ end trace 4090312d383e81f3 ]--- done.

That's what I get if I send my box into suspend-to-ram (S3) sleep with a running VT-x enabled VM. There is no problem when VT-x is disabled. I presume the kernel driver sets some CPU states/modes when VT-x is enabled, especially the "Invalid Opcode" message hints that. That's not that surprising as the power is removed from the CPU in S3 mode.

[Sander van Leeuwen]

Obsolete. Fixed in 2.1.0 already.

[Clemens Fruhwirth]

Indeed, 2.1.2 works. Thanks.