I bounced into the problem of getting the dreaded OVMAPI_4010e error when I was discovering the Oracle VM server in my network. Metalink (MyOracleSupport for the younger ones) told me that this was typically an issue with the password of the OVM Agent.
One obscure internet blog told me however that this was due to the difference in versions. Now - it beats me how the connection information and credentials are passed differently when a new version arrives, but eventually I placed the same version of the OVM Manager as the OVM Server on my Virualbox image and it works.
Obviously I do not run a major Oracle-based OVM data center. So for real-life large enterprises this is not an issue.
However image the following: you have a machine on which you want to run Oracle VM Server.
Installation of the OVM is straightforward and pretty easy.
Now you end up with a piece of equipment that does exactly NOTHING.
Nothing? Yup. Well you can start it and you get a Linux prompt, and that is pretty much it.
Ok - when you do things the first time you make mistakes.
This was my first server I've ever build from scratch. I fiddled around with some equipment before, but buying a number of components and installing them was new for me.
Now the motherboard I have does have no video card as the folks who typically buy these extreme motherboards do bring their own video cards with them to render the monsters they are about to slay.
So - I bought a decently sized system to have my own private cloud on it. The main motivation was the fact that currently it has become pretty difficult to run some Oracle software on your laptop.
Although a number of people do this you quickly realize that they just have a simple database installation on it or a plain WebLogic Server.
BIOS virtualization enabled
Intel Processor Identification Utlility in 8.1: virtualization disabled
Today, I bumped into a problem with accessing the WSM Policy Manager after I changed the listen address of the SOA managed server in my development environment. The administration server was not able to contact the WSM Policy Manager after the change, causing the problem that I could not run any SOA service test from the EM console