almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity

livemedia-creator: Update documentation to reflect new options

Browse Source
This commit is contained in:
Brian C. Lane 2014-04-03 10:05:37 -07:00
parent 19d8304070
commit 71dd20607b
2 changed files with 36 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.livemedia-creator
View File

@ -185,7 +185,7 @@ sudo livemedia-creator --make-ami --iso=/path/to/boot.iso --ks=./docs/fedora-liv
This will produce an ami-root.img file in the working directory.
At this time I have not tested the image with EC2. Feedback would we welcome.
At this time I have not tested the image with EC2. Feedback would be welcome.
APPLIANCE CREATION
@ -224,6 +224,23 @@ The created image can be imported into libvirt using:
virt-image appliance.xml
You can also create qcow2 appliance images using --qcow2, for example:
sudo livemedia-creator --make-appliance --iso=/path/to/boot.iso --ks=./docs/fedora-minimal.ks \
--qcow2 --app-file=minimal-test.xml --image-name=minimal-test.img
FILESYSTEM IMAGE CREATION
-------------------------
livemedia-creator can be used to create un-partitined filesystem images using the
--make-fsimage option. As of version 21.8 this works with both virt-install and no-virt. Previously
it was only available with --no-virt.
Kickstarts should have a single / partition with no extra mountpoints.
livemedia-creator --make-fsimage --iso=/path/to/boot.iso --ks=./docs/fedora-minimal.ks
You can name the output image with --image-name and set a label on the filesystem with --fs-label
DEBUGGING PROBLEMS
------------------

22
docs/livemedia-creator.1
View File

@ -1,4 +1,4 @@
.TH LIVEMEDIA-CREATOR 1 2013\-07\-26
.TH LIVEMEDIA-CREATOR 1 2014\-04\-03
.SH NAME
livemedia-creator \- Create live install media
@ -8,6 +8,8 @@ livemedia-creator [-h]
[--iso ISO] [--disk-image DISK_IMAGE]
[--fs-image FS_IMAGE] [--ks KS]
[--image-name IMAGE_NAME] [--image-only]
[--fs-label FS_LABEL]
[--qcow2] [--qcow2-arg QCOW2_ARGS]
[--keep-image] [--no-virt] [--proxy PROXY]
[--anaconda-arg ANACONDA_ARGS]
[--armplatform ARMPLATFORM] [--location LOCATION]
@ -30,8 +32,8 @@ use with virtualization.
The general idea is to use virt-install to install into a disk image and then
use the disk image to create the bootable media.
livemedia-creator --help will describe all of the options available. At the
minimum you need:
livemedia-creator --help will describe all of the options available. To create a
bootable iso you need at least:
--make-iso to create a final bootable .iso
--iso to specify the Anaconda install media to use with virt-install
@ -73,7 +75,15 @@ Path to disk image to use for creating final image
.TP
\fB\-\-fs\-image FS_IMAGE\fR
Path to filesystem image to use for creating final image
Path to existing filesystem image to use for creating final image.
.TP
\fB\-\-qcow2\fR
Create qcow2 image instead of raw sparse image when making disk images.
.TP
\fB\-\-qcow2\-args\fR
Arguments to pass to qemu-img. Pass once for each argument
.TP
\fB\-\-ks KS\fR
@ -83,6 +93,10 @@ Kickstart file defining the install.
\fB\-\-image\-name IMAGE_NAME\fR
Name of fs/disk image to create. Default is a random name.
.TP
\fB\-\-fs\-label FS_LABEL\fR
Label to set on fsimage, default is 'Anaconda'
.TP
\fB\-\-image\-only\fR
Exit after creating fs/disk image.