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

1192.0.0 does not boot on AWS in paravirtual mode #1600

Closed
monder opened this Issue Oct 8, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@monder

monder commented Oct 8, 2016

Issue Report

Bug

1192.0.0 fails to start on AWS

CoreOS Version

CoreOS-alpha-1192.0.0 (ami-f7b6f684)

Environment

PV m1.xlarge

Expected Behavior

Instance boots.

Actual Behavior

Instance does not boot and throws emergency shell

[K[�[0;1;31m TIME �[0m] Timed out waiting for device dev-mapper-usr.device.
[   92.212015] [systemd[1]: dev-mapper-usr.device: Job dev-mapper-usr.device/start timed out.�[0;1;33mDEPEND�[0m
] Dependency failed for /sysroot/usr.

Full log: https://gist.github.com/monder/c501245755f7c3271e3b03489ba495bb

@monder

This comment has been minimized.

monder commented Oct 8, 2016

HVM (ami-82b5f5f1) works just fine.

@monder monder changed the title from 1192.0.0 does not boot on AWS to 1192.0.0 does not boot on AWS in paravirtual mode Oct 8, 2016

@marineam

This comment has been minimized.

marineam commented Oct 10, 2016

By mistake we never added a piece of code to the Xen loader in GRUB that amends the kernel cmdline with the correct verity hash. And due to an oversight in our testing the Xen PV images weren't being tested.

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