Virtual switches a bit broken? (November 2024)

General Discussion
17

The issue in this thread with an error 500 creating local VIRTUAL devices has been resolved. However there were three other issues with local VIRTUAL devices in general, and the stock Virtual Switch in particular, which were discussed in another thread.

  1. Although a preference had been added to the Virtual Switch Edge driver and added to the profiles in the driver package, local VIRTUAL devices don’t use those profiles and the profiles they did use hadn’t been updated. That has been resolved.
  2. The new device preference is working at the API level, but unfortunately device preferences have never been available to Edge drivers being used for VIRTUAL devices. By that I mean device.preferences is empty in the driver. That has not been resolved.
  3. Edge drivers being used for VIRTUAL devices do not receive the infoChanged lifecycle. That has not been resolved.

The new code in Virtual Switch looks for the device preference being true in order to be back compatible with the previous code. As the device preference can’t be read that means the behaviour of the stock local VIRTUAL switch has changed. It now doesn’t include state_change=true by default.

3 Likes