virtualbox.org

Dear friends.

My guest OS crashes after starting nested VM.
Error message is : a critical error has occurred while running the virtual machine and machine execution has stopped

Host: Windows 10x64
Guest: Windows 10x64
Guest in guest: Linux x64 (boot2docker image).

Attaching logs (grabs them from context menu item "Show log") for guest VM and for nested VM.

Could you please help to run nested VM?
Thank you in advance for any ideas and help.

00:00:03.174160 OS Product: Windows 10
00:00:03.174161 OS Release: 10.0.17134

I don't know if this is pertinent but you're running Windows 10 1803 according to Wikipedia. I don't remember if there is a version requirement for the Windows host OS.

You have all four host CPUs available for guest usage:

00:00:03.391334 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:04.408496 CPUM: Physical host cores: 4

The hyperthreads don't help Virtualbox. If the first guest goes full throttle on all four cores the host could suffer.

The nested guest log is extremely truncated, and just about all of the diagnosable data is missing. Please start your "Win10_2_123" guest and run:

vboxmanage showvminfo "name_of_Linux_guest"

Then post the text (not screenshot) output of the command here, as a zipped text file, like you did the logs zip.

One piece of data in the nested log is:

00:00:03.497158 Host RAM: 4095MB (3.9GB) total, 838MB available

That's not much for the guest to run. XP could do it, DOS easily. Early Linux?

VkTester wrote:boot2docker image

If this is https://github.com/boot2docker/boot2docker, please try a standard lightweight third guest. The description of Docker looks an awful lot like a virtual machine, which appears to be setting up for nested nested virtualization (sic), 4 layers.

scottgus1 wrote:standard lightweight third guest

Hi, thanks for quick reply.
Tried 3 lightweight linux cores:
1) Tiny linux (Core)
2) Puppy
3) Docker

Result the same - guest crashes after starting any.
Attaching logs (result of showvminfo) for all 3 nested VM.

Could you please take a look to the logs?

Thanks for trying those other OS's.

all three showvminfo's wrote:Memory size 1024MB

the first guest log wrote:00:00:03.497158 Host RAM: 4095MB (3.9GB) total, 838MB available

There be not enough spare memory in that middle guest for the next layer. Try reducing, if the guest OS allows, to 512 or 256MB.

Or try a different, less demanding middle guest. Windows 10 is a hard hit on any layer of virtual machine.

scottgus1 wrote: to 512 or 256MB

Tried both - result is the same.
Changing Win10 to other OS is not possible, unfortunately.