Fix HVMs so they don't only work if the cluster you're on happens to have

hosts with an eth0 that's lucky enough to have an IPv4 address on it due
to random luck having nothing to do with the bridge all the Xen stuff is on.

diff --git a/debian/changelog b/debian/changelog
index e2a7aee..bb7138f 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -15,8 +15,10 @@ invirt-xen-config (0.0.54) unstable; urgency=low
     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>  Fri, 25 May 2018 03:06:00 -0400
+ -- Mitchell Berger <mitchb@mit.edu>  Sun, 27 May 2018 01:45:00 -0400
 
 invirt-xen-config (0.0.53) unstable; urgency=low
 

diff --git a/qemu-ifup.invirt b/qemu-ifup.invirt
index 4d3cb0d..756006d 100755 (executable)
--- a/qemu-ifup.invirt
+++ b/qemu-ifup.invirt
@@ -14,4 +14,4 @@ qemu_online=yes
 vif=vif${domid}.${ifnum}
 export vif qemu_online INTERFACE type_if
 
-exec /etc/xen/scripts/vif-invirtroute add
+exec /etc/xen/scripts/vif-invirtroute add netdev=$(invirt-getconf xen.iface)