Every time resume\suspend of physical host happens with launched and active VirtualBox machine - physical host freezes completely. Installed versions: virtualbox-ose-3.2.12_1 A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-3.2.12_1 VirtualBox kernel module for FreeBSD VirtualBox setup using instruction from: http://wiki.freebsd.org/VirtualBox Changes in env: .. echo vboxnet_enable=\"YES\" >> /etc/rc.conf echo 'cloned_interfaces="tap10 tap11 tap12 tap13 tap14 tap15 bridge0"' >> /etc/rc.conf echo 'ifconfig_bridge0="addm ale0 addm tap10 addm tap11 addm tap12 addm tap13 addm tap14 addm tap15 up"' >> /etc/rc.conf echo vboxdrv_load=\"YES\" >> /boot/loader.conf echo perm cd0 0660 >> /etc/devfs.conf echo perm xpt0 0660 >> /etc/devfs.conf echo perm pass0 0660 >> /etc/devfs.conf pw groupmod vboxusers -m $ARA_INIT_USER_NAME echo net.link.tap.user_open=1 >> /etc/sysctl.conf echo net.link.tap.up_on_open=1 >> /etc/sysctl.conf echo chmod 0660 /dev/tap10 >> /etc/rc.local echo chmod 0660 /dev/tap11 >> /etc/rc.local echo chmod 0660 /dev/tap12 >> /etc/rc.local echo chmod 0660 /dev/tap13 >> /etc/rc.local echo chmod 0660 /dev/tap14 >> /etc/rc.local echo chmod 0660 /dev/tap15 >> /etc/rc.local .. Then use VM with bridged adapter, tap10 for example. How-To-Repeat: VM - VirtualBox virtual machine PM - Physical Machine (host) 1. Boot PM; 2. Launch VirtualBox and run some prepared VM; 3. Suspend PM using acpiinfo -s3; 4. Resume PM; -> PM hangs with black screen after attempt to resume. Here is similar situation, but with pre-paused VirtualBox: 1. Boot PM; 2. Launch VirtualBox and run some prepared VM; 3. Set VM to Pause (menu Machine->Pause); 4. Suspend PM using acpiinfo -s3; 5. Resume PM; [PM resumed successfully here] 6. Set VM to "Resume" (Menu->Resume). -> PM hangs completely. So it's not ACPI bug, it's how ACPI affects VB and it in turn affects PM.
Responsible Changed From-To: freebsd-ports-bugs->freebsd-bugs This appears to be a kernel bug.
For bugs matching the following conditions: - Status == In Progress - Assignee == "bugs@FreeBSD.org" - Last Modified Year <= 2017 Do - Set Status to "Open"
(In reply to Robert from comment #0) Reproducible with 6.1.46_1 or greater on a currently supported version of the FreeBSD? Thanks
(In reply to Graham Perrin from comment #3) Indeed. I've never seen successfull resume with VM running on 14-current, 15-current But in my case there is no 'black screen' - always kernel panic
by the way. Solution described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212918#c4 (vboxmanage setproperty hwvirtexclusive off) works fine to me