Checking if a volume exists before attempting to create it results in
a "time of check to time of use" race. When the check is done the
volume doesn't exist but then, because it is shared storage, it is
then created by another node before the local attempt to create it.
This results in an unexpected failure.
It is better to simply attempt to create the volume and ignore EEXIST
in cases where this is permissible.
Implementing this properly is complicated by the fact that the
exception appears to contain only an error message and does not appear
to contain a useful error code. Digging through the layers in, for
example, fog-libvirt provides no evidence why this is so. However,
the error message seems fairly unique and matching it is easy, so just
do that. A small hack to vastly improve stability.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Support `vagrant package` of e.g. bento-derived boxes that require SSH
hostkeys already set (as in the case of bento/debian-7 and above,) as
well as leave existing LVM UUIDs untouched (e.g. in bento/ubuntu-18.04.)
Instead of hard-coding sysprep operations, use an environment variable
to set these instead.
Use the Chef bento use case as an example for customizing sysprep
operations.
Default to using the same storage pool in case the user defines
storage_pool_name without defining snapshot_pool_name and only use a
separate pool when snapshot_pool_name is explicitly set.
This will ensure that setting storage_pool_name to a different pool does
not also require setting snapshot_pool_name to match previous behaviour.
Additionally it is reasonable for a user to assume that if a Vagrantfile
sets storage_pool_name to something other than 'default', then there
should be no need for a default pool.
the 'echo' service is often not available out-of-the-box,
so the 'ping' of the ssh interface fails. This results in the
wrong ip addresses being used in /etc/exports, which results in
the vm not being able to mount the vagrant shares.
The 'vagrant ssh interface' will have the service 'ssh' available
(you won't be able to login to your vagrant box else), so it makes
sense to use that service for the ping.
This fixes the vm not being able to mount the shares over nfs after
a reload due to the wrong ip addresses being used.
Forcing an underscore between a defined default_prefix and the machine name
forces a naming format that the user might not want.
If they define their own default_prefix and want an underscore between that and
the machine name, they can/should add the underscore to the default_prefix.
For Darwin operating systems, `cmd` is not a valid keyword, thus
resulting in the following error when executing Vagrant `reload` and
`destroy` commands:
ps: cmd: keyword not found
ps: no valid keywords; valid keywords:
This commit ensures that SSH sessions for forwarded ports are
terminated via their respective process ID for Darwin *and* Linux
operating systems.
Both Darwin and Linux operating systems support the `command` keyword,
as reflected in the following documents, respectively:
- https://apple.co/2H7jFwl
- https://bit.ly/2HakfW0
* Add USB controller configuration
* Update README with USB controller configuration info
* Rename USB controller parameter to usb_controller
* Code style fixup
Some UEFI firmwares may want to use a non-volatile memory to store
variables.
This requires to specify loader and nvram to use UEFI boot in QEMU.
Specifying loader and nvram at the same time will set loader to
type 'pflash' instead of 'rom'.
If loader is used without nvram option type will remain 'rom'.
Further information can be found at libvirt documentation:
https://libvirt.org/formatdomain.html#elementsOS
This will obviously raise an exception if the data is not
convertable. Seems to be the best option, since to_i converts
'non-integer' strings to zero, which would lead to unpredicable
behaviour.
