X-Git-Url: http://xvm.mit.edu/gitweb/invirt/packages/invirt-xen-config.git/blobdiff_plain/eec0fc5b94f1bed727d1255dba2dc6cfd046a871..98e4d64197543617031240c55b9bd261912d7613:/debian/changelog?ds=sidebyside

diff --git a/debian/changelog b/debian/changelog
index 9c1ef64..c0ac0ae 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,13 +1,60 @@
+invirt-xen-config (0.0.57) unstable; urgency=low
+
+  * invirt-database: Fix the autoinstall logic so that if we've
+    increased the memory temporarily for the autoinstall above
+    the machine's database setting, we also bring maxmem up to
+    the same level.  Otherwise the machine doesn't turn on
+    because it's requesting to start with more memory than maxmem,
+    and this failure mode is silent to the user.
+
+ -- Mitchell Berger <mitchb@mit.edu>  Sat, 02 Feb 2019 16:52:00 -0500
+
+invirt-xen-config (0.0.56) unstable; urgency=low
+
+  * vif-invirtroute: Kill arpspoof with SIGKILL when we're done.  The
+    version in this distro (which is the latest beta from the
+    unmaintained upstream) tries to "clean up" when you normally
+    terminate it.  This involves trying to perform an ARP lookup
+    without interfering to see what the MAC should've been and then
+    sending replies for that.  This appears to cause a race depending
+    on whether the entry for the machine's old domain (if it's being
+    rebooted) is listed as <incomplete> in the ARP table or is totally
+    flushed.  If you lose the race, it sends further gratuitous ARPs
+    telling the router that your MAC is all-zeros because of a bug
+    where it fails to check for an incomplete ARP entry.  This is
+    believed to cause the bug that has plagued XVM for years where
+    you sometimes lose off-network connectivity on reboot.
+
+ -- Mitchell Berger <mitchb@mit.edu>  Mon, 25 Jun 2018 22:04:00 -0400
+
+invirt-xen-config (0.0.55) unstable; urgency=low
+
+  * invirt-database: bump up autoinstall memory to make modern releases
+    work again.
+
+ -- Mitchell Berger <mitchb@mit.edu>  Fri, 01 Jun 2018 02:17:00 -0400
+
 invirt-xen-config (0.0.54) unstable; urgency=low
 
-  * invirt-database: pass through parameters for the "other" IP address,
-    if any, to vif-invirtroute.
+  * invirt-database: handle several possible actions to take with an
+    "other" set of network parameters.  Renumber a machine by swapping
+    the sets of netparams, DNAT from an old address by passing through
+    additional parameters to vif-invirtroute, and teardown an IP
+    transition by clearing all the "other" values.  Also, use the
+    netmask and gateway for the VM when autoinstalling, rather than
+    parameters from the global cluster configuration.
   * vif-invirtroute: if there is an "other" IP address, DNAT it to the
     primary IP, set up routing to get it to the VM, and arp for it.
     Also, cut out the nonsense with backgrounding arpspoof, sleeping, and
-    killing it; we have the technology for 'timeout'.
-
- -- Mitchell Berger <mitchb@mit.edu>  Tue, 15 Nay 2018 19:50:00 -0400
+    killing it; we have the technology for 'timeout'.  Finally, don't
+    pass a "src" argument to "ip route del" to ensure a match even if
+    the host's "main IP" has changed and caused the route to be inserted
+    with a different src.
+  * templatize-xend-config: explicitly turn on the relocation server
+  * qemu-ifup.invirt: make HVMs work and not only if your eth0 just happens
+    to have an IPv4 network address sitting on it
+
+ -- Mitchell Berger <mitchb@mit.edu>  Sun, 27 May 2018 01:45:00 -0400
 
 invirt-xen-config (0.0.53) unstable; urgency=low