mirrors/libguestfs
1
0
Fork 0
mirror of https://github.com/libguestfs/libguestfs.git synced 2026-03-22 07:03:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve diagrams on various manual pages using Unicode box drawing characters.

Browse Source
This commit is contained in:
Richard W.M. Jones
2014-09-01 21:29:13 +01:00
parent 3c1b81d2af
commit c435053b34
5 changed files with 57 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
align/virt-alignment-scan.pod
View File

@@ -250,13 +250,13 @@ Partitions which are not aligned correctly to the underlying
storage cause extra I/O. For example:
sect#63
+--------------------------+------
| guest |
| filesystem block |
---+------------------+------+-------------------+-----+---
| host block | host block |
| | |
---+-------------------------+-------------------------+---
┌──────────────────────────┬ ─ ─ ─ ─
│ guest │
│ filesystem block │
─ ┬──────────────────┴──────┬───────────────────┴─────┬ ─ ─
│ host block │ host block │
│ │ │
─ ┴─────────────────────────┴─────────────────────────┴ ─ ─
In this example, each time a 4K guest block is read, two blocks on the
host must be accessed (so twice as much I/O is done). When a 4K guest

44
examples/guestfs-faq.pod
View File

@@ -509,21 +509,19 @@ In Fedora E<ge> 18 and RHEL E<ge> 7, libguestfs uses libvirt to manage
the appliance. Previously (and upstream) libguestfs runs qemu
directly:
+----------------------------------+
| libguestfs |
+----------------+-----------------+
| direct backend | libvirt backend |
+----------------+-----------------+
| |
v v
+-------+ +----------+
| qemu | | libvirtd |
+-------+ +----------+
|
v
+-------+
| qemu |
+-------+
┌──────────────────────────────────┐
│ libguestfs │
├────────────────┬─────────────────┤
│ direct backend │ libvirt backend │
└────────────────┴─────────────────┘
↓ ↓
┌───────┐ ┌──────────┐
│ qemu │ │ libvirtd │
└───────┘ └──────────┘
↓
┌───────┐
│ qemu │
└───────┘
upstream Fedora 18+
non-Fedora RHEL 7+
@@ -1144,14 +1142,14 @@ In contrast, when the virtual machine boots, it mounts those
filesystems into a consistent hierarchy such as:
/ (/dev/sda2)
|
+-- /boot (/dev/sda1)
|
+-- /home (/dev/vg_external/Homes)
|
+-- /usr (/dev/vg_os/lv_usr)
|
+-- /var (/dev/vg_os/lv_var)
│
├── /boot (/dev/sda1)
│
├── /home (/dev/vg_external/Homes)
│
├── /usr (/dev/vg_os/lv_usr)
│
└── /var (/dev/vg_os/lv_var)
(or drive letters on Windows).

10
p2v/virt-p2v.pod
View File

@@ -27,11 +27,11 @@ has to talk to another server called the "conversion server" which
must have L<virt-v2v(1)> installed on it. It always talks to the
conversion server over SSH:
+-----------+ +-------------+
| virt-p2v | | virt-v2v |
| (physical | ssh connection | (conversion |
| server) -----------------> server) |
+-----------+ +-------------+
┌──────────────┐ ┌─────────────────┐
│ virt-p2v │ │ virt-v2v │
│ (physical │ ssh connection │ (conversion │
│ server) ╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍▶ server) │
└──────────────┘ └─────────────────┘
The virt-v2v program on the conversion server does the actual
conversion (physical to virtual, and virtual to virtual conversions

37
src/guestfs.pod
View File

@@ -3392,25 +3392,24 @@ Internally, libguestfs is implemented by running an appliance (a
special type of small virtual machine) using L<qemu(1)>. Qemu runs as
a child process of the main program.
___________________
/ \
| main program |
| |
| | child process / appliance
| | __________________________
| | / qemu \
+-------------------+ RPC | +-----------------+ |
| libguestfs <--------------------> guestfsd | |
| | | +-----------------+ |
\___________________/ | | Linux kernel | |
| +--^--------------+ |
\_________|________________/
|
_______v______
/ \
| Device or |
| disk image |
\______________/
┌───────────────────┐
│ main program │
│ │
│ │ child process / appliance
│ │ ┌──────────────────────────┐
│ │ │ qemu │
├───────────────────┤ RPC │ ┌─────────────────┐ │
│ libguestfs ◀╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍▶ guestfsd │ │
│ │ │ ├─────────────────┤ │
└───────────────────┘ │ │ Linux kernel │ │
│ └────────┬────────┘ │
└───────────────│──────────┘
│
│ virtio-scsi
┌──────┴──────┐
│ Device or │
│ disk image │
└─────────────┘
The library, linked to the main program, creates the child process and
hence the appliance in the L</guestfs_launch> function.

12
v2v/virt-v2v.pod
View File

@@ -31,13 +31,13 @@ libguestfs E<ge> 1.28.
=head1 INPUT AND OUTPUT MODES
┌────────────┐
-i disk ───────────┐ │ │ ┌───────> -o local
-i disk ───────────┐ │ │ ┌───────▶ -o local
│ │ virt-v2v │ │
└──> │ conversion │ ──┘
-i libvirt ───────────> │ server │ ────────> -o libvirt
(default) ┌──> │ │ ──┐ (default)
│ │ │ ─┐└──────> -o glance
-i libvirtxml ─────┘ │ │ └─────────> -o rhev
└──▶ │ conversion │ ──┘
-i libvirt ───────────▶ │ server │ ────────▶ -o libvirt
(default) ┌──▶ │ │ ──┐ (default)
│ │ │ ─┐└──────▶ -o glance
-i libvirtxml ─────┘ │ │ └─────────▶ -o rhev
└────────────┘
Virt-v2v has a number of possible input and output modes, selected