libvirt: Version bump to 11.9.0, split out variants, add startup items

[iamGavinJ]

Description

Version bump to 11.9.0
Additionally variants for bhyve, esx, test, vbox, and vmware have been added, and also set at default variants as to not break prior installs.
Startup items have been created for libvirt daemons.

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 15.7.2 24G325 arm64
Xcode 26.0.1 17A400

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@ryandesign for port libvirt.

[mohd-akram]

Startup item shouldn't be needed unless you want to run as root (and should just launch libvirtd).

[ryandesign]

What advantage is there for the user in being able to disable these features? In other words, why do we need variants?

[ryandesign]

Previous discussion about adding a startup item is at https://trac.macports.org/ticket/67736

[iamGavinJ]

Startup item shouldn't be needed unless you want to run as root (and should just launch libvirtd).

vmnet-bridge (and almost all other network types) and passthrough of disks, both basic features IMO, require root and therefore the virt*d daemons running as root. Libvirt domains needing to be auto-started at boot - Plenty of Linux dev work happens on macOS. Using Libvirt+QEMU in this way is analogous to WSL.

What advantage is there for the user in being able to disable these features? In other words, why do we need variants?

Faster build; Removal of unnecessary code paths; Minimisation of attack surface.

[mohd-akram]

I would say running as root increases the attack surface :)

libvirt strongly recommends the qemu/qemu user/group.

vmnet-bridge (and almost all other network types)

For this you can use the socket_vmnet port.

passthrough of disks

I'm not sure if root is needed for this or how it works on macOS TBH.

[iamGavinJ]

If this isn't going to be merged please close the PR and remove the openmaintainer tag because I'm tired of wasting my time trying to make ports better if they just get ignored!