Vagrant: fixes for Jammy virtual machine

Tools/vagrant/initvagrant-desktop.sh

@@ -44,6 +44,11 @@ sudo -u "$VAGRANT_USER" dbus-launch gsettings set org.gnome.desktop.session idle
 sudo -u "$VAGRANT_USER" mkdir -p /home/"$VAGRANT_USER"/.config
 echo "yes" | sudo -u "$VAGRANT_USER" dd of=/home/"$VAGRANT_USER"/.config/gnome-initial-setup-done
 
+# sssd is missing config:
+if [ ${RELEASE_CODENAME} == 'jammy' ]; then
+    systemctl disable sssd
+fi
+
 # start the graphical environment right now:
 systemctl isolate graphical.target
 

Tools/vagrant/initvagrant.sh

@@ -61,6 +61,17 @@ echo "source $BASHRC_GIT" |
 # link a half-way decent .mavinit.scr into place:
 sudo --login -u $VAGRANT_USER ln -sf /vagrant/Tools/vagrant/mavinit.scr /home/$VAGRANT_USER/.mavinit.scr
 
+RELEASE_CODENAME=$(lsb_release -c -s)
+
+# no multipath available, stop mutlipathd complaining about lack of data:
+if [ ${RELEASE_CODENAME} == 'jammy' ]; then
+    cat >>/etc/multipath.conf <<EOF
+blacklist { devnode "sda" }
+blacklist { devnode "sdb" }
+EOF
+fi
+
+
 #Plant a marker for sim_vehicle that we're inside a vagrant box
 touch /ardupilot.vagrant