Vagrant -- Node kernel panic when creating virtual machine

[chbalbas]

When Vagrant is rising up the virtual machine I see this error:

    server-01: + docker run --rm --net=host appropriate/curl -s https://127.0.0.1/v3/clusterregistrationtoken -H 'content-type: application/json' -H 'Authorization: Bearer token-m6bmh:whgn5tlh8s6rwvv24j579lv5lhczmfmwgskd7rf7sg657hkzmx4vjz' --data-binary '{"type":"clusterRegistrationToken","clusterId":"c-jd9rx"}' --insecure
    server-01: pong{"baseType":"error","code":"ServerError","message":"Post \"https://127.0.0.1:6443/apis/management.cattle.io/v3/namespaces/c-jd9rx/clusterregistrationtokens?timeout=15m0s\": unexpected EOF","status":500,"type":"error"}
==> node-01: Cloning VM...
==> node-01: Matching MAC address for NAT networking...
==> node-01: Checking if box 'chrisurwin/RancherOS' version '1.5.1' is up to date...
==> node-01: Setting the name of the VM: node-01
==> node-01: Fixed port collision for 22 => 2222. Now on port 2200.
==> node-01: Clearing any previously set network interfaces...
==> node-01: Preparing network interfaces based on configuration...
    node-01: Adapter 1: nat
    node-01: Adapter 2: hostonly
==> node-01: Forwarding ports...
    node-01: 22 (guest) => 2200 (host) (adapter 1)
==> node-01: Running 'pre-boot' VM customizations...
==> node-01: Booting VM...

==> node-01: Waiting for machine to boot. This may take a few minutes...
    node-01: SSH address: 127.0.0.1:2200
    node-01: SSH username: rancher
    node-01: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

In the node-01 stdout:

Any clue to fix that?

Notes:

• VirtualBox version: 7.0.6
• Vagrant version: 2.3.4

[stefanlasiewski]

It's likely that your node didn't have enough RAM and crashed. That's what happened to me, now and in the past.

Bump up node.memory to 2500 or more and it should work.