Date: Sun, 27 Mar 2011 08:23:34 GMT From: Robert <brokensword@te.net.ua> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/155964: OS hangs completely when suspend\resume with active VirtualBox guest window Message-ID: <201103270823.p2R8NYA0037573@red.freebsd.org> Resent-Message-ID: <201103270830.p2R8UARr033069@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 155964 >Category: ports >Synopsis: OS hangs completely when suspend\resume with active VirtualBox guest window >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 27 08:30:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Robert >Release: 8.2-RELEASE >Organization: >Environment: FreeBSD ara-home-pc-freebsd 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: 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. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201103270823.p2R8NYA0037573>