Preregister entries on the windows registry to be reused with active hyperv machine

[lstocchi]

Feature request description

This came up when discussing with @l0rd about #24813

With that PR, it is possible to run podman on hyperv as a normal user (elevated rights are only asked for registry stuff).
The ideal solution would be to remove the need to request for elevated rights when creating/deleting a podman machine.

From a registry path perspective we cannot do much. Windows requires us to create an entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\GuestCommunicationServices because it is that the area reserved for hyperv services and where windows looks for when managing hvsock.

And, because of it, we are forced to write in the registry by being admin.

However, the vsock GUID on Windows have a specific format <port>-facb-11e6-bd58-64006a7986d3 where port is in hexadecimal (e.g "00000ac9" represents port 2761) and on hyper-v only one running machine per time is allowed.

An idea to be investigated could be to add some entries in the registry by preallocating some ports when installing podman and re-use these same ports for every new podman machine. As two machines cannot be started at the same time there would be no conflicts and there could be no need to add new registry entries for each init action.

Suggest potential solution

No response

Have you considered any alternatives?

No response

Additional context

This issue is related to #24813 and i opened it so we don't lose this idea.
I'll close/update it based on how that PR evolves.