# Are we stuck? The situation has not changed, but it should also not just hang around forever.
As was outlined before, that code is unmaintained, hence disabled consciously (more details above). What does that leave us with as options. a) just re-enable and ship it, that would make more people reply on it longer which is not the way this seems to be going b) keep it disabled and say "bad luck" is not nice to the people still depending on it c) compromises ... (c) leads me to a few aspects of the discussion so far: c1: workarounds Christopher said: > It would be great if there were a package to pull down to use until a longer term solution is found. I agree, but due to the risk of (a) just extending the use of something not meant to be used, it is not a good path. We could provide a PPA with it enabled as Lukas did, thanks for the feedback to also need MPT btw. If we go that route it would be with MPT. That would allow people to use that as fallback until a long term solution is found. But that would be a one off PPA, not regularly rebuilt for fixes, not under security monitoring and so on - TL;DR we'd establish something we'd not want people to really use. But that feels like being stuck... ** Bug watch added: bugs-devel.debian.org/ #1016359 https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1016359 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2129178 Title: Can not boot qemu VMs using ParaVirtual SCSI controllers with Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2129178/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
