search

flatcar / Flatcar

Flatcar project repository for issue tracking, project documentation, etc.
https://www.flatcar.org/
Apache License 2.0
679 stars 29 forks source link

Vagrant virtualbox not starting #158

Open tinjaw opened 4 years ago

tinjaw commented 4 years ago

Description

I wanted to try flatcar so I chose the option to use alpha and virtualbox. The VMs won't start up.

Impact

I am unable to explore flatcar.

Environment and steps to reproduce

vagrant box add -f flatcar-alpha  https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_vagrant.box

vagrant up

Expected behavior successful startup of the cluster

Additional information Please add any information here that does not fit the above format.

(base) chaimkrause@macmini flatcar % vagrant up
Bringing machine 'core-01' up with 'virtualbox' provider...
Bringing machine 'core-02' up with 'virtualbox' provider...
Bringing machine 'core-03' up with 'virtualbox' provider...
==> core-02: Importing base box 'flatcar-alpha'...
==> core-02: Matching MAC address for NAT networking...
==> core-02: Setting the name of the VM: flatcar_core-02_1595511424618_58668
==> core-02: Fixed port collision for 22 => 2222. Now on port 2202.
==> core-02: Clearing any previously set network interfaces...
==> core-02: Preparing network interfaces based on configuration...
    core-02: Adapter 1: nat
==> core-02: Forwarding ports...
    core-02: 22 (guest) => 2202 (host) (adapter 1)
==> core-02: Running 'pre-boot' VM customizations...
==> core-02: Booting VM...
==> core-02: Waiting for machine to boot. This may take a few minutes...
    core-02: SSH address: 127.0.0.1:2202
    core-02: SSH username: core
    core-02: 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.
(base) chaimkrause@macmini flatcar %
goshlanguage commented 3 years ago

If you look at the console, I'd be willing to bet you see a "tsc: Marking TSC unstable due to clocksource watchdog" error as the last log line in VirtualBox?

If not, you might simply try to extend the timeout in your Vagrantfile:

  config.vm.boot_timeout = 600

I have also gotten around this by reducing the amount of vCPUs to 1, but this is not a solution either as the software I need to test requires no less than 2 cores.

t-lo commented 3 years ago

Needs root causing (Flatcar console log etc.), tagging as good first issue until we now more.

pothos commented 2 years ago

Since using virtualbox it could be related to using the right image for vagrant so that Ignition works? https://github.com/flatcar-linux/Flatcar/issues/56