Skip to content
This repository has been archived by the owner. It is now read-only.

1192.0.0 does not boot on AWS in paravirtual mode #1600

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

1192.0.0 does not boot on AWS in paravirtual mode #1600

monder opened this issue Oct 8, 2016 · 2 comments

Comments

@monder
Copy link

@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
Copy link
Author

@monder monder commented Oct 8, 2016

HVM (ami-82b5f5f1) works just fine.

@monder monder changed the title 1192.0.0 does not boot on AWS 1192.0.0 does not boot on AWS in paravirtual mode Oct 8, 2016
@marineam
Copy link

@marineam 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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.