Virtual Machine in headless mode crash then i connect to it via VNC app-emulation/virtualbox-4.1.18-r1 (additions extensions headless java opengl pam qt4 sdk vboxwebsrv vnc) net-libs/libvncserver-0.9.9 virtualbox-4.1.18-r1 depends on this version of libvncserver All packages was rebuilded with "emerge world -e" This is described in bug 425698 https://bugs.gentoo.org/show_bug.cgi?id=425698 Topic Starter decision was to mask net-libs/libvncserver-0.9.9 ( echo "=net-libs/libvncserver-0.9.9" >> /etc/portage/package.mask ) After i downgraded to (just emerged this two) app-emulation/virtualbox-4.1.18 net-libs/libvncserver-0.9.8.2-r2 -- VM does not crash after VNC connect and shows screen. Reproducible: Always Steps to Reproduce: 1. VM started as servce /etc/init.d/virtualbox.vnc_test actual start command is VBoxHeadless -startvm "VM_NAME" --vnc --vncport 59111 --vncpass "PASS" 2. When i connect via VNC client - VM crashes (even before password request) 3. If i don not connect with VNC - VM continues to work Actual Results: *** buffer overflow detected ***: /usr/lib64/virtualbox/VBoxHeadless terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x7f0638e93cc7] /lib64/libc.so.6(+0xfbb30)[0x7f0638e91b30] /lib64/libc.so.6(+0xfdc7e)[0x7f0638e93c7e] /usr/lib64/libvncserver.so.0(rfbProcessNewConnection+0xf9)[0x7f0636878c49] /usr/lib64/libvncserver.so.0(rfbCheckFds+0x438)[0x7f0636879198] /usr/lib64/libvncserver.so.0(rfbProcessEvents+0x1e)[0x7f06368703de] /usr/lib64/libvncserver.so.0(rfbRunEventLoop+0x23)[0x7f06368704c3] /usr/lib64/virtualbox/VBoxHeadless.so(+0xc2e5)[0x7f0636adb2e5] /usr/lib64/virtualbox/VBoxRT.so(+0x7275e)[0x7f0638adb75e] /usr/lib64/virtualbox/VBoxRT.so(+0xbd51e)[0x7f0638b2651e] /lib64/libpthread.so.0(+0x7d56)[0x7f0639348d56] /lib64/libc.so.6(clone+0x6d)[0x7f0638e7e35d] ======= Memory map: ======== Expected Results: See VM screen, no VirtualMachine crash Bug 425698 https://bugs.gentoo.org/show_bug.cgi?id=425698 https://bugs.archlinux.org/task/30401
Hmm... virtualbox-4.1.18-r1 is already using the patch from that arch linux bug report (see bug #425698 for reference). If that patch really is not fixing the issue I suppose I gotta remove virtualbox-4.1.18-r1 from the tree and wait for the release of virtualbox-4.2.0 before we can use libvncserver-0.9.9 again.
I have no ipv6 support net-libs/libvncserver (24bpp jpeg threads zlib -gcrypt -gnutls -ipv6 -test) virtualbox-4.1.18-ipv6_vnc.patch contains : """"" +#ifdef LIBVNCSERVER_IPv6 + if (mVncPort) { + vncServer->port = mVncPort; + vncServer->ipv6port = mVncPort; + } +#else if (mVncPort) vncServer->port = mVncPort; +#endif + """"" So - i think this patch does absolutely nothing in the case you use only ip4 . It may be better to alter virtualbox-4.1.18-r1 (r2) to depend on <net-libs/libvncserver-0.9.9 Anyways , now i'm using stable virtualbox-4.1.18 and stable libvncserver-0.9.8.2-r2
+*virtualbox-4.1.20 (21 Aug 2012) + + 21 Aug 2012; Lars Wendler <polynomial-c@gentoo.org> virtualbox-4.1.12.ebuild, + -virtualbox-4.1.16.ebuild, virtualbox-4.1.18.ebuild, + -virtualbox-4.1.18-r1.ebuild, -files/virtualbox-4.1.18-ipv6_vnc.patch, + +virtualbox-4.1.20.ebuild: + Version bump. Removed old. Pin libvncserver down to versions lower than 0.9.9 + to prevent crashes in virtualbox (bug #431728). +