Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VM fails to boot #16

Open
daithiocrualaoich opened this issue May 14, 2017 · 2 comments
Open

VM fails to boot #16

daithiocrualaoich opened this issue May 14, 2017 · 2 comments
Labels

Comments

@daithiocrualaoich
Copy link
Member

VM fails to boot, stalls at network established. This typically happens when the RktMachine binary is changed. Currently needs a reboot to resolve.

[    3.812760] systemd-networkd[216]: eth0: Gained carrier
[    4.773086] systemd-networkd[216]: eth0: Gained IPv6LL
[    6.603250] systemd-networkd[216]: eth0: DHCPv4 address 192.168.64.19/24 via 192.168.64.1
[   17.453799] systemd-networkd[216]: eth0: Configured
@duraki
Copy link

duraki commented Apr 21, 2019

Similar happens here, on post-installation:

> booting rktmachine (1/1)
---> 'rktmachine' boot logs can be found at '/Users/user/.coreos/running/C16CF576-FB07-4DC9-8BF6-C022445B31A8/log'
[ERROR] Unable to grab VM's IP after 30s (!)... Aborted

Any update @daithiocrualaoich

@daithiocrualaoich
Copy link
Member Author

I’m currently travelling without my laptop for the rest of April and most of May so can’t look into this for you. The error message is common for a bunch of issues unfortunately as it is how the underlying VM management code exhibits failures.

I plan to give this repository some proper attention when I am back from travelling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants