virtualbox.org

Remove the old extension pack to whatever extent the GUI will let you, then use "VBoxManage extpack cleanup" to make doubly sure it's gone. Then check the VBox program extpack folder to make trebly sure that it's empty, then you can install the new extpack.

mpack, thanx for your help. I tried it out, but it does not work to install extension pack into a fresh Solaris 11.1 and fresh v3.4.6. Neither does it work when I execute your suggestions. it says:

Failed to install the Extension Pack
The installer failed with exit code 255:
Result code: NS_ERROR_FAILURE (0x8000040005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

Now what should I do? Can someone from Oracle chime in with a suggestion?

mpack wrote:

klaus4040 wrote:My i7-2670QM (quad code with HT -> 8 virtual cores) now also only shows 4 cores.

You have a quad core processor, and VBox now agrees you have a quad core processor. What's the beef? Intel page for i7-2670QM. Are you really complaining that you can't assign cores to a VM without regard to how many you actually have?

z_hopa's situation seems to be different,
at least as claimed so far.

Were you able to reproduce my scenario? Any plans on putting the old core enumerator code back?

Brutalizer wrote:mpack, thanx for your help. I tried it out, but it does not work to install extension pack into a fresh Solaris 11.1 and fresh v3.4.6. Neither does it work when I execute your suggestions. it says:

Failed to install the Extension Pack
The installer failed with exit code 255:
Result code: NS_ERROR_FAILURE (0x8000040005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

Now what should I do? Can someone from Oracle chime in with a suggestion?

Same problem persists with v4.3.4. Extension pack can not be installed on a fresh Solaris 11.1 and fresh VirtualBox install.

Nope, can not install Extension pack at all. Tried to downgrade each release down to v3.2.20 to no avail. The thing is, I need USB support in VB, and I need extension pack for that. v3.2.20 had no extpack to install. So... what could the problem be? Why is it not possible to install extension packs in VirtualBox on Solaris 11.1 at all? Can anyone install extension packs on a fresh Solaris 11.1? Or do I need some additional libraries? Fresh Solaris 11.1 does not work?

One note though: I had a WindowsXP VM created long time ago, maybe in v3.xx or so. That VM followed me up to v4.3.6 on Solaris 11 Express without problems. Then I recently bought a new PC and installed Solaris 11.1, and VB v4.3.6. And tried to import the cloned VM with success (VB said something about sound not working properly, but sound works fine except the volume control. I need to control the volume from WinXP, the Solaris global volume control does not work at all). And then I tried to install the extension pack and all these problems arose, just like the guy at Google Group I linked to earlier. I can even uninstall the old extension packs properly.

Can it be the case that you must install the extension pack, before creating/importing any VMs? The extension pack needs a clean VB install? No VMs can be created/added before? Any suggestions? Hmmm... does it say in the manual you must install extension packs before any VMs?

EDIT: I installed v4.3.6 again from v3 something. I have no registered VMs now (lost that info when downgrading far below). Version 4.3.6 said something about "you have an old extpack, do you want to download and install the latest?". I said yes but this failed too. Could not install the latest ext pack version "exit code 255". This seems to be quite an annoying problem. Any suggestions how to circumvent this problem? I need USB support to access USB memory sticks (I am trying to install Windows 8 dual boot on my PC. Solaris and Windows dual boot).

Should I file it as a bug?

PS. I have a Supermicro X10SAT motherboard, and Xeon 1245v3, and 32GB ECC RAM. All servergrade stuff. And fresh Solaris 11.1. Also server stuff. And VirtualBox v3.4.6. So, it is not a weird homebrewn combination of hardware I have. It should work with server hardware? Should I file a bug?

Unless some other Solaris user responds, most of us here can't give you any definitive answers. If you have a repeatable problem (meaning: something which someone else can repeat) then you should certainly file a bug ticket.

mpack wrote:Unless some other Solaris user responds, most of us here can't give you any definitive answers. If you have a repeatable problem (meaning: something which someone else can repeat) then you should certainly file a bug ticket.

Yes, that sounds reasonable. Can someone with a supermicro motherboard and Xeon cpu try to install extension pack on a fresh Solaris 11.1 install? Anyone has access to such hardware?

The brand new Supermicro X10SAT is not really supported by Solaris 11.1 yet. There are no drivers for Lynx point serial connection, and no drivers for the ethernet card. Could this be the problem? Or is it a bug i VB? Hmm....

z hopa wrote:

mpack wrote:

klaus4040 wrote:My i7-2670QM (quad code with HT -> 8 virtual cores) now also only shows 4 cores.

You have a quad core processor, and VBox now agrees you have a quad core processor. What's the beef? Intel page for i7-2670QM. Are you really complaining that you can't assign cores to a VM without regard to how many you actually have?

z_hopa's situation seems to be different,
at least as claimed so far.

Were you able to reproduce my scenario? Any plans on putting the old core enumerator code back?

Any news regarding core enumeration on AMD Phenom II?

Have you tried 4.3.8?

Perryg wrote:Have you tried 4.3.8?

Who are you replying to?

z hopa wrote:

Perryg wrote:Have you tried 4.3.8?

Who are you replying to?

Presumably, Perry is replying to anyone who may not be aware that 4.3.6 is no longer the latest version, e.g. people who are still posting questions in the 4.3.6 release topic.

mpack wrote:

z hopa wrote:

Perryg wrote:Have you tried 4.3.8?

Who are you replying to?

Presumably, Perry is replying to anyone who may not be aware that 4.3.6 is no longer the latest version, e.g. people who are still posting questions in the 4.3.6 release topic.

Until I heard back that CPU enumeration problem has been fixed or at least attempted to be fixed, I am not motivated to 'give it a try' which would mean uninstalling a perfectly working 4.3.4 and taking chances with 4.3.8 which may or may not work. I am using VMs for real world work and trying means downtime.

z hopa wrote: Until I heard back that CPU enumeration problem has been fixed or at least attempted to be fixed, I am not motivated to 'give it a try' which would mean uninstalling a perfectly working 4.3.4 and taking chances with 4.3.8 which may or may not work. I am using VMs for real world work and trying means downtime.

That being the case, why do you want to upgrade at all? Is there something that you want that has been incorporated since 4.3.4 ?

I always have a dev unit that I test the builds with before I go live in prod. I have a few prod units that are still in 3.* and just work.

Keeping in mind the old adage if it ain't broke.....