lstocchi d2ea5a3fd0 prevent starting/stopping legacy Hyper-v machines when not elevated ...

Podman 5.x and earlier required to run as admin to work with Hyper-v.
Starting from Podman 6 this is not mandatory anymore as Registry
entries are handled differently. However, it may
happen the user have a legacy machine running when switching to Podman 6
or starts an old machine in elevated mode and then tries to stop it as a
normal user with Podman 6. If that happens the system will end up in a corrupted state
as the gvproxy process will not be stopped.
To prevent such scenario and issues, this commit maintains the original
behavior Podman 5.x has. Legacy Hyper-v machines needs to be handled
with elevated rights.

Signed-off-by: lstocchi <lstocchi@redhat.com>

2026-01-09 08:07:00 +01:00

..

vsock

remove legacy registry entry

2025-11-20 16:51:47 +01:00

hutil.go

prevent starting/stopping legacy Hyper-v machines when not elevated

2026-01-09 08:07:00 +01:00

stubber.go

prevent starting/stopping legacy Hyper-v machines when not elevated

2026-01-09 08:07:00 +01:00

volumes.go

hyperv should reuse hvsock registry entries when possible

2025-11-20 16:51:31 +01:00