Re: VBoxManage errors at boot
On Wed, Mar 19, 2014 at 11:25 PM, Thomas Hoffmann trh...@gmail.com wrote: On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann trh...@gmail.comwrote: I'm running emulators/virtualbox-ose-4.3.8 on -CURRENT r263411 amd64. The last several boot sequences I have noticed the following errors in the console log: Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Failed to create the VirtualBox object! Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. I'm perplexed by these messages because I do not have any cron jobs that invoke VBoxManage @reboot for any purpose whatsoever be it managing or starting a virtual machine. I'm thinking these messages appeared after the upgrade to 4.3.8, but I cannot be certain. Can anyone provide a context for these errors? -Tom I've done a bit of digging and can offer a bit more info. I upgraded virtualbox-ose to 4.3.8 on 3/3 and did not see the errors until 3/11, so the upgrade itself did not introduce the errors. The 3/3 upgrade was my last upgrade of virtualbox-ose and I did not re-install it after that. However, on 3/11 I built a new -CURRENT (r263062). Something in that build seems to have introduced the errors. My previous -CURRENT (r262295) built on 3/8 did not have the errors. I'm still looking into this. -Tom Okay, so I found the source of this error. In /usr/local/etc/rc.d/vboxnet (I have vboxnet_enable in /etc/rc.conf) it attempts to execute the following command for vboxnet_start: # initialize configured host-only interfaces /usr/local/bin/VBoxManage list hostonlyifs /dev/null I can run VBoxManage as a normal user without any problems, but when I run VBoxManage as root it results in the same three errors from my original post. That is why it errors out during the boot process. I don't know if that behavior is normal or not. In any event, don't understand the purpose of the VBoxManage command in /usr/local/etc/rc.d/vboxnet since, contrary to the immediately preceding comment, it is only listing (not initializing) hostonly interfaces and sending the output to dev/null. It seems pointless. Anyway my conclusion is that the boot time error messages while annoying, are harmless. I'm still not certain why the error messages just started showing up in the console log on 3/11. -Tom ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VBoxManage errors at boot
On Thu, Mar 20, 2014 at 8:53 AM, Thomas Hoffmann trh...@gmail.com wrote: On Wed, Mar 19, 2014 at 11:25 PM, Thomas Hoffmann trh...@gmail.com wrote: On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann trh...@gmail.comwrote: I'm running emulators/virtualbox-ose-4.3.8 on -CURRENT r263411 amd64. The last several boot sequences I have noticed the following errors in the console log: Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Failed to create the VirtualBox object! Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. I'm perplexed by these messages because I do not have any cron jobs that invoke VBoxManage @reboot for any purpose whatsoever be it managing or starting a virtual machine. I'm thinking these messages appeared after the upgrade to 4.3.8, but I cannot be certain. Can anyone provide a context for these errors? -Tom I've done a bit of digging and can offer a bit more info. I upgraded virtualbox-ose to 4.3.8 on 3/3 and did not see the errors until 3/11, so the upgrade itself did not introduce the errors. The 3/3 upgrade was my last upgrade of virtualbox-ose and I did not re-install it after that. However, on 3/11 I built a new -CURRENT (r263062). Something in that build seems to have introduced the errors. My previous -CURRENT (r262295) built on 3/8 did not have the errors. I'm still looking into this. -Tom Okay, so I found the source of this error. In /usr/local/etc/rc.d/vboxnet (I have vboxnet_enable in /etc/rc.conf) it attempts to execute the following command for vboxnet_start: # initialize configured host-only interfaces /usr/local/bin/VBoxManage list hostonlyifs /dev/null I can run VBoxManage as a normal user without any problems, but when I run VBoxManage as root it results in the same three errors from my original post. That is why it errors out during the boot process. I don't know if that behavior is normal or not. In any event, don't understand the purpose of the VBoxManage command in /usr/local/etc/rc.d/vboxnet since, contrary to the immediately preceding comment, it is only listing (not initializing) hostonly interfaces and sending the output to dev/null. It seems pointless. Anyway my conclusion is that the boot time error messages while annoying, are harmless. I'm still not certain why the error messages just started showing up in the console log on 3/11. It does exactly what the comment says. host-only interfaces need to be initialized (pretty early for some configurations) and the hostonlyifs listing is the least intrusive one which ensures that they are. It might be that the error output of vboxmanage has been switched to stderr now and we need to add an 2/dev/null too. Have you recompiled all vbox kernel modules after your update to a new current? -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: VBoxManage errors at boot
On Thu, Mar 20, 2014 at 8:02 AM, Bernhard Fröhlich de...@freebsd.orgwrote: On Thu, Mar 20, 2014 at 8:53 AM, Thomas Hoffmann trh...@gmail.com wrote: On Wed, Mar 19, 2014 at 11:25 PM, Thomas Hoffmann trh...@gmail.com wrote: On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann trh...@gmail.com wrote: I'm running emulators/virtualbox-ose-4.3.8 on -CURRENT r263411 amd64. The last several boot sequences I have noticed the following errors in the console log: Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Failed to create the VirtualBox object! Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. I'm perplexed by these messages because I do not have any cron jobs that invoke VBoxManage @reboot for any purpose whatsoever be it managing or starting a virtual machine. I'm thinking these messages appeared after the upgrade to 4.3.8, but I cannot be certain. Can anyone provide a context for these errors? -Tom I've done a bit of digging and can offer a bit more info. I upgraded virtualbox-ose to 4.3.8 on 3/3 and did not see the errors until 3/11, so the upgrade itself did not introduce the errors. The 3/3 upgrade was my last upgrade of virtualbox-ose and I did not re-install it after that. However, on 3/11 I built a new -CURRENT (r263062). Something in that build seems to have introduced the errors. My previous -CURRENT (r262295) built on 3/8 did not have the errors. I'm still looking into this. -Tom Okay, so I found the source of this error. In /usr/local/etc/rc.d/vboxnet (I have vboxnet_enable in /etc/rc.conf) it attempts to execute the following command for vboxnet_start: # initialize configured host-only interfaces /usr/local/bin/VBoxManage list hostonlyifs /dev/null I can run VBoxManage as a normal user without any problems, but when I run VBoxManage as root it results in the same three errors from my original post. That is why it errors out during the boot process. I don't know if that behavior is normal or not. In any event, don't understand the purpose of the VBoxManage command in /usr/local/etc/rc.d/vboxnet since, contrary to the immediately preceding comment, it is only listing (not initializing) hostonly interfaces and sending the output to dev/null. It seems pointless. Anyway my conclusion is that the boot time error messages while annoying, are harmless. I'm still not certain why the error messages just started showing up in the console log on 3/11. It does exactly what the comment says. host-only interfaces need to be initialized (pretty early for some configurations) and the hostonlyifs listing is the least intrusive one which ensures that they are. It might be that the error output of vboxmanage has been switched to stderr now and we need to add an 2/dev/null too. Have you recompiled all vbox kernel modules after your update to a new current? Sigh. No I did not. I should have thought of that as a probable cause. Thanks. -Tom ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
pkg upgrade today (20140320) breaks VirtualBox
$ uname -a FreeBSD mercury 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 cd@mercury:~$ $ VBoxManage /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/bin/VBoxManage not found $ VBoxSDL VBoxSDL: Error -610 in supR3HardenedMainInitRuntime! VBoxSDL: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found VBoxSDL: Tip! It may help to reinstall VirtualBox. $ pkg info virtualbox-ose virtualbox-ose-4.3.6 Name : virtualbox-ose Version: 4.3.6 Installed on : Sun Mar 2 17:38:52 CET 2014 Origin : emulators/virtualbox-ose Architecture : freebsd:10:x86:64 Prefix : /usr/local Categories : emulators Licenses : GPLv2 Maintainer : v...@freebsd.org WWW: http://www.virtualbox.org/ Comment: A general-purpose full virtualizer for x86 hardware Options: DBUS : on DEBUG : off GUESTADDITIONS : off NLS: on PULSEAUDIO : off PYTHON : on QT4: on UDPTUNNEL : on VDE: off VNC: on VPX: off WEBSERVICE : on X11: on Shared Libs required: libxml2.so.5 libvncserver.so.0 libstdc++.so.6 libpng15.so.15 libgcc_s.so.1 libcurl.so.7 libXt.so.6 libXmu.so.6 libXinerama.so.1 libXext.so.6 libXcursor.so.1 libX11.so.6 libSDL-1.2.so.11 libQtOpenGL.so.4 libQtNetwork.so.4 libQtGui.so.4 libQtCore.so.4 libGL.so.1 VBoxXPCOM.so VBoxVMM.so VBoxRT.so VBoxREM.so VBoxOGLrenderspu.so VBoxOGLhostcrutil.so VBoxKeyboard.so VBoxDDU.so VBoxDD2.so Shared Libs provided: VirtualBox.so VBoxXPCOMIPCC.so VBoxXPCOMC.so VBoxXPCOM.so VBoxVNCMain.so VBoxVNC.so VBoxVMMPreload.so VBoxVMM.so VBoxSharedFolders.so VBoxSharedCrOpenGL.so VBoxSharedClipboard.so VBoxSVCM.so VBoxSDL.so VBoxRT.so VBoxREM.so VBoxPython2_7.so VBoxPython.so VBoxOGLrenderspu.so VBoxOGLhosterrorspu.so VBoxOGLhostcrutil.so VBoxNetNAT.so VBoxNetDHCP.so VBoxKeyboard.so VBoxHostChannel.so VBoxHeadless.so VBoxGuestPropSvc.so VBoxGuestControlSvc.so VBoxDbg.so VBoxDDU.so VBoxDD2.so VBoxDD.so VBoxC.so VBoxAuthSimple.so VBoxAuth.so DBGCPlugInDiggers.so Flat size : 217MiB Description: VirtualBox is a family of powerful x86 virtualization products for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License. WWW: http://www.virtualbox.org/ -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: pkg upgrade today (20140320) breaks VirtualBox
On Thu, 20 Mar 2014, CeDeROM wrote: $ VBoxManage /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/bin/VBoxManage not found $ VBoxSDL VBoxSDL: Error -610 in supR3HardenedMainInitRuntime! VBoxSDL: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found I found it necessary to `pkg delete compat9x\*`. I don't know why that compat package is getting installed. -- Greg ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/187580: commit references a PR
The following reply was made to PR ports/187580; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: ports/187580: commit references a PR
Date: Thu, 20 Mar 2014 18:11:16 + (UTC)
Author: jkim
Date: Thu Mar 20 18:11:11 2014
New Revision: 348711
URL: http://svnweb.freebsd.org/changeset/ports/348711
QAT: https://qat.redports.org/buildarchive/r348711/
Log:
Fix panic for stable/9. Use vm_page_alloc_contig() as it is now available.
Tested by: Douglas Berry (doug at bitnix dot ca)
PR: ports/187580
Added:
head/emulators/virtualbox-ose-kmod-legacy/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_PAGEOUT_GROW_CACHE.c
(contents, props changed)
Modified:
head/emulators/virtualbox-ose-additions/Makefile
head/emulators/virtualbox-ose-kmod-legacy/Makefile
head/emulators/virtualbox-ose-kmod-legacy/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c
head/emulators/virtualbox-ose-kmod/Makefile
head/emulators/virtualbox-ose/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c
Modified: head/emulators/virtualbox-ose-additions/Makefile
==
--- head/emulators/virtualbox-ose-additions/Makefile Thu Mar 20 18:01:39
2014(r348710)
+++ head/emulators/virtualbox-ose-additions/Makefile Thu Mar 20 18:11:11
2014(r348711)
@@ -3,6 +3,7 @@
PORTNAME= virtualbox-ose
DISTVERSION= 4.3.8
+PORTREVISION= 1
CATEGORIES= emulators
MASTER_SITES= http://download.virtualbox.org/virtualbox/${DISTVERSION}/ \
http://tmp.chruetertee.ch/ \
Modified: head/emulators/virtualbox-ose-kmod-legacy/Makefile
==
--- head/emulators/virtualbox-ose-kmod-legacy/Makefile Thu Mar 20 18:01:39
2014(r348710)
+++ head/emulators/virtualbox-ose-kmod-legacy/Makefile Thu Mar 20 18:11:11
2014(r348711)
@@ -3,6 +3,7 @@
PORTNAME= virtualbox-ose
DISTVERSION= 4.2.22
+PORTREVISION= 1
CATEGORIES= emulators
MASTER_SITES= http://download.virtualbox.org/virtualbox/${DISTVERSION}/ \
http://tmp.chruetertee.ch/ \
Modified:
head/emulators/virtualbox-ose-kmod-legacy/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c
==
---
head/emulators/virtualbox-ose-kmod-legacy/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c
Thu Mar 20 18:01:39 2014(r348710)
+++
head/emulators/virtualbox-ose-kmod-legacy/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c
Thu Mar 20 18:11:11 2014(r348711)
@@ -1,7 +1,7 @@
$FreeBSD$
src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2013-03-20
19:19:36.795745576 -0700
-+++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2013-03-20
19:15:35.164791970 -0700
+--- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.orig
2014-03-14 17:25:46.0 -0400
src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2014-03-14
17:34:35.0 -0400
@@ -162,7 +162,11 @@
case RTR0MEMOBJTYPE_PHYS:
case RTR0MEMOBJTYPE_PHYS_NC:
@@ -14,7 +14,7 @@ $FreeBSD$
vm_page_t pPage = vm_page_find_least(pMemFreeBSD-pObject, 0);
#if __FreeBSD_version 90
/* See
http://lists.freebsd.org/pipermail/freebsd-current/2012-November/037963.html */
-@@ -177,7 +181,12 @@
+@@ -177,7 +181,11 @@
#if __FreeBSD_version 90
vm_page_unlock_queues();
#endif
@@ -23,11 +23,18 @@ $FreeBSD$
+#else
VM_OBJECT_UNLOCK(pMemFreeBSD-pObject);
+#endif
-+
vm_object_deallocate(pMemFreeBSD-pObject);
break;
}
-@@ -205,10 +214,18 @@
+@@ -198,17 +206,25 @@
+ vm_page_t pPages;
+ int cTries = 0;
+
+-#if __FreeBSD_version 100
++#if __FreeBSD_version = 902508
+ int fFlags = VM_ALLOC_INTERRUPT | VM_ALLOC_NOBUSY;
+ if (fWire)
+ fFlags |= VM_ALLOC_WIRED;
while (cTries = 1)
{
@@ -46,31 +53,7 @@ $FreeBSD$
if (pPages)
break;
vm_pageout_grow_cache(cTries, 0, VmPhysAddrHigh);
-@@ -228,7 +245,11 @@
-
- if (!pPages)
- return pPages;
-+#if __FreeBSD_version = 130
-+VM_OBJECT_WLOCK(pObject);
-+#else
- VM_OBJECT_LOCK(pObject);
-+#endif
- for (vm_pindex_t iPage = 0; iPage cPages; iPage++)
- {
- vm_page_t pPage = pPages + iPage;
-@@ -240,7 +261,11 @@
- atomic_add_int(cnt.v_wire_count, 1);
- }
- }
-+#if __FreeBSD_version = 130
-+VM_OBJECT_WUNLOCK(pObject);
-+#else
- VM_OBJECT_UNLOCK(pObject);
Re: ports/187580: emulators/virtualbox-ose panic when starting virtual machine on 9.2-STABLE
Synopsis: emulators/virtualbox-ose panic when starting virtual machine on 9.2-STABLE State-Changed-From-To: open-closed State-Changed-By: jkim State-Changed-When: Thu Mar 20 18:20:15 UTC 2014 State-Changed-Why: It should be fixed with r348711. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=187580 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: pkg upgrade today (20140320) breaks VirtualBox
On Thu, Mar 20, 2014 at 7:06 PM, Greg Rivers gcr+freebsd-po...@tharned.org wrote: I found it necessary to `pkg delete compat9x\*`. I don't know why that compat package is getting installed. Ugh, I have uninstalled that package, but before I have tried to reinstall virtualbox-ose... it seems its gone from repositories! Daaamn I need that VBox :-( # pkg install -x virtualbox Updating repository catalogue The following 9 packages will be installed: Installing php5: 5.4.26 Installing php5-xml: 5.4.26 Installing php5-simplexml: 5.4.26 Installing php5-json: 5.4.26 Installing virtualbox-ose-kmod: 4.3.8 Installing virtualbox-ose-kmod-legacy: 4.2.22 Installing php5-session: 5.4.26 Installing php5-soap: 5.4.26 Installing phpvirtualbox: 4.3.1_1 The installation will require 26 MB more space 5 MB to be downloaded -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: pkg upgrade today (20140320) breaks VirtualBox
Also noticed that since yesterday at least... its not in the latest repo.. only in quarterly and release. Same for other ports like kde... I guess those failed to build. How often is the latest repo updated? weekly? Guess the only option for those is build from ports. Mike On 20 March 2014 19:13:33 WET, CeDeROM cede...@tlen.pl wrote: On Thu, Mar 20, 2014 at 7:06 PM, Greg Rivers gcr+freebsd-po...@tharned.org wrote: I found it necessary to `pkg delete compat9x\*`. I don't know why that compat package is getting installed. Ugh, I have uninstalled that package, but before I have tried to reinstall virtualbox-ose... it seems its gone from repositories! Daaamn I need that VBox :-( # pkg install -x virtualbox Updating repository catalogue The following 9 packages will be installed: Installing php5: 5.4.26 Installing php5-xml: 5.4.26 Installing php5-simplexml: 5.4.26 Installing php5-json: 5.4.26 Installing virtualbox-ose-kmod: 4.3.8 Installing virtualbox-ose-kmod-legacy: 4.2.22 Installing php5-session: 5.4.26 Installing php5-soap: 5.4.26 Installing phpvirtualbox: 4.3.1_1 The installation will require 26 MB more space 5 MB to be downloaded -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
