cb62bae9b8
Qemu-nbd does not perform well with older versions of qemu due to the lack of writeback caching mode. It also only builds qcow2 images and there is a desire for raw image support. Finally, qemu-nbd makes it very difficult to build images concurrently due to the somewhat opaque nature of how it selects a /dev/nbd# device. losetup, on the other hand, makes this process very straight forward. Change-Id: I309fad8af4fd1e8d1720c17b65e1897a76d5e897 Co-Author: Clint Byrum <clint@fewbar.com>
16 lines
459 B
Bash
Executable File
16 lines
459 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -e
|
|
|
|
yum remove -y grub2-tools
|
|
|
|
#GRUB_CFG=/boot/grub2/grub.cfg
|
|
|
|
#[ -f "$GRUB_CFG" ]
|
|
|
|
# Update the config to have the search UUID of the image being built.
|
|
# When partition staging is moved to a separate stage, this will need to happen
|
|
# there. This generates a non-UUID config, which is irrelevant for booting with
|
|
# hypervisor kernel + ramdisk, and fixed up by 51-grub for vm images.
|
|
#GRUB_DISABLE_LINUX_UUID=true grub2-mkconfig -o $GRUB_CFG
|