Summary: | emulators/virtualbox-ose: VirtualBox 5.1.6 (110634) shut down hang | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | tony01 |
Component: | Individual Port(s) | Assignee: | Walter Schwarzenfeld <w.schwarzenfeld> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Many People | CC: | freebsd, fua, rm, vvd, w.schwarzenfeld |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
Bug Depends on: | 234929 | ||
Bug Blocks: |
Description
tony01
2016-09-27 12:04:50 UTC
if you disconnect from VNC before OS sends the ACPI command "power off" then it will power off fine. if you do not disconect in time the process will hang. I see same issue on my 5 servers. Hosts: 10.3-p7 amd64, virtualbox 4.3.38 and 5.0.26. Guest any: FreeBSD 10.3 amd64, CentOS/RHEL/Oracle Linux 6.x amd64, Win7/2008 32/64bit. Issue was appeared after update net/libvncserver from 0.9.9 to 0.9.10: https://svnweb.freebsd.org/ports?view=revision&revision=417416. Assign to maintainer after downgrading libvncserver.so.0 as vvd suggested the problem will go away. so it seems that the problem is with net/libvncserver tony, port net/libvncserver was updated to version 0.9.11 - can you test it? (In reply to vvd from comment #5) seems to have the same issue. you still need to disconnect from VNC before OS sends the ACPI command "power off" then it will power off fine. if you do not disconnect in time the process will hang. I have the same issue with VirtualBox 5.1.18 r114002 and lbvncserver 0.9.11 on FreeBsd 11.0 p09 We have 5.2.4. Overcome by events? (In reply to w.schwarzenfeld from comment #8) > We have 5.2.4. Overcome by events? No. Bug still exist with all versions of VirtaulBox and net/libvncserver 0.9.9+. I am seeing this issue also. I thought it was a FreeBSD bug (I raised: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228089) but it's obviously a VirtualBox related. (In reply to devnull from comment #10) Fixed after update libvncserver https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234929 Close here , see comment11. *** This bug has been marked as a duplicate of bug 234929 *** It isn't Duplicate, it's Overcome By Events. |