From a19d8ceee7aafe785eb3174cd1197d9fc3504e61 Mon Sep 17 00:00:00 2001 From: Chris Jones Date: Mon, 18 Nov 2013 19:45:59 +0000 Subject: [PATCH] Document ramdisk troubleshooting. We now document how to trigger a troubleshooting shell when booting a di-b ramdisk. Change-Id: Ief44347893fa81a7f2669143e1746a5ee99599af --- README.md | 5 +++++ elements/ramdisk/README.md | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index df0f831b..8a092327 100644 --- a/README.md +++ b/README.md @@ -381,6 +381,11 @@ console so nova's console-log command can function. There is an element in the tripleo-image-elements repository called "remove-serial-console" which will force all boot messages to appear on the main console. +Ramdisk images can be debugged at run-time by passing "troubleshoot" as a +kernel command line argument, or by pressing "t" when an error is reached. This +will spawn a shell on the console (this can be extremely useful when network +interfaces or disks are not detected correctly). + Testing Elements ---------------- diff --git a/elements/ramdisk/README.md b/elements/ramdisk/README.md index 69c8b5b3..3cf6d58a 100644 --- a/elements/ramdisk/README.md +++ b/elements/ramdisk/README.md @@ -10,5 +10,5 @@ and scripts need to be injected into a ramdisk that will fetch and apply a machine image to local disks. That tooling/scripting customisation can be easily applied in a repeatable and automatable way, using this element. -See the top-level README.me of the project, for more information about the +See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.