search

mmumshad / kubernetes-the-hard-way

Bootstrap Kubernetes the hard way on Vagrant on Local Machine. No scripts.
Apache License 2.0
4.6k stars 4.48k forks source link

fix Kernel Panic while provisioning #293

Closed walidayada92 closed 10 months ago

walidayada92 commented 2 years ago

Update Load Balancer and worker Node with higher value vb.cpus to be 2 to fix "Kernel Panic not syncing: Attempted to kill the idle task!" while provisioning

fireflycons commented 2 years ago

Hi @walidayada92

What is the setup of the machine you were running this on (OS, Number of CPU cores, amount of RAM)?

We are about to merge a major update to this to bring it up to v1.24, and this includes changes to the vagrantfile - and to upgrade to ubuntu 22.04, therefore this PR won't be merged as is.

Once the upgrade is merged, we invite you to test it again using the latest versions of vagrant and virtualbox to see if the issue persists.

walidayada92 commented 2 years ago

@fireflycons The Setup of the machine which being generated by vagrantfile (Ubuntu 18.04.6 LTS) , CPU and Memory same as the mentioned on the vagrantfile
vb.memory = 512 vb.cpus = 1 with this setup the issue happened Kernel Panic while provisioning Load Balancer and worker Node and being solved by updating the value of vb.cpus = 1 to be vb.cpus = 2 for both Virtualbox Version 6.1.38 r153438 (Qt5.6.2)

fireflycons commented 2 years ago

@walidayada92 I meant the setup of your workstation i.e. your Mac or Windows box, whatever you are running this on, not the VM.

We have now merged the v1.24 upgrade, so please try it again. I have tested this on Windows 10, 32GB RAM, 12 core i7 CPU using VirtualBox 6.1.38-153438, Vagrant 2.2.19.

There is no kernel panic in the VMs.

Should you still be getting it, please post the full output of the panic.

fireflycons commented 10 months ago

Closing this as the repo is receiving a refresh to latest version of kube