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
27 Using virt-p2v-make-kickstart is very simple:
28 virt-p2v-make-kickstart fedora
30 will build a kickstart file for Fedora. The kickstart file will be
32 called p2v.ks and located in the current directory.
33 The parameters are a list of one or more repositories. Some built-in
35 repositories are available: "fedora", "rawhide", "koji" or
36 "rhel-VERSION" (eg. "rhel-7.1"). You can also use a URL as a parameter
37 to point to a repository, for example:
38 virt-p2v-make-kickstart https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Everything/x86_64/os/
40 To control the name of the output file, use the -o parameter. To tell
42 kickstart to use a proxy server or web cache to download files, use the
43 --proxy parameter.
44
46 Once you have the kickstart file, you can use livecd-creator(8) to make
47 a live CD:
48 sudo livecd-creator p2v.ks
50 Before running this note that you should probably run "livecd-creator"
52 in a disposable virtual machine for these reasons:
53 · You have to disable SELinux when running the tool.
55 · This tool has to be run as root, and has some nasty failure modes.
57 · You can only create the exact same Live CD distro as the host
59 distro. Cross-builds will fail in strange ways (eg. RHBZ#1092327).
60
62 This requires "spin-livecd" permissions on Koji, which are not given
63 out usually, even to Fedora packagers. However assuming you have been
64 given these permissions (or have your own Koji instance, I guess), then
65 you can do:
66 koji spin-livecd [--scratch] virt-p2v 1.XX.YY rawhide x86_64 p2v.ks
68 · Add the "--scratch" option to do a scratch build (recommended for
70 testing).
71 · "1.XX.YY" should match the libguestfs version
73 · Instead of "rawhide" you can use any Koji target.
75
77 Use the livecd-iso-to-disk(8) program to convert the ISO created above
78 to a USB key:
79 sudo livecd-iso-to-disk livecd-p2v.iso /dev/sdX
81
83 Use the "livecd-iso-to-pxeboot" program to convert the ISO created
84 above to a PXE boot image.
85 sudo livecd-iso-to-pxeboot livecd-p2v.iso
87 This creates a "tftpboot" subdirectory under the current directory
89 containing the files required to PXE boot virt-p2v:
90 $ ls -1R tftpboot/
92 tftpboot/:
93 initrd0.img
94 pxelinux.0
95 pxelinux.cfg/
96 vmlinuz0
97 tftpboot/pxelinux.cfg:
99 default
100
102 Virt-p2v can convert any 32 or 64 bit guest, regardless of whether
103 virt-p2v itself is built as a 32 or 64 bit binary. The only
104 restriction is that 64 bit virt-p2v cannot run on 32 bit hardware.
105 Old virt-p2v 0.9 was always built as a 32 bit (i686) ISO. This meant
107 that the CD could be booted on any 32- or 64-bit i686 or x86-64
108 hardware, and could convert any guest. The old virt-p2v ISO shipped by
109 Red Hat was based on Red Hat Enterprise Linux (RHEL) 6.
110 Since RHEL 7 dropped support for 32 bit machines, current virt-p2v on
112 RHEL can only be built for 64 bit. It cannot run on old 32 bit only
113 hardware.
114 Fedora virt-p2v ISOs are generally built for 32 bit, so like the old
116 RHEL 6-based virt-p2v 0.9 they can boot on any hardware.
117
119 TESTING THE P2V ISO USING QEMU
120 You can use qemu to test-boot the P2V ISO:
121 qemu-kvm -m 1024 -hda /tmp/guest.img -cdrom /tmp/livecd-p2v.iso -boot d
123 Note that "-hda" is the (virtual) system that you want to convert (for
125 test purposes). It could be any guest type supported by virt-v2v(1),
126 including Windows or Red Hat Enterprise Linux.
127 TESTING PXE SUPPORT USING QEMU
129 · Unpack the tftpboot directory into /tmp (so it appears as
130 /tmp/tftpboot).
131 · Copy pxelinux.0 and ldlinux.c32 from syslinux (usually from
133 /usr/share/syslinux) into /tmp/tftpboot.
134 · Adjust the "APPEND" line in /tmp/tftpboot/pxelinux.cfg/default if
136 required. See "KERNEL COMMAND LINE CONFIGURATION" in virt-p2v(1).
137 · Run qemu like this so that it acts as a TFTP and BOOTP server,
139 emulating a netboot:
140 qemu-kvm \
142 -m 4096 -hda /tmp/guest.img \
143 -boot n \
144 -netdev user,id=unet,tftp=/tmp/tftpboot,bootfile=/pxelinux.0 \
145 -device virtio-net-pci,netdev=unet \
146 -serial stdio
147 Note that this requires considerably more memory because the PXE
149 image is loaded into memory. Also that qemu’s TFTP server is very
150 slow and the virt-p2v PXE image is very large, so it can appear to
151 "hang" after pxelinux starts up.
152
154 You can install extra packages using the --install option. This can be
155 useful for making a more fully-featured virt-p2v disk with extra tools
156 for debugging and troubleshooting. Give a list of packages, separated
157 by commas. For example:
158 virt-p2v-make-kickstart [...] --install tcpdump,traceroute
160
162 You can inject an SSH identity (private key) file to the kickstart and
163 hence into the ISO using the --inject-ssh-identity option. Note that
164 you cannot inject a key once the ISO has been built.
165 First create a key pair. It must have an empty passphrase:
167 ssh-keygen -t rsa -N '' -f id_rsa
169 This creates a private key ("id_rsa") and a public key ("id_rsa.pub")
171 pair. The public key should be appended to the "authorized_keys" file
172 on the virt-v2v conversion server (usually to
173 "/root/.ssh/authorized_keys").
174 The private key should be added to the kickstart file and then
176 discarded:
177 virt-p2v-make-kickstart [...] --inject-ssh-identity id_rsa
179 rm id_rsa
180 The ISO can then be built from the kickstart in the usual way (see
182 above), and it will contain the embedded SSH identity
183 (/var/tmp/id_rsa).
184 When booting virt-p2v, specify the URL of the injected file like this:
186 │ User name: [root_____________________________] │
188 │ │
189 │ Password: [ <leave this field blank> ] │
190 │ │
191 │ SSH Identity URL: [file:///var/tmp/id_rsa___________] │
192 or if using the kernel command line, add:
194 p2v.identity=file:///var/tmp/id_rsa
196 For more information, see "SSH IDENTITIES" in virt-p2v(1).
198
200 --help
201 Display help.
202 --inject-ssh-identity id_rsa
204 Add an SSH identity (private key) file into the kickstart. See
205 "ADDING AN SSH IDENTITY" above.
206 --install pkg,pkg,...
208 Add extra packages to the kickstart %packages section. See "ADDING
209 EXTRA PACKAGES" above.
210 -o OUTPUT
212 --output OUTPUT
213 Write kickstart to "OUTPUT". If not specified, the default is
214 p2v.ks in the current directory.
215 --proxy URL
217 Tell the kickstart to use a proxy server or web cache for
218 downloads.
219 -v
221 --verbose
222 Enable verbose output. Use this if you need to debug problems with
223 the script or if you are filing a bug.
224 -V
226 --version
227 Display version number and exit.
228
230 $libdir/virt-p2v/virt-p2v.xz
231 The virt-p2v(1) binary which is copied into the kickstart file.
232 The location of the binary can be changed by setting the
234 "VIRT_P2V_DATA_DIR" environment variable.
235 $datadir/virt-p2v/issue
237 $datadir/virt-p2v/launch-virt-p2v.in
238 $datadir/virt-p2v/p2v.ks.in
239 $datadir/virt-p2v/p2v.service
240 Various data files that are used to make the kickstart.
241 The location of these files can be changed by setting the
243 "VIRT_P2V_DATA_DIR" environment variable.
244
246 "VIRT_P2V_DATA_DIR"
247 The directory where virt-p2v-make-kickstart looks for data files
248 and the virt-p2v binary (see "FILES" above). If not set, a
249 compiled-in location is used.
250
252 virt-p2v(1), virt-p2v-make-disk(1), virt-v2v(1), livecd-creator(8),
253 livecd-iso-to-disk(8), http://libguestfs.org/.
254
256 Richard W.M. Jones http://people.redhat.com/~rjones/
257
259 Copyright (C) 2009-2019 Red Hat Inc.
260
262 This program is free software; you can redistribute it and/or modify it
263 under the terms of the GNU General Public License as published by the
264 Free Software Foundation; either version 2 of the License, or (at your
265 option) any later version.
266 This program is distributed in the hope that it will be useful, but
268 WITHOUT ANY WARRANTY; without even the implied warranty of
269 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
270 General Public License for more details.
271 You should have received a copy of the GNU General Public License along
273 with this program; if not, write to the Free Software Foundation, Inc.,
274 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
275
277 To get a list of bugs against libguestfs, use this link:
278 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
279 To report a new bug against libguestfs, use this link:
281 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
282 When reporting a bug, please supply:
284 · The version of libguestfs.
286 · Where you got libguestfs (eg. which Linux distro, compiled from
288 source, etc)
289 · Describe the bug accurately and give a way to reproduce it.
291 · Run libguestfs-test-tool(1) and paste the complete, unedited output
293 into the bug report.
294libguestfs-1.40.1 2019-01-17 virt-p2v-make-kickstart(1)