From 5aafe008bc7e8766482bfd76516a1bb3eb3b3237 Mon Sep 17 00:00:00 2001 From: Cole Robinson Date: Sat, 6 Sep 2014 18:05:43 -0400 Subject: [PATCH] Remove virt-image, as scheduled As promised with the last release, remove virt-image. In 6 months I didn't hear a peep from any actual users that cared. --- .gitignore | 2 - man/virt-image-xml.pod | 240 ---------- man/virt-image.pod | 190 -------- setup.py | 21 +- tests/__init__.py | 1 - .../compare/virt-image-image-boot0.xml | 42 -- .../compare/virt-image-image-boot1.xml | 44 -- .../compare/virt-image-image-nogfx.xml | 38 -- tests/cli-test-xml/image-nogfx.xml | 37 -- tests/cli-test-xml/image.xml | 38 -- tests/clitest.py | 61 +-- tests/image-xml/image-bad-arch.xml | 35 -- tests/image-xml/image-format.xml | 27 -- tests/image-xml/image-kernel.xml | 37 -- tests/image-xml/image.xml | 48 -- .../image2guest/image-format-out.xml | 40 -- tests/image-xml/image2guest/image-xenfv32.xml | 38 -- .../image2guest/image-xenpv32-kernel.xml | 35 -- tests/image-xml/image2guest/image-xenpv32.xml | 30 -- tests/image-xml/image2nics.xml | 49 -- tests/image.py | 110 ----- tests/misc.py | 2 +- virt-image | 172 ------- virt-manager.spec.in | 5 - virtinst/cli.py | 4 +- virtinst/virtimage.py | 429 ------------------ 26 files changed, 13 insertions(+), 1762 deletions(-) delete mode 100644 man/virt-image-xml.pod delete mode 100644 man/virt-image.pod delete mode 100644 tests/cli-test-xml/compare/virt-image-image-boot0.xml delete mode 100644 tests/cli-test-xml/compare/virt-image-image-boot1.xml delete mode 100644 tests/cli-test-xml/compare/virt-image-image-nogfx.xml delete mode 100644 tests/cli-test-xml/image-nogfx.xml delete mode 100644 tests/cli-test-xml/image.xml delete mode 100644 tests/image-xml/image-bad-arch.xml delete mode 100644 tests/image-xml/image-format.xml delete mode 100644 tests/image-xml/image-kernel.xml delete mode 100644 tests/image-xml/image.xml delete mode 100644 tests/image-xml/image2guest/image-format-out.xml delete mode 100644 tests/image-xml/image2guest/image-xenfv32.xml delete mode 100644 tests/image-xml/image2guest/image-xenpv32-kernel.xml delete mode 100644 tests/image-xml/image2guest/image-xenpv32.xml delete mode 100644 tests/image-xml/image2nics.xml delete mode 100644 tests/image.py delete mode 100755 virt-image delete mode 100644 virtinst/virtimage.py diff --git a/.gitignore b/.gitignore index 3ee600eb..dd2404e0 100644 --- a/.gitignore +++ b/.gitignore @@ -14,9 +14,7 @@ po/virt-manager.pot /man/virt-manager.1 /man/virt-install.1 /man/virt-clone.1 -/man/virt-image.1 /man/virt-convert.1 -/man/virt-image.5 /man/virt-xml.1 /virt-manager.spec diff --git a/man/virt-image-xml.pod b/man/virt-image-xml.pod deleted file mode 100644 index b8e30969..00000000 --- a/man/virt-image-xml.pod +++ /dev/null @@ -1,240 +0,0 @@ -=pod - -=head1 NAME - -virt-image - Format of the virtual image XML descriptor - -=head1 DESCRIPTION - -L relies on an XML descriptor to create virtual machines from -virtual machine images. In general, a virtual machine image consists of the -XML descriptor (usually in a file F) and a number of files for -the virtual machine's disks. - -In the following explanation of the structure of the image descriptor, -mandatory XML elements are marked as B, whereas optional elements -are marked as I. - -All file names in the image descriptor are relative to the location of the -descriptor itself. Generally, disk files are either kept in the same -directory as the image descriptor, or in a subdirectory. - -=head1 HOST MATCHING - -The image descriptor contains information on the requirements a guest has -on the host platform through one or more the F -descriptors (see section L). The image can only be used if at least -one of the boot descriptors is suitable for the host platform; a boot -descriptor is suitable if: - -=over 4 - -=item * - -The CPU architecture of the boot descriptor, given by the -F element, is supported by the host - -=item * - -The host supports a guest with the features requested in the -F element, such as providing an APIC, or having ACPI -turned off - -=back - -If a suitable boot descriptor is found, the guest is created and booted -according to the information about booting the OS from the F -element and with the disks specified in the F element. If more -than one suitable boot descriptor is found, one of them is chosen based on -a heuristic, generally preferring paravirtualized guests over full -virtualized ones, though this is an implementation detail of the tool -creating the virtual machine. - -=head1 STRUCTURE - -The image descriptor consists of three sections, all contained in the -toplevel B element: - -=over 4 - -=item General metadata about the image - -A number of elements like I