1virt-p2v-make-kickstart(1) Virtualization Support virt-p2v-make-kickstart(1)
2
6 virt-p2v-make-kickstart - Build the virt-p2v kickstart
7
9 virt-p2v-make-kickstart [-o p2v.ks] [--proxy=http://...] repo [repo...]
10
12 virt-p2v(1) converts a physical machine to run virtualized on KVM,
13 managed by libvirt, OpenStack, oVirt, Red Hat Enterprise Virtualisation
14 (RHEV), or one of the other targets supported by virt-v2v(1).
15 Kickstart is a format used by Red Hat-derived distributions (such as
17 Fedora, Red Hat Enterprise Linux, CentOS, Scientific Linux, and others)
18 to describe how to make live CDs, install the distro, make "Spins" and
19 so on. It is driven by a kickstart file.
20 virt-p2v-make-kickstart builds a kickstart file which can be used to
22 build a bootable P2V ISO, live CD, USB key, or PXE image. This tool
23 only builds the kickstart file, but this manual page describes some of
24 the ways you can use the kickstart file.
25 The root user on the disk image uses "p2v" as its initial password.
27
29 Using virt-p2v-make-kickstart is very simple:
30 virt-p2v-make-kickstart fedora
32 will build a kickstart file for Fedora. The kickstart file will be
34 called p2v.ks and located in the current directory.
35 The parameters are a list of one or more repositories. Some built-in
37 repositories are available: "fedora", "rawhide", "koji" or
38 "rhel-VERSION" (eg. "rhel-7.1"). You can also use a URL as a parameter
39 to point to a repository, for example:
40 virt-p2v-make-kickstart https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Everything/x86_64/os/
42 To control the name of the output file, use the -o parameter. To tell
44 kickstart to use a proxy server or web cache to download files, use the
45 --proxy parameter.
46
48 Once you have the kickstart file, you can use livecd-creator(8) to make
49 a live CD:
50 sudo livecd-creator p2v.ks
52 Before running this note that you should probably run "livecd-creator"
54 in a disposable virtual machine for these reasons:
55 · You have to disable SELinux when running the tool.
57 · This tool has to be run as root, and has some nasty failure modes.
59 · You can only create the exact same Live CD distro as the host
61 distro. Cross-builds will fail in strange ways (eg. RHBZ#1092327).
62
64 This requires "spin-livecd" permissions on Koji, which are not given
65 out usually, even to Fedora packagers. However assuming you have been
66 given these permissions (or have your own Koji instance, I guess), then
67 you can do:
68 koji spin-livecd [--scratch] virt-p2v 1.XX.YY rawhide x86_64 p2v.ks
70 · Add the "--scratch" option to do a scratch build (recommended for
72 testing).
73 · "1.XX.YY" should match the libguestfs version
75 · Instead of "rawhide" you can use any Koji target.
77
79 Use the livecd-iso-to-disk(8) program to convert the ISO created above
80 to a USB key:
81 sudo livecd-iso-to-disk livecd-p2v.iso /dev/sdX
83
85 Use the "livecd-iso-to-pxeboot" program to convert the ISO created
86 above to a PXE boot image.
87 sudo livecd-iso-to-pxeboot livecd-p2v.iso
89 This creates a "tftpboot" subdirectory under the current directory
91 containing the files required to PXE boot virt-p2v:
92 $ ls -1R tftpboot/
94 tftpboot/:
95 initrd0.img
96 pxelinux.0
97 pxelinux.cfg/
98 vmlinuz0
99 tftpboot/pxelinux.cfg:
101 default
102
104 Virt-p2v can convert any 32 or 64 bit guest, regardless of whether
105 virt-p2v itself is built as a 32 or 64 bit binary. The only
106 restriction is that 64 bit virt-p2v cannot run on 32 bit hardware.
107 Old virt-p2v 0.9 was always built as a 32 bit (i686) ISO. This meant
109 that the CD could be booted on any 32- or 64-bit i686 or x86-64
110 hardware, and could convert any guest. The old virt-p2v ISO shipped by
111 Red Hat was based on Red Hat Enterprise Linux (RHEL) 6.
112 Since RHEL 7 dropped support for 32 bit machines, current virt-p2v on
114 RHEL can only be built for 64 bit. It cannot run on old 32 bit only
115 hardware.
116 Fedora virt-p2v ISOs are generally built for 32 bit, so like the old
118 RHEL 6-based virt-p2v 0.9 they can boot on any hardware.
119
121 TESTING THE P2V ISO USING QEMU
122 You can use qemu to test-boot the P2V ISO:
123 qemu-kvm -m 1024 -hda /tmp/guest.img -cdrom /tmp/livecd-p2v.iso -boot d
125 Note that "-hda" is the (virtual) system that you want to convert (for
127 test purposes). It could be any guest type supported by virt-v2v(1),
128 including Windows or Red Hat Enterprise Linux.
129 TESTING PXE SUPPORT USING QEMU
131 · Unpack the tftpboot directory into /tmp (so it appears as
132 /tmp/tftpboot).
133 · Copy pxelinux.0 and ldlinux.c32 from syslinux (usually from
135 /usr/share/syslinux) into /tmp/tftpboot.
136 · Adjust the "APPEND" line in /tmp/tftpboot/pxelinux.cfg/default if
138 required. See "KERNEL COMMAND LINE CONFIGURATION" in virt-p2v(1).
139 · Run qemu like this so that it acts as a TFTP and BOOTP server,
141 emulating a netboot:
142 qemu-kvm \
144 -m 4096 -hda /tmp/guest.img \
145 -boot n \
146 -netdev user,id=unet,tftp=/tmp/tftpboot,bootfile=/pxelinux.0 \
147 -device virtio-net-pci,netdev=unet \
148 -serial stdio
149 Note that this requires considerably more memory because the PXE
151 image is loaded into memory. Also that qemu’s TFTP server is very
152 slow and the virt-p2v PXE image is very large, so it can appear to
153 "hang" after pxelinux starts up.
154
156 You can install extra packages using the --install option. This can be
157 useful for making a more fully-featured virt-p2v disk with extra tools
158 for debugging and troubleshooting. Give a list of packages, separated
159 by commas. For example:
160 virt-p2v-make-kickstart [...] --install tcpdump,traceroute
162
164 You can inject an SSH identity (private key) file to the kickstart and
165 hence into the ISO using the --inject-ssh-identity option. Note that
166 you cannot inject a key once the ISO has been built.
167 First create a key pair. It must have an empty passphrase:
169 ssh-keygen -t rsa -N '' -f id_rsa
171 This creates a private key ("id_rsa") and a public key ("id_rsa.pub")
173 pair. The public key should be appended to the "authorized_keys" file
174 on the virt-v2v conversion server (usually to
175 "/root/.ssh/authorized_keys").
176 The private key should be added to the kickstart file and then
178 discarded:
179 virt-p2v-make-kickstart [...] --inject-ssh-identity id_rsa
181 rm id_rsa
182 The ISO can then be built from the kickstart in the usual way (see
184 above), and it will contain the embedded SSH identity
185 (/var/tmp/id_rsa).
186 When booting virt-p2v, specify the URL of the injected file like this:
188 │ User name: [root_____________________________] │
190 │ │
191 │ Password: [ <leave this field blank> ] │
192 │ │
193 │ SSH Identity URL: [file:///var/tmp/id_rsa___________] │
194 or if using the kernel command line, add:
196 p2v.identity=file:///var/tmp/id_rsa
198 For more information, see "SSH IDENTITIES" in virt-p2v(1).
200
202 --help
203 Display help.
204 --inject-ssh-identity id_rsa
206 Add an SSH identity (private key) file into the kickstart. See
207 "ADDING AN SSH IDENTITY" above.
208 --install pkg,pkg,...
210 Add extra packages to the kickstart %packages section. See "ADDING
211 EXTRA PACKAGES" above.
212 -o OUTPUT
214 --output OUTPUT
215 Write kickstart to "OUTPUT". If not specified, the default is
216 p2v.ks in the current directory.
217 --proxy URL
219 Tell the kickstart to use a proxy server or web cache for
220 downloads.
221 -v
223 --verbose
224 Enable verbose output. Use this if you need to debug problems with
225 the script or if you are filing a bug.
226 -V
228 --version
229 Display version number and exit.
230
232 $libdir/virt-p2v/virt-p2v.xz
233 The virt-p2v(1) binary which is copied into the kickstart file.
234 The location of the binary can be changed by setting the
236 "VIRT_P2V_DATA_DIR" environment variable.
237 $datadir/virt-p2v/issue
239 $datadir/virt-p2v/launch-virt-p2v.in
240 $datadir/virt-p2v/p2v.ks.in
241 $datadir/virt-p2v/p2v.service
242 Various data files that are used to make the kickstart.
243 The location of these files can be changed by setting the
245 "VIRT_P2V_DATA_DIR" environment variable.
246
248 "VIRT_P2V_DATA_DIR"
249 The directory where virt-p2v-make-kickstart looks for data files
250 and the virt-p2v binary (see "FILES" above). If not set, a
251 compiled-in location is used.
252
254 virt-p2v(1), virt-p2v-make-disk(1), virt-v2v(1), livecd-creator(8),
255 livecd-iso-to-disk(8), http://libguestfs.org/.
256
258 Richard W.M. Jones http://people.redhat.com/~rjones/
259
261 Copyright (C) 2009-2019 Red Hat Inc.
262
264 This program is free software; you can redistribute it and/or modify it
265 under the terms of the GNU General Public License as published by the
266 Free Software Foundation; either version 2 of the License, or (at your
267 option) any later version.
268 This program is distributed in the hope that it will be useful, but
270 WITHOUT ANY WARRANTY; without even the implied warranty of
271 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
272 General Public License for more details.
273 You should have received a copy of the GNU General Public License along
275 with this program. If not, see <https://www.gnu.org/licenses/>.
276
278 To get a list of bugs against libguestfs (which include virt-p2v), use
279 this link:
280 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
281 To report a new bug against libguestfs, use this link:
283 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
284 When reporting a bug, please supply:
286 · The version of virt-p2v.
288 · Where you got virt-p2v (eg. which Linux distro, compiled from
290 source, etc)
291 · Describe the bug accurately and give a way to reproduce it.
293virt-p2v-1.42.0 2020-01-31 virt-p2v-make-kickstart(1)