﻿ticket	summary	guest	version	created	modified	_changetime	_description	_reporter
19602	VirtualBox 6.1.6 and 6.1.8 failled to start virtual machines	Windows	VirtualBox 6.1.8	2020-05-19T14:43:29Z	2020-08-23T06:17:42Z	2020-08-23T06:17:42Z	"Hello,

I have used VirtualBox successfully under Illumos/OpenIndiana (the open version of Solaris). However, today I upgraded my system and I
cannot run VirtualBox version 6.1.6 r137129. My system has ab AMD FX-6300 Six-core processor and AMD-V is enable. When the I try to run
either Windows XP or Windows 7 I get the following message:

Failed to open a session for the virtual machine Win7.

VirtualBox can't enable the AMD-V extension. Please close all other virtualization programs. (VERR_SVM_IN_USE).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

KVM is not installed in my system:

$ pkg list kvm

pkg list: no packages matching the following patterns are installed:
kvm

Also bhyve is not installed inthis system:

$ pkg list bhyve

pkg list: no packages matching the following patterns are installed:
bhyve

Since I have no idea what is going I thouggt someone here might be able to help fixing this problem.

Regards,

Apostolos

PS Setting export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on a terminal and running VBox from there does not solve the problem...

PSS I have also used a build of VBox 6.1.8 and I see exactly the same behavior"	asyropoulos
20752	VirtualBox-6.1.30-SunOS-amd64-r148432.pkg failed on Solaris 10 1/13 s10x_u11wos_24a	other	VirtualBox 6.1.30	2021-12-29T14:29:10Z	2021-12-29T19:36:19Z	2021-12-29T19:36:19Z	"Info for Solaris 10:

# cat release
                    Oracle Solaris 10 1/13 s10x_u11wos_24a X86
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013


VB installation console output:
# pkgadd -G -d VirtualBox-6.1.30-SunOS-amd64-r148432.pkg

The following packages are available:
  1  SUNWvbox     Oracle VM VirtualBox
                  (i386) 6.1.30,REV=2021.11.22.16.37.46.148432

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <SUNWvbox> from </tmp/VirtualBox-6.1.30-SunOS-amd64-r148432.pkg>

Oracle VM VirtualBox(i386) 6.1.30,REV=2021.11.22.16.37.46.148432

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.


The installation of this package was previously terminated and
installation was never successfully completed.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
Done.
Waiting for services from previous installation to be removed.........
Warning!!! Some service(s) still appears to be present
Using </> as the package base directory.
## Processing package information.
## Processing system information.
   327 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

The following files are being installed with setuid and/or setgid
permissions:
* /opt/VirtualBox/amd64/VBoxHeadless <setuid root>
* /opt/VirtualBox/amd64/VBoxNetAdpCtl <setuid root>
* /opt/VirtualBox/amd64/VBoxNetDHCP <setuid root>
* /opt/VirtualBox/amd64/VBoxNetNAT <setuid root>
* /opt/VirtualBox/amd64/VBoxSDL <setuid root>
* /opt/VirtualBox/amd64/VirtualBoxVM <setuid root>

* - overwriting a file which is also setuid/setgid.

Do you want to install these as setuid/setgid files [y,n,?,q] y

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y

Installing Oracle VM VirtualBox as <SUNWvbox>

## Installing part 1 of 1.
/opt/VirtualBox/vboxconfig.sh
[ verifying class <none> ]
[ verifying class <manifest> ]
## Executing postinstall script.
Checking for older bits...
//opt/VirtualBox/vboxconfig.sh: syntax error at line 682: `refgroup=$' unexpected
## ERROR!! Failed to remove older/partially installed bits.
pkgadd: ERROR: postinstall script did not complete successfully

Installation of <SUNWvbox> failed.

"	Ming H
20144	Solaris host produce no sound in guest OSes	all	VirtualBox 6.1.18	2021-01-20T16:36:58Z	2021-01-20T16:36:58Z	2021-01-20T16:36:58Z	"Since VB v5.2.18 guests in Solaris have no sound, see:
https://forums.virtualbox.org/viewtopic.php?f=11&t=94108&p=490595#p490595

Steps to reproduce this regression :
-Install Solaris 11.4 (or 11.3) on bare metal
-Install latest VB version
-Install any OS, for instance Linux Ubuntu
Problem: Ubuntu guest have no sound. Win7 guest has no sound neither, and probably all other guest OSes?
"	Brutalizer
18330	Linux Mint 19.1 doesn't display on large monitor	Linux	VirtualBox 6.0.2	2019-01-18T23:28:29Z	2019-01-18T23:28:29Z	2019-01-18T23:28:29Z	"I'm running VirtualBox 6.0.2 on Solaris 11.4.
I have a 24"" Sun monitor.

Running Linux Mint 18.1, I can run in full screen just fine.

Running Linux Mint 19.1, if I try to resize the VM window to be close to
the size of the monitor, or run in full screen mode, it only displays a
black screen.  Resizing the window to be smaller causes the display to
appear.

I've installed the 6.0.2 Guest Additions in both cases.

I've updated Linux Mint in both cases.

Even with Linux Mint 18.1, I had at least one case where it would refuse
to use the entire screen size.  I reinstalled the Guest Additions and
then it started working correctly.

Of course all of this could be a problem with Linux Mint, but I have no
idea how to determine that.

I was previously using VirtualBox 6.0.0 with Linux Mint 18.1 and never
had any problems at all with that combination so I fear that something
might be broken with 6.0.2.
"	bs
17400	Seamless mode fails on Solaris hosts, VB 5.2.4	all	VirtualBox 5.2.4	2017-12-25T03:13:38Z	2017-12-25T03:13:38Z	2017-12-25T03:13:38Z	"This started with 5.2.0 beta 1 and continues through VB 5.2.4.  Problem does not exist with 5.1.x.  All guest additions have been updated.

I've tested with Ubuntu Mate 16.10, Solaris 11.3, Windows 7, and Windows XP guests.  With all, the toolbar never appears, and the mini-toolbar of VirtualBox appears for a short time, but also vanishes without even the small row of pixels you can normally click on to have it appear.

Guest toolbar/start bar does not appear, but if you move the mouse over where it should be and click, you get some distortion of the host's desktop, but no guest menus appear.  Compiz is NOT running on host or guests.

I'm attaching log files for the Ubuntu, XP, and Solaris VMs.  Will have to wait for the Windows 7 VM until I get back to that computer in a week."	bq
18134	Qt5 interface does not start with hardening, with qt-xcb enabled.	other	VirtualBox 5.2.22	2018-11-15T15:16:16Z	2018-11-15T15:16:16Z	2018-11-15T15:16:16Z	"Hi,
trying to package VirtualBox for OpenIndiana given that stack clash mitigation in illumos broken compatibility (VirtualBox panics).

https://github.com/OpenIndiana/oi-userland/pull/4569

Non-hardened builds run as expected while hardened builds fail to bring up the Qt5 interface.

alarcher@helios:/home/alarcher$ VirtualBox 
ld.so.1: VirtualBox: fatal: libQt5XcbQpa.so.5: open failed: No such file or directory
ld.so.1: VirtualBox: fatal: relocation error: file /usr/lib/qt/5.8/plugins/amd64/platforms/libqxcb.so: symbol _ZN15QXcbIntegrationC1ERK11QStringListRiPPc: referenced symbol not found
Killed

This runs properly as root and symbols were verified to be OK.

Trussing the execution does not help due to hardening.

The only reason I could come up with is that libqtxcb.so's RUNPATH uses $ORIGIN to pick the location of libQt5XcbQpa.so.5.

Is there a hard limitation in the hardening code regarding RUNPATH or is it a bug?

Thanks

"	alarcher
15993	VB 5.1.6 + Solaris 11.3 + SunRay + Multihead + Fullscreen = only first monitor shown	Windows	VirtualBox 5.1.6	2016-09-27T20:58:25Z	2016-09-27T20:58:25Z	2016-09-27T20:58:25Z	When going to fullscreen using VirtualBox 5.1.6 on Solaris 11.3 using SunRay on a multihead Windows 7 instance, only the first (left) screen is drawn. Going back to windowed mode produces the remaining screens.	Marty
17418	Incorrect color map for Solaris 11.3 host when upgrading from 5.1.22 to 5.1.24 and beyond	Windows	VirtualBox 5.1.24	2018-01-04T20:41:34Z	2018-01-04T20:41:34Z	2018-01-04T20:41:34Z	"I'm using a Solaris 11.3 x64 SunRay server and after upgrading from 5.1.22 to 5.1.24 or newer, including 5.2.4, the color map appears to be inverted.

This affects both the GUI and the clients.

Downgrading to 5.1.22 restores the correct behavior."	Tipo
16366	Solaris x86 Host - Centos 7 Guest hangs after using all the memory	Linux	VirtualBox 5.1.12	2017-01-08T11:24:22Z	2017-01-26T22:18:55Z	2017-01-26T22:18:55Z	Solaris x86 Host has 64GB Memory. Centos7 Guest VM given 16GB. After about 3-4 days the VirtualBox process consumes all 16GB and the VM is unavailable. Am able to stop and start the VM and it will stay running for another 3-4 days.	Buster Gonad
15645	3D broken on Solaris 10	other	VirtualBox 5.1.0	2016-07-19T20:20:35Z	2016-08-10T10:53:22Z	2016-08-10T10:53:22Z	"After upgrading to 5.1.0, starting vb results in ""VMSetError: This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings""
Disabling 3D allows VM to start. The problem didn't exist with VirtualBox-5.0.24.  The host graphics driver is NVIDIA-Solaris-x86-352.79.
"	bernievb
15557	Solaris + SMP: Performance decreases as you add processors to guest	Windows	VirtualBox 5.0.22	2016-06-29T14:24:59Z	2016-09-22T21:16:05Z	2016-09-22T21:16:05Z	"I found that with VirtualBox 5.0.x, when you have 1-2 processors assigned to a VM, performance is quite fast. But the more processors you add, the slower the guest VM becomes. I've gone up to 16 processors, which is very slow to boot and extremely laggy after logging in (even Task Manager stopped responding.)

For a scientific test, I used the same host and guest, with a combination of vbox versions and processors assigned to the guest.

The host:
- O/S: Solaris 11.2.15.4.0
- Hardware: Oracle X4-2L
- CPUs: Quantity 2 of E5-2690 v2, 10 cores, 20 threads (Total of 20 cores, 40 threads)
- RAM: 512GB

The guest:
- O/S: Windows 7 + IE 9 Developer VM, downloaded from https://developer.microsoft.com/en-us/m ... tools/vms/
- RAM: 4GB
- Video RAM: 64MB

Below are the timings for how long it takes to boot the guest VM (complete when you see the start button):

VirtualBox 4.3.32:
        - 4 CPU: 0:24
        - 10 CPU: 0:30
        - 16 CPU: 1:06
VirtualBox 4.3.38:
        - 4 CPU: 0:23
        - 10 CPU: 0:30
        - 16 CPU: 0:48
VirtualBox 5.0.4:
        - 4 CPU: 0:22
        - 10 CPU: 1:44
        - 16 CPU: 3:36
VirtualBox 5.0.22:
        - 4 CPU: 0:21
        - 10 CPU: 1:40
        - 16 CPU: 4:15

I'm not 100% sure that this is the cause of the issue. But, by doing ""truss"", ""pstack"" and ""pfiles"" commands, I found that several stack traces that are performing a tremendous amount of ioctl() system calls against the /dev/vboxdrv device. Here are some of the stack traces:

Stack Trace 1:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185687, ffff80ffbe13ddc0)
     ffff80ffa385df0f SUPR3CallVMMR0Ex () + 30f
     ffff80ffa0accad3 _Z19vmR3HaltGlobal1HaltP6UVMCPUjm () + 1e3
     ffff80ffa0acd004 VMR3WaitHalted () + f4
     ffff80ffa0a62d66 EMR3ExecuteVM () + 656
     ffff80ffa0acbbcf _Z25vmR3EmulationThreadWithIdP11RTTHREADINTP6UVMCPUj () + 12f
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}


Stack Trace 2:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185698, ffff80ffbcbceda0)
     ffff80ffa3862442 SUPSemEventWaitNoResume () + 82
     ffff80ff9fd3d440 _Z15ahciAsyncIOLoopP9PDMDEVINSP9PDMTHREAD () + 330
     ffff80ffa0a87aea _Z15pdmR3ThreadMainP11RTTHREADINTPv () + 6a
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}


Stack Trace 3:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185698, ffff80ffbc2fcc60)
     ffff80ffa3862442 SUPSemEventWaitNoResume () + 82
     ffff80ffa0b45828 _Z29pdmR3R0CritSectEnterContendedP11PDMCRITSECTmPK15RTLOCKVALSRCPOS () + 98
     ffff80ffa0b45914 PDMCritSectEnter () + a4
     ffff80ffa0a98424 PGMR3PhysReadExternal () + 34
     ffff80ffa0a7a4e8 _Z20pdmR3DevHlp_PhysReadP9PDMDEVINSmPvm () + 78
     ffff80ff9fd0b4f4 _Z17ohciR3ThreadFrameP9PDMDEVINSP9PDMTHREAD () + 254
     ffff80ffa0a87aea _Z15pdmR3ThreadMainP11RTTHREADINTPv () + 6a
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}

Currently, this issue prevents us from using 5.0.x at all."	KSJohn
14525	Mini toolbar does not show up in fullscreen mode	all	VirtualBox 5.0.2	2015-08-31T21:14:08Z	2015-08-31T21:14:08Z	2015-08-31T21:14:08Z	"When the guest VM is set to full screen mini-tool bar disappears.
It appears for a while when I switch between application (Alt+Tab) but disappears when VM gets focus.
Looks like the mini-tool bar is not a part of VM window but runs in a separate window.

The problem not fixed in development build VirtualBox-5.0.3-SunOS-amd64-r102322.

Host: OpenIndiana 151a9 x86_64 (pkgadd says 'Detected Solaris 11 Version 151'),
VirtualBox 5.0.2-SunOS-amd64-r10209, Extension Pack: 5.0.2-102096

Guests: Linux 32 and 64 bits, Windows 32 and 64-bit."	virtit
15253	USB does not with VirtualBox 5.x on OpenIndiana	Windows	VirtualBox 5.0.14	2016-03-18T05:12:42Z	2016-03-18T05:12:42Z	2016-03-18T05:12:42Z	"Guest: Windows XP with CH-340 USB to Serial driver installed
Host: SunOS watt 5.11 oi_151a9 i86pc i386 i86pc  (OpenIndiana)
VirtualBox: 5.0.14 with the extension pack installed

The USB to Serial adapter works fine in VirtualBox 4.*, but does not communicate in Virtual 5.x. The device does enumerate and shows up in the guest's Device Manager.

The VM log contains a number of:
00:00:37.203270 USBProxy:Command 0xc0185694 failed. Req.rc=VERR_PIPE_IO_ERROR
00:00:37.203291 USBProxy:usbProxySolarisUrbQueue Failed!! pProxyDev=0000000002828360[proxy 1a86:7523] pUrb=000000000282a5f0 EndPt=0x1 bEndpoint=0x81 enmType=3 enmDir=1 cbData=8 rc=VERR_PIPE_IO_ERROR

followed by...

00:00:39.525634 PCNet#0: Init: ss32=1 GCRDRA=0x01ae4420[64] GCTDRA=0x01ae4020[64]
00:00:41.820029 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:42.208793 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:52.389837 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices

Current workaround is to remain on VirtualBox 4.x
"	Deece
14864	VDI eviroment bugs	Windows	VirtualBox 4.3.30	2015-11-24T13:33:51Z	2015-11-25T12:51:45Z	2015-11-25T12:51:45Z	Hi I hope somebody can help me, We are running 25 sunrays in a class with sunray server and a custom broker. Since we upgraded to 4.2.28 from 4.3.30 we are getting strange bugs frequently. We are connected to the VRDEport(console connected) to the running VM. 1. When a user logs off the screen snaps to the smallest 8bit resolution which leave the user with a small screen with mangled colours a windows reboot solve the issue but would like to know what the cause is. 2. When a user logs out it remains on logging off and needs to be powered off hard and started up to recover.   	Reniervdw
11720	Solaris Autostart service can only work for 1st user in staff group => fixed in SVN	other	VirtualBox 4.2.12	2013-04-15T18:20:24Z	2017-04-17T07:21:00Z	2017-04-17T07:21:00Z	"
First:
The use of ""exec"" in smf-vboxautostart.sh breaks the loop through the users as it replaces the current process with the ""su"" process. It also prevents the immediately following exit status check from functioning.

Second:
The smf-vboxautostart.sh script loops over the ""staff"" Unix group instead of the ""vboxuser"" Unix group to determine which users to look for to start autostart-enabled VMs.
The use of the ""vboxuser"" group makes more sense than ""staff"" as not all companies use ""staff"" for their users, and the ""vboxuser"" group is a required group for anyone running VirtualBox anyways.

Third:
Looping through ""logins -g ''group''"" includes 5 columns of data (including the GECOS field), so it will be looping over UID, group, GID, first name, last name, etc. as well as the username. At a minimum, it should be piped through ""cut -d' '  -f1"" to strip out the irrelevant data.
{{{
        # Get all users
        for VW_USER in `logins -g staff`
        do
            exec su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""

            VW_EXIT=$?
            if [ $VW_EXIT != 0 ]; then
                echo ""VBoxAutostart failed with $VW_EXIT.""
                VW_EXIT=1
                break
            fi
        done
}}}

I suggest changing it to the following (diff attached):
{{{
        for VW_USER in `logins -g vboxuser | cut -d' ' -f1`
        do
            su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""

            VW_EXIT=$?
            if [ $VW_EXIT != 0 ]; then
                echo ""VBoxAutostart failed with $VW_EXIT.""
                VW_EXIT=1
                break
            fi
        done
}}}

The above fixes all three problems: autostart VMs not starting unless you're 1st in the list; users not in ""staff"" group not having VMs started); and attempting to su to groups, numbers, etc.
(diff attached)

Note the diff also contains a clarification of error output for the top section where it checks if a file is executable, then if it exists. I reversed those and changed the error to make more sense.
{{{
--- /opt/VirtualBox/smf-vboxautostart.sh.orig   Fri Apr 12 12:19:08 2013
+++ /opt/VirtualBox/smf-vboxautostart.sh        Mon Apr 15 19:23:31 2013
@@ -24,13 +24,13 @@
 
 case $VW_OPT in
     start)
-        if [ ! -x /opt/VirtualBox/VBoxAutostart ]; then
+        if [ ! -f /opt/VirtualBox/VBoxAutostart ]; then
             echo ""ERROR: /opt/VirtualBox/VBoxAutostart does not exist.""
             return $SMF_EXIT_ERR_CONFIG
         fi
 
-        if [ ! -f /opt/VirtualBox/VBoxAutostart ]; then
-            echo ""ERROR: /opt/VirtualBox/VBoxAutostart does not exist.""
+        if [ ! -x /opt/VirtualBox/VBoxAutostart ]; then
+            echo ""ERROR: /opt/VirtualBox/VBoxAutostart is not executable.""
             return $SMF_EXIT_ERR_CONFIG
         fi
 
@@ -51,9 +51,9 @@
         [ -z ""$VW_LOGINTERVAL"" ] && VW_LOGINTERVAL=86400
 
         # Get all users
-        for VW_USER in `logins -g staff`
+        for VW_USER in `logins -g vboxuser | cut -d' ' -f1`
         do
-            exec su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""
+            su - ""$VW_USER"" -c ""/opt/VirtualBox/VBoxAutostart --background --start --config \""$VW_CONFIG\"" --logrotate \""$VW_ROTATE\"" --logsize \""$VW_LOGSIZE\"" --loginterval \""$VW_LOGINTERVAL\""""
 
             VW_EXIT=$?
             if [ $VW_EXIT != 0 ]; then
}}}


I started a forum post on this, originally thinking the problem was the use of null arguments to options when calling VBoxAutostart (before I noticed the ""exec""), as VBoxAutostart fails under those conditions.
[https://forums.virtualbox.org/viewtopic.php?f=11&t=55006]

"	kburtch
11032	VBox 4.2 on Solaris 11/11 with bonding locks up network adapter	all	VirtualBox 4.2.0	2012-10-05T23:11:30Z	2012-10-22T17:20:54Z	2012-10-22T17:20:54Z	"I am running Solaris 11/11 SRU 11.

I have two onboard network adapters which I had bonded.  Both e1000e drivers.

I understood that virtualbox would not work properly with bond0 without vnics created.  So I created a vnic for each Guest with the guests mac.  After aprox 2 days of operation, the entire host machine will no longer be network accessible.  There are no system log messages about any issues and VBoxSvr does not have any information. This of course crashes any VBox that is using iSCSI harddrives.

I was able to reproduce this issue twice. Each time taking 2 to 3 days for the problem to manifest.

I have since unbonded the adapters and set net0 as the primary bridgeadapter for all VMs and let the vbox network driver create its own vnics over net0.  This has been running stable for 2 weeks now.

I have an identical hardware box also running Solaris 11/11 SRU 11 with bonding turned on. This box ONLY serves up iSCSI targets and has not exhibited the same behavior.

Hopefully I can get a third box where I can try reproducing it on that without disrupting production."	norchem
10957	"website: add link to ""vboxsvc"" project (enhanced SMF management of VMs on Solaris-based hosts)"	all	VirtualBox 4.2.0	2012-09-18T08:59:16Z	2012-09-18T08:59:16Z	2012-09-18T08:59:16Z	"The http://www.virtualbox.org site lists some useful open-source projects that can be used along with VirtualBox. I suggest adding there a link to the ""vboxsvc"" project, which is hosted on SourceForge at http://sourceforge.net/projects/vboxsvc/ and its discussion is in VirtualBox forum, thread ""[Free as in beer] SMF service for VirtualBox VM's"" http://forums.virtualbox.org/viewtopic.php?f=11&t=33249.

This project provides an SMF method script and manifest to wrap execution/hibernation/shutdown of each VM as a separate SMF service instance, and lifetime monitoring (i.e. a frozen VM can be forced to reboot), as well as optional automated ZFS snapshot creation upon VM startup/shutdown, and many other administrative features. An SVR4 package of the project deliverables is also available.

In comparison with VirtualBox 4.2.0 automated VM startup support there are a few differences which may be important in more advanced setups - but available only for solutions built on Solaris 10, OpenSolaris and its relatives (using SMF and ZFS):
* With vboxsvc, each VM is an SMF instance, which allows to enable-disable them independently, and to build SMF dependency graphs between VMs and/or other system services and resources for automatic startup and shutdown/savestate of VMs.
* You can monitor the VM's functionality (i.e. test that it is ""pingable"" or that a webserver inside it responds), and accordingly restart the SMF service or put it into maintenance; you can also delay the exit is start-method until the VM actually works (needed for dependencies to start at a right moment in time and not after a delay randomly selected by admins).
* You can automate taking snapshots of ZFS-backed VM filesystem resources (including those on remote storage hosts available to VBox host via NFS or perhaps CIFS) before start/after stop to keep track of relatively stable points in time.
* There are some other differences, such as getting X11 control of a VM and then passing its execution back to headless SMF controller and various other ""nifty features"", all with configurable SMF attributes."	Jim Klimov
8789	Shared Folders doesn't honor guest OS DAC settings	Windows	VirtualBox 4.0.2	2011-04-25T15:43:28Z	2011-05-09T19:33:13Z	2011-05-09T19:33:13Z	"When using VBoxHeadless vrdp -off and set a mount point on the NFS shared (/export/home/COMMON_SHARE) we noticed that the files that are copied to NFS share from the guest OS show DAC root:root instead of the user DAC settings from the guest OS. The user account exists on both Host and Guest (same UID/GID) example testuser1/staff.

Guest OS: Windows Server 2003 STD R2
Host OS: Solaris 10 v10/09
Extension pack for 4.0.2 installed"	Ronald MacDonald
6985	"""Configuring the BIOS DMI information"" documentation needs improvement"	Windows	VirtualBox 3.2.4	2010-06-14T02:01:36Z	2010-06-14T12:44:22Z	2010-06-14T12:44:22Z	"I am trying to use the ""VBoxManage setextradata"" feature described in that section of the manual to set up the DMI data so that my VM looks like my actual system, in this case an Acer Ferrari 3400 laptop, so that the version of Windows XP that came with it will install.

However the example given in the documentation does not show which DMI information from dmidecode to use for which parameters.  Several that are shown as being something you can change, like the Release and BIOS Major/Minor values, do not show up in the dmidecode output I see.

I would be very helpful to show example output of dmidecode from a specific system and then show how you use it to set the various values, and what to do if no such value is present.

I have included the full output of dmidecode for my laptop for you to see what it looks like as an attachment to this report.
"	Mike Riley
4427	active FTP doesn't work with NAT	Windows	VirtualBox 3.0.0	2009-07-07T23:40:24Z	2019-09-05T02:54:35Z	2019-09-05T02:54:35Z	"This is with a 64-bit OpenSolaris host (2009.06).  It happens with all tested guests (XP, Ubuntu, OpenSolaris, Solaris 10), both with NAT and bridged networking.  The problem did not exist prior to 3.0.0, and has been confirmed both with pre-existing guests and newly created guests.

When you open an FTP session from the guest to the OpenSolaris host, the host returns an error like this one from a NAT guest:

Jun 21 19:50:21 fnog ftpd[1902]: [ID 227848 daemon.warning] refused PORT 10.0.2.15,60783 from fnog [192.168.99.22]

192.168.99.22 is the host IP.

If you do the same with VB 2.2.4 on the same host, ftpd logs no errors and successfully connects the guest.  This has been tested on two different hosts.  Both tested installations of the host OS use an unmodified default ftp configuration.

With FTP servers on the Internet, VB guests connect, but are unable to list files or directories on the FTP server using either the 'ls' or 'dir' commands.  The same FTP servers interact normally with computers that are not VB guests.  One tested example would be ftp.sunfreeware.com.

Shared folders and SSH/SCP/SFTP exhibit no observed problems from guest to host, but are slower for large transfers and for network testing.

I will be attaching a log file soon."	bqbauer
3473	alt+printscreen and windows-logo+E  used to work but now do not	Windows	VirtualBox 2.1.2	2009-03-02T14:27:17Z	2011-03-21T16:26:07Z	2011-03-21T16:26:07Z	"Hi,

on a solaris host (snv_103 X86) with windows XP guests

   ( in all cases below guest additions were installed )

In 2.0.6 I was able to pop up windows explorer with the standard keyboard shortcut of windows-logo key + 'E'

I was also able to take a ""snapshot"" of the active microsoft window with alt+printscreen (for pasting into Word or an Image Tool or whatever)

In 2.1.2 I no longer can.

At first I thought maybe it was me .... but I uninstalled 2.1.2 and re-installed 2.0.6 and the functionality returned.

I recently installed 2.1.4 and the alt-prtscreen seems to work (it seems slower but I'll take it)  BUT the windows-logo key + 'E' to pop up windows explorer still does not work.

If I can be of help to a developer I'm happy to try things out.
"	cj
3072	Seamless mode prevents drag to host desktop	other	VirtualBox 2.1.0	2009-01-18T18:15:13Z	2010-04-09T07:19:46Z	2010-04-09T07:19:46Z	"When running a guest in seamless mode on my 64-bit OpenSolaris host, I am unable to drag and drop anything to the host's desktop, whether that is a URL from firefox, or a file from within nautilus.  I cannot even move a desktop icon around unless I first ""minimize"" the guest or switch it out of seamless mode.

I have observed this with all releases since at least 2.0.  I am not trying to drag items between guest & host--this is regarding only the host's desktop, icons, and files."	bqbauer
