virtualbox.org

Hi

I have an windows 8.1 x64, 16 GBRAM, Core i7

I made a Oracle Virtual Box (3 GB RAM, XP sp3, 50GB VHD)

Sometimes, when i work on my XP VM, suddendly crahs and get aborted.

What could be happened?

Thanks

If you go to the doctor and you tell him/her that "sometimes" "something" hurts, do you expect a diagnosis? I wouldn't think so. If you want to continue this discussion, please see: Minimum information needed for assistance. Choose a log file from when your guest crashes.

Hi,

This is minimal information you requested.

The version of VirtualBox you are using, and whether you have installed the Guest Additions (in the guest).

VirtualBox VM 4.3.15 r95286
00:00:02.005920 Installed Extension Packs:
00:00:02.005967 Oracle VM VirtualBox Extension Pack (Version: 4.3.14 r95030;


Host & Guest make and version including 32 or 64 bit, and the amount of memory available to both.
Host Windows 8.1 x64 - 16 GB Ram
Guest Windows XP SP3 x32 - 3 GB Ram


Guest log file (as an attachment) See your VirtualBox users guide for how to locate this if using CLI or right click the guest in the VirtualBox main manager and select show log. Then choose save.

Attached.

4.3.15? That is a test build which you should have replaced long ago with either 4.3.16, 4.3.18, or 4.3.20.

ok,

I'll try with 4.3.20

thanks!

Hi

Yesterday i installed the 4.3.20 version, and ran the VM

Today I found the VM aborted again!,

Check the log.

What could be the problem?

Tks.

Vbox.log wrote: 00:00:01.730514 RamSize <integer> = 0x00000000c0000000 (3 221 225 472, 3 GB)

3GB is excessive for an XP VM. The maximum I would give is 1GB.

Vbox.log wrote: 00:00:02.103740 Hypervisor Present (we're a guest) = 0 (1)

Nested VMs are not supported.

Thanks,

I'll set 2 GB to the VM-XP

But...

How can i correct the next parameter?

"Vbox.log wrote:
00:00:02.103740 Hypervisor Present (we're a guest) = 0 (1)
Nested VMs are not supported."

You can't correct it. As it says in the log, "Nested VMs are not supported" and this is by design.

I'd guess that you have Hyper-v enabled on your host. You would need to disable Hyper-v, which will free up VT-x to be used by VirtualBox, and incidentally will probably solve a number of other stability problems with VMs.

mpack wrote:I'd guess that you have Hyper-v enabled on your host. You would need to disable Hyper-v, which will free up VT-x to be used by VirtualBox, and incidentally will probably solve a number of other stability problems with VMs.

Thanks mpack,

i'll disable HyperV and lets see...

Cheers!

Thanks mpack

Your solution was right!!!!

Its been working good since yesterday, i think the VM is more stable.

Thak you Very Much!!!!

Arzamm wrote:

mpack wrote:I'd guess that you have Hyper-v enabled on your host. You would need to disable Hyper-v, which will free up VT-x to be used by VirtualBox, and incidentally will probably solve a number of other stability problems with VMs.

Thanks mpack,

i'll disable HyperV and lets see...

Cheers!