Recent(?) change forces reboot after adding vif

[Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>]

Hi,

Some recent(ish) change made Windows want a reboot after adding a vif to
the domU config, even if such vif was there in the past (so, the driver
was installed). While the prompt is there, network clearly works
already.

The specific workflow is:
1. Create domU with vif included.
2. Install Windows (10 or 11 - both seems to be affected)
3. Install PV drivers
4. Shutdown Windows
5. Remove vif from the domU config
6. Start Windows, wait(?), shutdown
7. Re-add the vif and start domU

Such operation used to work perfectly fine without any extra reboot. But
now domU prompts to reboot, like this:
https://openqa.qubes-os.org/tests/146690#step/windows_clipboard_and_filecopy/25

Note that network actually works already at the point then reboot is
prompted - so it seems the reboot isn't really necessary?

This is especially problematic because we have some domUs intentionally
don't persist changes on the disk on reboot. So, this basically means
reboot loop if you do a change to vif config...

The old/new versions are:

    xenvif updated from 9fd1af to 4608bc 
    xennet updated from ad7717 to 0b1a93 

Full version differences can be seen at
https://github.com/QubesOS/qubes-vmm-xen-windows-pvdrivers/pull/4/files

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

Attachment: signature.asc
Description: PGP signature