/
README
338 lines (224 loc) · 11.5 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
Libguestfs is a library for accessing and modifying guest disk images.
Amongst the things this is good for: making batch configuration
changes to guests, getting disk used/free statistics (see also:
virt-df), migrating between virtualization systems (see also:
virt-p2v), performing partial backups, performing partial guest
clones, cloning guests and changing registry/UUID/hostname info, and
much else besides.
Libguestfs uses Linux kernel and qemu code, and can access any type of
guest filesystem that Linux and qemu can, including but not limited
to: ext2/3/4, btrfs, FAT and NTFS, LVM, many different disk partition
schemes, qcow, qcow2, vmdk.
Libguestfs provides ways to enumerate guest storage (eg. partitions,
LVs, what filesystem is in each LV, etc.). It can also run commands
in the context of the guest. Also you can access filesystems over
FUSE.
Libguestfs is a library that can be linked with C and C++ management
programs (or management programs written in OCaml, Perl, Python, Ruby,
Java, PHP, Haskell or C#). You can also use it from shell scripts or the
command line.
Libguestfs was written by Richard W.M. Jones (rjones@redhat.com) and
hacked on by lots of other people. For discussion, development,
patches, etc. please use the mailing list:
http://www.redhat.com/mailman/listinfo/libguestfs
Home page
----------------------------------------------------------------------
http://libguestfs.org/
Requirements
----------------------------------------------------------------------
- recent QEMU >= 0.12 with virtio-serial support
- febootstrap >= 2.10
- fakeroot
- fakechroot >= 2.9
- XDR, rpcgen (on Linux these are provided by glibc)
- pcre (Perl Compatible Regular Expressions C library) (optional)
- libmagic (the library that corresponds to the 'file' command) (optional)
- libvirt (optional)
- libxml2 (optional)
- Augeas (http://augeas.net/) (optional)
- gperf
- squashfs-tools (mksquashfs only)
- genisoimage / mkisofs
- hivex >= 1.2.1 (http://libguestfs.org/download)
- (Optional) FUSE to build the FUSE module
- perldoc (pod2man, pod2text) to generate the manual pages and
other documentation.
- (Optional) Readline to have nicer command-line editing in guestfish.
- (Optional) xmllint to validate virt-inspector RELAX NG schema
- (Optional) OCaml if you want to rebuild the generated files, and
also to build the OCaml bindings
- (Optional) local Fedora mirror
- (Optional) Perl if you want to build the perl bindings
- (Optional) Python if you want to build the python bindings
- (Optional) Ruby, rake if you want to build the ruby bindings
- (Optional) Java, JNI, jpackage-utils if you want to build the java
bindings
- (Optional) GHC if you want to build the Haskell bindings
- (Optional) Perl XML::XPath, Sys::Virt modules (for libvirt support
in virt-inspector).
- (Optional, but highly recommended) perl-libintl for translating perl code.
- (Optional) po4a for translating manpages and POD files.
- (Optional) PHP, phpize if you want to build the PHP bindings
Running ./configure will check you have all the requirements installed
on your machine.
Building
----------------------------------------------------------------------
Then make the daemon, library and root filesystem:
./configure [--with-mirror=URI]
make
Use the optional --with-mirror parameter to specify the URI of a local
Fedora mirror. See the discussion of the MIRROR parameter in the
febootstrap(8) manpage.
Finally run the tests:
make check
If everything works, you can install the library and tools by running
this command as root:
make install
Fedora
----------------------------------------------------------------------
We provide packages for Fedora >= 11 in Fedora. Use those, or build
from our source RPMs - it's far simpler that way.
You can compile libguestfs on Fedora 10 but you cannot use it with the
version of qemu in Fedora 10. You need to compile your own qemu, see
section 'qemu' below.
RHEL / EPEL / CentOS etc
----------------------------------------------------------------------
We provide packages in EPEL which cover RHEL/CentOS >= 5. Use those
or build from our source RPMs.
Debian
----------------------------------------------------------------------
libguestfs is now built as a package in Debian by Guido Gunther and
the other Debian libvirt maintainers. See:
http://wiki.debian.org/Teams/DebianLibvirtTeam#Packages
You can build for Debian in two different ways, either building a
Fedora-based appliance using febootstrap, yum, rpm, fakeroot,
fakechroot (all packaged in Debian). However the recommended way is
to build a Debian-based appliance using debootstrap and debirf.
Both ways are supported by the configure script.
qemu
----------------------------------------------------------------------
By far the most common problem is with broken or incompatible
qemu releases.
Different versions of qemu have problems booting the appliance for
different reasons. This varies between versions of qemu, and Linux
distributions which add their own patches.
If you find a problem, you could try using your own qemu built from
source (qemu is very easy to build from source), with a 'qemu
wrapper'. Qemu wrappers are described in the guestfs(3) manpage.
Note on using KVM
----------------------------------------------------------------------
By default the configure script will look for qemu-kvm (KVM support).
You will need a reasonably recent processor for this to work. KVM is
much faster than using plain Qemu.
You may also need to enable KVM support for non-root users, by following
these instructions:
http://www.linux-kvm.org/page/FAQ#How_can_I_use_kvm_with_a_non-privileged_user.3F
On some systems, this will work too:
chmod o+rw /dev/kvm
On some systems, the chmod will not survive a reboot, and you will
need to make edits to the udev configuration.
vmchannel
----------------------------------------------------------------------
Previous versions of libguestfs required something called "vmchannel".
Vmchannel is a special device given to virtual machines which allows
them to communicate in some way with the host, often (but not always)
without using a traditional network device. In reality, there is no
one thing called "vmchannel". This idea has been reimplemented
several times under the name vmchannel, and other hypervisors have
their own incompatible implementation(s) too.
In libguestfs <= 1.0.71, we required a specific vmchannel which is
properly known as "guestfwd" and has been upstream in qemu since here:
http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg01042.html
In libguestfs >= 1.0.71 we don't require any vmchannel implementation,
as long as qemu has been compiled with support for SLIRP (user mode
networking, or "-net user"), which is almost always the case.
In libguestfs >= 1.5.4 we switched again to using qemu's virtio-serial
and removed all the other vmchannels and the SLIRP channel.
Supermin appliance
----------------------------------------------------------------------
If you configure with --enable-supermin then we will build a supermin
appliance (supermin = super-minimized). This is a very specialized
appliance which is built on-the-fly at runtime (specifically, when you
call guestfs_launch).
The normal appliance is a self-contained Linux operating system, based
on the Fedora/RHEL/CentOS Linux distro. So it contains a complete
copy of all the libraries and programs needed, like kernel, libc,
bash, coreutils etc etc.
The supermin appliance removes the kernel and all the executable
libraries and programs from the appliance. That just leaves a
skeleton of config files and some data files, which is obviously
massively smaller than the normal appliance. At runtime we rebuild
the appliance on-the-fly from the libraries and programs on the host
(eg. pulling in the real /lib/libc.so, the real /bin/bash etc.)
Although this process of rebuilding the appliance each time sounds
slow, it turns out to be faster than using the prebuilt appliance.
(Most of the saving comes from not compressing the appliance - it
transpires that decompressing the appliance is the slowest part of the
whole boot sequence). On my machine, a new appliance can be built in
under a fifth of a second, and the boot time is several seconds
shorter.
The big advantage of the supermin appliance for distributions like
Fedora is that it gets security fixes automatically from the host, so
there is no need to rebuild the whole of libguestfs for a security
update in some underlying library.
There are several DISADVANTAGES:
It won't work at all except in very narrow, controlled cases like the
Fedora packaging case. We control the dependencies of the libguestfs
RPM tightly to ensure that the required binaries are actually present
on the host.
Furthermore there are certain unlikely changes in the packages on the
host which could break a supermin appliance, eg. an updated library
which depends on an additional data file.
Also supermin appliances are subjected to changes in the host kernel
which might break compatibility with qemu -- these are, of course,
real bugs in any case.
Lastly, supermin appliances really can't be moved between branches of
distributions (eg. built on Fedora 12 and moved to Fedora 10) because
they are not self-contained and they rely on certain libraries being
around. You shouldn't do this anyway.
Use supermin appliances with caution.
Notes on cross-architecture support
----------------------------------------------------------------------
At the moment we basically don't support cross-architecture or
32-on-64. This limits what is possible for some guests. Filesystem
operations and FUSE will work fine, but running commands in guests may
not be possible.
To enable this requires work for cross-architecture and 32-on-64
support in febootstrap, fakeroot and fakechroot.
The daemon/ directory contains its own configure script. This is so
that in future we will be able to cross-compile the daemon.
Mirroring tip
----------------------------------------------------------------------
On my machines I can usually rebuild the appliance in around 3
minutes. If it takes much longer for you, use a local Fedora mirror
or squid.
To use squid to cache yum downloads, read this first:
https://lists.dulug.duke.edu/pipermail/yum/2006-August/009041.html
(In brief, because yum chooses random mirrors each time, squid doesn't
work very well with default yum configuration. To get around this,
choose a Fedora mirror which is close to you, set this with
'./configure --with-mirror=[...]', and then proxy the whole lot
through squid by setting http_proxy environment variable).
You will also need to substantially increase the squid configuration
limits:
http://fedoraproject.org/wiki/Using_Mock_to_test_package_builds#Using_Squid_to_Speed_Up_Mock_package_downloads
Porting to other Linux distros / non-Linux
----------------------------------------------------------------------
libguestfs itself should be fairly portable to other Linux
distributions. Non-Linux ports are trickier, but we will accept
patches if they aren't too invasive.
The main porting issues are with the dependencies needed to build the
appliance. You will need to find or port the following packages
first:
- fakeroot
- fakechroot
- python
- rpm-python http://www.rpm.org/
- yum http://yum.baseurl.org/
- febootstrap http://people.redhat.com/~rjones/febootstrap/
Copyright and license information
----------------------------------------------------------------------
Copyright (C) 2009-2010 Red Hat Inc.
The library is distributed under the LGPLv2+. The programs are
distributed under the GPLv2+. Please see the files COPYING and
COPYING.LIB for full license information.