(SOLVED)Two machines refuse Virtual Box Win7 guest install

[besonian]

Can anybody help with this? I've been trying to install - from the Get Virtual Box script - Win7 Ultimate. I go through all the usual configuration procedures, and as soon as I click on 'Start' to begin the install, I get the following -

"Failed to open a session for Virtual machine Win7
The Virtual machine Win7 has terminated unexpectedly during startup
because of Signal 11

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}"

I'm getting exactly the same thing on two separate machines, the first running LXDE (up to date) and the second a Dell laptop running Gnome (up to date).
I've tried installing Vista - in case it has something to do with the Win7 disc - but the result is exactly the same.

I've installed Virtual Box a number of times before (on other machines) but have never hit this. Can anybody give me an idea what's wrong or what I'm doing wrong?

[menotu]

Have you rebooted since the Virtualbox install?

[besonian]

Menotu - very strange. I never got as far as the install - as soon as I clicked on 'Start' to begin it, I got that message. However, having read your post, I tried again. Clicked on 'Start', got the same error message once more. Even so, I rebooted. To my amazement, everything then worked - on both machines. Was I missing some direction? What was that about? Anyway, whatever - it's all running now. So - I don't know what you did but thank you.

[menotu]

Was I missing some direction?

Great - pleased it's up and running.

I believe Virtualbox sometimes needs to (for want of a better term) "rebuild" itself into the system therefore a reboot often helps - I find it useful especially after any large update and VBox installs.

If memory serves - one time when I added a new kernel and rebooted one of the items I noticed being "rebuilt" - along with various other modules - was virtualbox therefore I tend to reboot after I install it.

Not certain whether any of this is actually necessary but a reboot often cures minor niggles plus I find it helps keep my systems nice and tidy (and refreshes memory)

[besonian]

Menotu - like you I quite often do a reboot for the same reasons. But I doubt I'd have done so in this case - the message was quite unequivocal - 'can't do it!' However, yet again one learns a little more. Thank you again.

[Xenaflux]

Had the same issue a few weeks ago.
Reboot the system and all was OK

[uncleV]

Even so, I rebooted. To my amazement, everything then worked - on both machines. Was I missing some direction?

If I remember correctly GetVirtualBox script explicitly tells to reboot at the end of installation of VB.