Any tag ending in ".gpg" will be considered to be the according
keyring file in /usr/share/keyrings/. This is at least needed for some
Ubuntu releases which were eol'ed in the past few years, especially
because Ubuntu split up their keyrings much more finegrained than just
"archive" and "archive-removed-keys".
This adds a parameter '--lvm_thin' to xen-create-image that allows you
to specify the thin pool where the thin logical volumes will be
created.
If '--lvm_thin' is not specified, nothing will change and thick
provisioned volumes will be created.
[Committer's note: Code logic taken from
https://github.com/youknow0/xen-tools-thin-provisioning/commit/a6f267ef
and adapted to current code. Needed more than just a rebase. All
trailing whitespace has been removed, too.]
Fixesxen-tools/xen-tools#47.
If an "lvremove" is immediately followed by an "lvcreate" for an LV
with the same name, "mkswap" (and maybe other commands) occasionally
fail with "Device or resource busy".
Work around it by using sync and sleep.
This fixes a regression introduced in
503db1668b595d71b45a94d7391d5c9e6b9e9d1e.
`@array = undef` doesn't empty an array but fills it with one item
which is undef. Hence `$#array` is zero and hence false.
Since the commit above, `@array = ()` was used instead of `@array =
undef`, hence `$#array` no more was false when the array seemed to be
empty (but wasn't). This caused an empty partition table in the
configuration file and hence prohibited the start of the DomU.
This commit fixes the according `!$#array` to just `!@array` and adds
the according changelog entry for both commits. (I initially thought
that such a tiny commit like the one above is not worth being
mentioned. I obviously was wrong.)
Its default values work around bug #792729 in debootstrap.
Does not yet import those keys into APT's keyring inside the DomU.
(Not sure if debootstrap does that already, either.)
Split off hardcoded release code names list and default mirrors in
xen-create-image into separate configuration file which are parsed
before the default settings or command-line options are set.
Older Debian releases are not able to cope with sha256 hashed
passwords and refuse login without any visible or accessible error
message.
This only affects the initially set root password and does not affect
passwords which are later set with the DomU's "passwd" tool.
