svmi :: latest features

[techAdmin]

svmi updated, thanks

[techAdmin]

Finally, added auto download/install and pre-install removal/cleanup of
Oracle VM VirtualBox Extension Pack
when installing vbox-non ose versions 4 or greater.

Added detection of running vbox components, and exit on error, this avoids
various install failure issues on removing old packages and vbox instances.

why now? well, because I finally updated to vbox 4.x and realized this was needed. Someone has mentioned this before, but no patches appeared so I didn't worry about it.

Also updated to handle potential new kernel string syntax, 3.xx (as opposed to 3.0.xx

[iotaka]

New VirtualBox 4.0.10

[techAdmin]

svmi updated, thanks

[drb]

h2,

the version 4.0.10 extension pack version isn't aligned to the VB 4.0.10 version . . . . it's 72436 (not 72479)

drb

[techAdmin]

nice to see oracle/sun vbox still maintaining their randomness release to release.

I guess what will be needed is the extension pack version number being coded in separately, sigh...

Why those matched and now do not match is beyond me, that can't have been a coincidence.

[techAdmin]

ok, sigh, updated svmi to have a separate extension pack number. For versions 4.0.0 to 4.0.8 oracle / sun had the numbers synced, but in 4.0.10, the redhat number and the other numbers were different, and the extension pack number was synced to the redhat number. Now svmi will simply hardcode in the extension pack number along with the vbox file number.

[techAdmin]

vbox 4.0.12 added.

[techAdmin]

vbox 4.1.0 added.

[drb]

I installed 4.1 and virtualbox runs without any problems . . .until I shut down. Everything fine till the power off point and then a kernel panic which requires a hard reset.

:: Code ::

/etc/init.d/vboxdrv stop

before shutting down allows a clean shutdown.

I've tried downloading new copies of virtualbox and extensions in case it was a corrupted file issue but have the same problem. Reverted back to virtualbox 4.0.12 and everything is fine.

Any ideas?