> From: vbox-users [mailto:[email protected]]
> 
> Using openindiana 151a7, and virtualbox 4.2.6...
> Recently updated from virtualbox 4.1.x
>       poweroff all vm's, and exit VirtualBox
>       sudo pkgrm SUNWvbox
>       sudo pkgadd -d VirtualBox-4.2.6-blah.pkg -n -a autoresponse
> SUNWvbox
>       (followed by launching VirtualBox, and updating Oracle Extensions)
> 
> All my old VM's work fine.  But if I try to create any new VM's, they won't
> launch.  They give this error message.
> Failed to open a session for the virtual machine, exit code 0,
> NS_ERROR_FAILURE (0x80004005)

Well, uh ...  Just in case anybody ever has the same problem again, I might as 
well write what I know here.

I wanted to get a good clean VBox.log for this problem, so I could go submit a 
bug report.  So I shutdown all my guests, closed VirtualBox, did a "ps" to 
verify there's nothing VirtualBox related running (except VBoxZoneAccess).

Launched VirtualBox.  Repeated steps to reproduce problem (create a new guest 
VM, try to launch it) ... and it worked.  Problem is gone.

So, what's the cause of the problem?  I only have two guesses:

1- This is the first time I ever did a VirtualBox upgrade on solaris.  I did 
not know it was a bad idea to have machines in "savestate" state during the 
upgrade.  It quickly became obvious, as I tried to restore machine states, they 
were obviously in a bad state.  So I shutdown and rebooted all guest VM's 
immediately after upgrade.  But I probably didn't completely close out of 
VirtualBox.  It's possible that VirtualBox got into a bad state because of this.

2- I recently reported another bug, a really simple one, VirtualBox refuses to 
create a new machine if the destination directory already exists.  While I was 
figuring this out and preparing to file the bug report, I created a guest VM, I 
shut it down, I renamed the directory that it was in, while VirtualBox was 
still running.  It's possible that Virtualbox pays attention to the directories 
where guest VM's reside, even when they're powered off.  It's possible 
Virtualbox got into a bad state because of me fiddling around not knowing what 
I was doing.

Good luck everyone.


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:  
mailto:[email protected]?subject=unsubscribe

Reply via email to