keremet/mkimage-profiles
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
b150f9097b
mkimage-profiles/features.in/build-vm/lib/90-build-vm.mk

105 lines
2.7 KiB
Makefile
Raw Normal View History

initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
# step 4: build the virtual machine image
build-{ve,vm}: handle THE_* and DOT_BASE too Classic VEs don't carry any kernel since these are running under a single OpenVZ (or potentially LXC) kernel image; ARM Multiboot (TWRP in this particular case) allows to boot off a chroot via kexec, and we need a kernel in it for that, obviously. No bootloader required inside such VE though.
2013-05-17 14:41:32 +04:00
IMAGE_PACKAGES = $(DOT_BASE) \
$(SYSTEM_PACKAGES) \
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
$(COMMON_PACKAGES) \
$(BASE_PACKAGES) \
$(THE_PACKAGES) \
build-{ve,vm}: handle THE_* and DOT_BASE too Classic VEs don't carry any kernel since these are running under a single OpenVZ (or potentially LXC) kernel image; ARM Multiboot (TWRP in this particular case) allows to boot off a chroot via kexec, and we need a kernel in it for that, obviously. No bootloader required inside such VE though.
2013-05-17 14:41:32 +04:00
$(call list,$(BASE_LISTS) $(THE_LISTS))
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
build-ve, build-vm: handle *_PACKAGES_REGEXP BASE_PACKAGES_REGEXP and THE_PACKAGES_REGEXP, to be exact; the lack of handling these appears to have been the culprit of firefox missing in vm images which use/browser/firefox.
2017-08-21 21:39:52 +03:00
IMAGE_PACKAGES_REGEXP = $(THE_PACKAGES_REGEXP) \
build-vm: whitespace fixup ...so that it doesn't show up in a diff with build-vm.
2018-02-14 18:33:46 +03:00
$(BASE_PACKAGES_REGEXP)
build-ve, build-vm: handle *_PACKAGES_REGEXP BASE_PACKAGES_REGEXP and THE_PACKAGES_REGEXP, to be exact; the lack of handling these appears to have been the culprit of firefox missing in vm images which use/browser/firefox.
2017-08-21 21:39:52 +03:00
build-vm, kernel, tar2fs: make-initrd happens now in build-vm NB: 07-kernel change breaks multi-kernel setup! Breaks: 650e92bf7fe7bcec939d4512b275ad843268bba4
2019-05-07 19:17:55 +03:00
ifdef EFI_BOOTLOADER
VM_BOOTLOADER=$(EFI_BOOTLOADER)
else
VM_BOOTLOADER=$(BASE_BOOTLOADER)
endif
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
# intermediate chroot archive
VM_TARBALL := $(IMAGE_OUTDIR)/$(IMAGE_NAME).tar
initial specific VM formats support Raw disk images are convenient and universal but there are custom formats like Qemu's qcow2 providing additional features, e.g. copy-on-write or space savings. All of this ultimately belongs to mkimage but in the mean time has been implemented here as well.
2012-06-19 17:51:56 +04:00
VM_RAWDISK := $(IMAGE_OUTDIR)/$(IMAGE_NAME).raw
tar2vm: rewrote as tar2fs Overview of the changes: - ARM support: separate ext2 /boot, no LILO - avoid race condition with devmapper - trap ERR so that -e in shebang doesn't result in extra cleanup hassle - configurable root filesystem type (ext4 by default) - jumps through parted hoops Details: 1. LILO is x86-specific while the rest of the script can be used to prepare e.g. Marvell ArmadaXP or CuBox images; we can generally count on uboot supporting ext2 for relatively sane platforms but not ext4 that would be a better root filesystem performance-wise. 2. Apparently /dev/mapper/loopXpY can be still missing at the time when kpartx returns and pop up a bit later... sit there, wait and check for it. 3. If something went wrong with any command of the script it would bail out due to -e in shebang; it is now better to clean up the loopback device and its mappings in this situation either. 4. One size doesn't fit all, really. 5. The parted sizing was sloppy as in broken, now it's just half insane. Someone's decision to stick units and auto-alignment knobs into a single one was apparently hilarious... http://www.gnu.org/software/parted/manual/parted.html#unit Manual loop/dm cleanup is described in documentation just in case. /boot size meter is suboptimal in terms of additional I/O incurred, will be most likely rewritten to make use of advance "du -s".
2013-05-29 17:56:12 +04:00
VM_FSTYPE ?= ext4
VM_SIZE ?= 0
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
VM_GZIP_COMMAND ?= gzip
VM_XZ_COMMAND ?= xz -T0
build-vm, main.mk, pack: add recovery.tar recovery.tar needed for tavolga (mipsel). This commit is the result of transferring the required functionality from build-mr (mipsel rootfs). This change uses external tool to build Tavolga-compatible recovery.tar. This simplifies the logic and avoids having recovery workdir in the profile. After this change, m-p will require tavolga-image-tools >= 3.0.
2019-05-19 12:39:04 +03:00
# tavolga
RECOVERY_LINE ?= Press ENTER to start
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
check-sudo:
@if ! type -t sudo >&/dev/null; then \
echo "** error: sudo not available, see doc/vm.txt" >&2; \
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
fi
check-qemu:
@if ! type -t qemu-img >&/dev/null; then \
echo "** error: qemu-img not available" >&2; \
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
exit 1; \
fi
build-vm: Don't copy in .host/qemu* if tar2fs won't be called (gkebfm@ thinks it was a terrible idea in the first place and mike@ agrees; this is a rework TODO item)
2019-06-19 16:45:15 +03:00
tar2fs: check-sudo prepare-tarball-qemu
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
@if [ -x /usr/share/mkimage-profiles/bin/tar2fs ]; then \
Use correct path for system tar2fs tar2fs comes from m-p, not from mkimage. Also, we should use $TOPDIR from shell, not $(TOPDIR) from make, when calling it. Note: this is a security fix for environments relying on packaged mkimage-profiles with sudo enabled for the builder user. Fixes: f293239d5bd7d2a1e50e155f09effb56b262071e
2018-12-10 12:10:13 +03:00
TOPDIR=/usr/share/mkimage-profiles; \
build-vm: try system tar2fs first It's at least removing the very obvious user->root attack through (maliciously) modifying bin/tar2fs and waiting for it to be run; if mkimage-profiles is installed system-wide as a package, the script from /usr/share/mkimage-profiles will be tried so those willing to allow vm/* build to themselves can provide for a passwordless sudo (as described in doc/vm.txt) to run a root-only writable script, not user-writable. Still not perfect but a step away from the abyss.
2016-11-07 13:20:09 +03:00
fi; \
Use correct path for system tar2fs tar2fs comes from m-p, not from mkimage. Also, we should use $TOPDIR from shell, not $(TOPDIR) from make, when calling it. Note: this is a security fix for environments relying on packaged mkimage-profiles with sudo enabled for the builder user. Fixes: f293239d5bd7d2a1e50e155f09effb56b262071e
2018-12-10 12:10:13 +03:00
if ! sudo $$TOPDIR/bin/tar2fs \
build-vm, kernel, tar2fs: make-initrd happens now in build-vm NB: 07-kernel change breaks multi-kernel setup! Breaks: 650e92bf7fe7bcec939d4512b275ad843268bba4
2019-05-07 19:17:55 +03:00
"$(VM_TARBALL)" "$(VM_RAWDISK)" "$(VM_SIZE)" "$(VM_FSTYPE)" \
"$(VM_BOOTLOADER)"; then \
90-build-vm.mk: better error reference In this case it's rather worth it to examine build.log than read documentation again (as vm.txt should have been read or at least skimmed through to get sudo setup ready, and the problem might be either an environment one or a bug).
2017-01-14 12:06:30 +03:00
echo "** error: sudo tar2fs failed, see build log" >&2; \
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
exit 1; \
fi
build-vm: Don't copy in .host/qemu* if tar2fs won't be called (gkebfm@ thinks it was a terrible idea in the first place and mike@ agrees; this is a rework TODO item)
2019-06-19 16:45:15 +03:00
# copy $(BUILDDIR)/.work/chroot/.host/qemu* into chroot if qemu is used
prepare-tarball-qemu:
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
@(cd "$(BUILDDIR)/.work/chroot/"; \
tar -rf "$(VM_TARBALL)" ./.host/qemu*) ||:
convert-image/tar:
mv "$(VM_TARBALL)" "$(IMAGE_OUTPATH)"
convert-image/tar.gz:
$(VM_GZIP_COMMAND) < "$(VM_TARBALL)" > "$(IMAGE_OUTPATH)"
convert-image/tar.xz:
$(VM_XZ_COMMAND) < "$(VM_TARBALL)" > "$(IMAGE_OUTPATH)"
convert-image/img: tar2fs
mv "$(VM_RAWDISK)" "$(IMAGE_OUTPATH)"
convert-image/qcow2 convert-image/qcow2c convert-image/vmdk \
convert-image/vdi convert-image/vhd: check-qemu tar2fs
build-vm, pack: implement qcow2c support This is a compressed version of good ol' qcow2. Suggested-by: Alexey Shabalin <shaba@altlinux.org>
2017-12-04 20:02:19 +03:00
@VM_COMPRESS=; \
case "$(IMAGE_TYPE)" in \
initial specific VM formats support Raw disk images are convenient and universal but there are custom formats like Qemu's qcow2 providing additional features, e.g. copy-on-write or space savings. All of this ultimately belongs to mkimage but in the mean time has been implemented here as well.
2012-06-19 17:51:56 +04:00
"vhd") VM_FORMAT="vpc";; \
build-vm, pack: implement qcow2c support This is a compressed version of good ol' qcow2. Suggested-by: Alexey Shabalin <shaba@altlinux.org>
2017-12-04 20:02:19 +03:00
"qcow2c") VM_FORMAT="qcow2"; VM_COMPRESS="-c";; \
initial specific VM formats support Raw disk images are convenient and universal but there are custom formats like Qemu's qcow2 providing additional features, e.g. copy-on-write or space savings. All of this ultimately belongs to mkimage but in the mean time has been implemented here as well.
2012-06-19 17:51:56 +04:00
*) VM_FORMAT="$(IMAGE_TYPE)"; \
esac; \
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
qemu-img convert $$VM_COMPRESS -O "$$VM_FORMAT" \
"$(VM_RAWDISK)" "$(IMAGE_OUTPATH)"
build-vm, main.mk, pack: add recovery.tar recovery.tar needed for tavolga (mipsel). This commit is the result of transferring the required functionality from build-mr (mipsel rootfs). This change uses external tool to build Tavolga-compatible recovery.tar. This simplifies the logic and avoids having recovery workdir in the profile. After this change, m-p will require tavolga-image-tools >= 3.0.
2019-05-19 12:39:04 +03:00
# for tavolga
convert-image/recovery.tar:
build-recovery-tar \
--image-name $(IMAGE_NAME) \
--date $(DATE) \
--compress-command '$(VM_GZIP_COMMAND)' \
--rootfs "$(VM_TARBALL)" \
--output "$(IMAGE_OUTPATH)" \
--line '$(RECOVERY_LINE)'
build-vm, pack: implement tar, tar.gz, tar.xz support for vm/* target build-vm ceases to be a target for building only virtual machine images. Now it can be used to build tarballs designed for installation on real machines. This commit is the result of transferring the required functionality from build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>. NB: mike@ strongly objected to this dilution but gave up eventually; the whole kernel/build-vm/tar2fs/pack mess should be split into distinct layers busy with their own responsibilities: 1) a tarball with kernel is done without tar2fs at all (and no build-vm bits should be needed either, maybe it's worth splitting and renaming as "vm" meaning disk image for some armh board is grossly misleading); 2) a tarball with kernel can be further (multi-)packed as, well, (compressed) tarball and a disk image (only the latter one should employ build-vm/tar2fs); 3) compression should be done in pack feature style, preferably described once and not duplicated all over the profile for every single new kind of its output. In the mean time, running into this and moving no further starts to hurt more than it could help.
2019-05-19 09:23:16 +03:00
post-convert:
@rm -f "$(VM_RAWDISK)"; \
if [ "0$(DEBUG)" -le 1 ]; then rm -f "$(VM_TARBALL)"; fi
build-vm: Don't copy in .host/qemu* if tar2fs won't be called (gkebfm@ thinks it was a terrible idea in the first place and mike@ agrees; this is a rework TODO item)
2019-06-19 16:45:15 +03:00
convert-image: convert-image/$(IMAGE_TYPE) post-convert; @:
initial specific VM formats support Raw disk images are convenient and universal but there are custom formats like Qemu's qcow2 providing additional features, e.g. copy-on-write or space savings. All of this ultimately belongs to mkimage but in the mean time has been implemented here as well.
2012-06-19 17:51:56 +04:00
proxy CLEANUP_PACKAGES down mkimage implementation requires that the variables to be passed to the scripts are to be prefixed with GLOBAL_ or INFO_ tags as appropriate; in this case the upstream makefile didn't care to.
2012-06-26 00:22:35 +04:00
run-image-scripts: GLOBAL_CLEANUP_PACKAGES := $(CLEANUP_PACKAGES)
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
initial specific VM formats support Raw disk images are convenient and universal but there are custom formats like Qemu's qcow2 providing additional features, e.g. copy-on-write or space savings. All of this ultimately belongs to mkimage but in the mean time has been implemented here as well.
2012-06-19 17:51:56 +04:00
# override
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
pack-image: MKI_PACK_RESULTS := tar:$(VM_TARBALL)
image.in, build-*: generalize SUBDIRS This is a fix to previous failures of ve/vm + use/repo/main build attempts (in fact, any non-distro/ targets). SUBDIRS were just optimized away...
2018-02-15 16:57:50 +03:00
all: $(GLOBAL_DEBUG) \
build-image copy-subdirs copy-tree run-image-scripts pack-image \
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
convert-image postprocess $(GLOBAL_CLEAN_WORKDIR)
Reference in New Issue Copy Permalink