openstack/diskimage-builder
Code Issues Proposed changes

Document ramdisk troubleshooting.

Browse Source 
We now document how to trigger a troubleshooting shell when booting a
di-b ramdisk.

Change-Id: Ief44347893fa81a7f2669143e1746a5ee99599af
This commit is contained in:
Chris Jones 2013-11-18 19:45:59 +00:00
parent 45a0082fa7
commit a19d8ceee7
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -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 tripleo-image-elements repository called "remove-serial-console" which will
force all boot messages to appear on the main console. 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 Testing Elements
---------------- ----------------

2
elements/ramdisk/README.md
View File

@ -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 machine image to local disks. That tooling/scripting customisation can be
easily applied in a repeatable and automatable way, using this element. 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. mechanisms available to a ramdisk element.