Failed to open a session for the virtual machine OBIEE Sampl

[mike salvador]

im trying to run the obiee sampleapp 405 on ovirtualbox, so far i have installed virtualbox on my windows 8 host machine, imported the obiee files on to the virtual machine;
i recieved an error telling VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED). This I manage to solve by enabling VT-x on my BIOS setting; so far so good however
as soon as i try to start the vm i get a second error which is

Failed to open a session for the virtual machine OBIEE SampleApp v406.

The virtual machine 'OBIEE SampleApp v406' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

while viewing the log file; I notice there is a warning line WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.

I decided to change Linux virsion via the general settings to Linux 64bit; decided to start the machine again and same error happen again

Can anyone help me, Im completely lost; please see log attachment

[Perryg]

1) 64-bit guests need hardware-virtualzation enabled in the hosts bios.
2) when creating the 64-bit guest you must select 64-bit in General -> Basic -> version.
3) If running Windows as host you must make sure hyper-v or xp mode is not enabled on the host. MS does not play well and wants it all.

[mike salvador]

where do i make sure hyper-v or xp mode is not enabled; i have looked at the settings in the virtual machine; and cannot find it; any help

[Perryg]

That would be the Windows host, not the guest.
The only thing that would cause the disabled in bios other than actually in bios is if something else was using VT-x. I would really look at the hosts bios again though to be sure. Sometimes it is in the security section of the bios.

[mike salvador]

have looked at the bios settings, the vt is enabled, tried to run the virtual box again and the same error occurs; any idea ?

[mpack]

have looked at the bios settings, the vt is enabled

Not according to the log it isn't, and AFAIK the log isn't wrong about such things. If you're saying things have changed then provide a new log.

Don't confuse VT-x with VT-d (redirected I/O) in the BIOS settings. Look for "VT-x", or "Intel Virtualization Technology". Someone recently even reported their BIOS calling it "Vanderpool Technology" - the uninitiated has no chance of understanding that. If necessary ask your PC manufacturer where the option is.

Intel has a small software tool that can tell you the current state of the VT-x option. Don't bother trying to use VT-x in a VBox VM until this tool reports it as available and enabled.

[mike salvador]

right downloaded the the Intel file utility; as far as the programs was concerned vt was enabled see file attachment
i have also removed virtual machine and re-imported it
went to start the vm and the same problem again

see attachment

and this time the virtual box is not even creating a log file

ps i have also tried to disable hardware virtulization via setting on virtual box; but this normally the displays invalid settings warning and re-enables it back

[mpack]

No attachment.

[mike salvador]

apologies

I'm not quite sure what i did; but i decided to go for broke
on the virtual-box settings-->network
I originally chose the NAT option and followed the oracle YouTube video on port forwarding, where i created 4 additional rules. I decided to cancel those rules and leave the option at NAT and not bothering with port forwarding; decided to start the vm and it worked

unbelievable..... so much for following oracle's manual

[mpack]

I'm not aware of any Oracle YouTube tutorial vids - do you have a link?

If you wish to suggest better wording for a user manual section then post something in the Suggestions forum.

[mike salvador]

that's the link https://www.youtube.com/watch?v=cPrjX5VFXrE
for the port forwarding tutorial that came with the obiee sample app deployment guide.
Incidentally everything was working fine all of a sudden decided to take a snapshot of the virtual-box, then stopped the virtual box, came back the following day and the same error happened; apart from windows operating system doing an update nothing else has change but for some reason i'm back to where i started

[mike salvador]

by the way this is the last log before everything went tit's up was wondering whether you can spoot something that I might of missed

[mpack]

A log from before there was any problem? No, I don't see how that can help - though I do notice that the RAM allocation to the guest is way too high given the free mem on this host. And incidentally: choosing 4GB or more for a guest is AFAIK what forces it to 64bit. 32bit processes on Windows hosts don't get that much RAM.

I guess I would try downgrading to 4.3.12.

And, it doesn't seem like a good idea to be using the wrong guest OS template.

Otherwise, it looks straightforward: VT-x has been disabled in the BIOS.