From 4c65aaa57413cc99641a6adb320dbc46f055ea1f Mon Sep 17 00:00:00 2001
From: Peter Palfrader <peter@palfrader.org>
Date: Fri, 5 Jul 2019 11:31:17 +0200
Subject: [PATCH] more notes on the network issue
---
tsa/howto/upgrades/buster.mdwn | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/tsa/howto/upgrades/buster.mdwn b/tsa/howto/upgrades/buster.mdwn
index 7c2eb922..b88145e0 100644
--- a/tsa/howto/upgrades/buster.mdwn
+++ b/tsa/howto/upgrades/buster.mdwn
@@ -5,9 +5,15 @@ Caveats
* Warning: upgrading(restarting) openvswitch will mean all guests lose network.
- * At least on kvm5, I had to reorder inet6 and inet4 stanzas in /etc/network/interfaces
- for brpub to have an ipv6 address and route to the guest network after the
- upgrade.
+ * At least on kvm5, brpub was having issues. Either ipv4 or ipv6 address was missing,
+ or the v6 route to the guests was missing. Probably because the ipv6 route
+ setting failed since we set a prefsrc and that was only brought up later?
+
+
+ Rewrote network/interfaces to set things up more manually.
+ On your host, check if brpub has both ipv4 and ipv6 addresses after boot before
+ launching VMs, and that is has an ipv6 route into brpub with the configured
+ prefsrc addr. If not, fiddle likewise.
* On physical hosts witch /etc/sysfs.d/local-io-schedulers.conf, note that 'deadline' no
longer existsts. Probably it is also not necessary as Linux might pick the right
--
GitLab