Opened 13 years ago
Closed 13 years ago
#10622 closed defect (worksforme)
VBox 4.1.14 w guest Win7 crashes after several days, is not working anymore
Reported by: | gucky | Owned by: | |
---|---|---|---|
Component: | host support | Version: | VirtualBox 4.1.16 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Solaris |
Description (last modified by )
Hi folks,
my VB installation isnt working anymore. the 4.1.14 inst. has crashed some days before, rm of all VM dir and files, pkgrm and installation of the actual version doesnt work. The main window appears, after several sec VM is coredumping.
The machine was started with root-rights, actual there is no VM attached or created
My system:
SunOS r2d4 5.11 11.0 i86pc i386 i86pc VBoxlog cat VBoxSVC.log VirtualBox (XP)COM Server 4.1.16 r78094 solaris.amd64 (May 22 2012 14:31:38) release log 00:00:00.001 main Log opened 2012-05-29T17:53:14.513355000Z 00:00:00.001 main OS Product: SunOS 00:00:00.001 main OS Release: 5.11 00:00:00.001 main OS Version: 11.0 00:00:00.001 main OS Service Pack: 11.0 00:00:00.001 main Executable: /opt/VirtualBox/amd64/VBoxSVC 00:00:00.001 main Process ID: 3301 00:00:00.001 main Package type: SOLARIS_64BITS_GENERIC 00:00:00.118 nspr-2 Loading settings file "/root/.VirtualBox/VirtualBox.xml" with version "1.12-solaris" 00:00:01.226 nspr-2 VDInit finished 00:00:14.598 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
hope somebody could help
thanks a lot best regards
Change History (6)
comment:2 by , 13 years ago
Sorry for the code"salad"
Replying to gucky:
Hi folks,
my VB installation isnt working anymore. the 4.1.14 inst. has crashed some days before, rm of all VB dir and files, pkgrm and installation of the actual version doesnt work. The main window appears, after several sec VM is coredumping.
The machine was started with root-rights, actual there is no VM attached or created
My system:
SunOS r2d4 5.11 11.0 i86pc i386 i86pc
VBoxlog
cat VBoxSVC.log VirtualBox (XP)COM Server 4.1.16 r78094 solaris.amd64 (May 22 2012 14:31:38) release log 00:00:00.001 main Log opened 2012-05-29T17:53:14.513355000Z 00:00:00.001 main OS Product: SunOS 00:00:00.001 main OS Release: 5.11 00:00:00.001 main OS Version: 11.0 00:00:00.001 main OS Service Pack: 11.0 00:00:00.001 main Executable: /opt/VirtualBox/amd64/VBoxSVC 00:00:00.001 main Process ID: 3301 00:00:00.001 main Package type: SOLARIS_64BITS_GENERIC 00:00:00.118 nspr-2 Loading settings file "/root/.VirtualBox/VirtualBox.xml" with version "1.12-Solaris" 00:00:01.226 nspr-2 VDInit finished 00:00:14.598 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
comment:3 by , 13 years ago
Description: | modified (diff) |
---|
comment:4 by , 13 years ago
Hi Folks,
PROBLEM SOLVED ++++++
after several deinstalls and reinstalls :
Somehow Virtualbox check the permission for the /opt directory these should be 755 owner root / grp sys It seems that VB is thinking that everything higher than gid 0 is ++NOT++ a system-grp.
and something ++ not me as far as I know ++, maybe during packetinstallation, changed the permissions.
The question is, why is VB checking the permission on /opt ?
May there should be a hint during the installation or during the startup of VB.
comment:5 by , 13 years ago
I can only answer the question regarding why does VBox check the permissions of /opt. The reason is that VirtualBox is system software which has special privileges. If the permissions of the directory where VirtualBox is stored would be wrong then an unprivileged user could replace some binaries and could do bad this. Same problem if a user could write to parent directories (e.g. /opt). Some checks are perhaps a bit pedantic but better safe than sorry.
comment:6 by , 13 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Looks like some weird Qt crash while checking for updates. Please re-open if this problem resurfaces since you mention the problem is solved/disappeared. Closing this ticket for now.
Here is pstack core: