Skip to content

Releases: LINBIT/virter

Release v0.20.1

27 Sep 14:22
Compare
Choose a tag to compare
netcopy: Give --protect-args option to rsync for vm copy

This prevents rsync from using a shell on the remote side
to expand special characters. This makes transfer of files
and directories containing whitespace work.

Signed-Off-By: Johannes Thoma <[email protected]>

Release v0.20.0

27 Sep 09:56
Compare
Choose a tag to compare
vm: add tools and docs for convenient ssh integration

Release v0.19.1

26 Jul 12:47
v0.19.1
Compare
Choose a tag to compare
Release 0.19.1

Release v0.19.0

01 Jul 07:49
v0.19.0
Compare
Choose a tag to compare
Release 0.19.0

Release v0.18.1

04 Mar 10:42
v0.18.1
Compare
Choose a tag to compare
Release 0.18.1

Release v0.18.0

20 Dec 09:20
v0.18.0
Compare
Choose a tag to compare
Release 0.18.0

Release v0.17.0

01 Dec 11:57
Compare
Choose a tag to compare
make disk driver cache attribute configurable

In some typical virter usage scenarios, the consistency of guest disks
after a host crash is unimportant. Hence setting the cache to "unsafe"
is acceptable. This improves disk performance.

Release v0.16.0

22 Nov 11:31
Compare
Choose a tag to compare
container: increase copy timeout

The implementation of this involves file IO and running an external
process, so it can take some time on a system under heavy load.

Release v0.15.1

08 Nov 12:40
Compare
Choose a tag to compare
vm run: avoid adding empty "mounts" section to user-data

An empty "mounts" section causes cloud-init to fail to start. It gets
far enough that the VM is accessible, but still registers as a failed
unit in systemd. Prevent this by only writing the "mounts" section when
there are actual mounts.

Release v0.15.0

08 Nov 10:54
Compare
Choose a tag to compare
define domain before creating resources it depends on

And undefine it after those resources have been removed.

This has the advantage that the VM is defined whenever the other
resources exist. So we can find those other resources in order to remove
them.

Previously a failure while removing a VM could leave orphaned disks.
These caused problems when trying to create the same VM again.