[2902312214] Upstream Reporter: Jeff MAURY
Upstream issue status: Closed
Upstream description:

Issue Description

I can't start HyperV podman machines got an error each time I start it. The VM is started but the initialization process is errored. Might be cause by my Windows user name (thus home dirrectory) containing space

Steps to reproduce the issue

Steps to reproduce the issue

1. create an HyperV podman machine
2. start it

Describe the results you received

VM is started, error messages in the console:

podman machine start h1
Starting machine "h1"

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

        podman machine set --rootful h1

Error: accepts 2 arg(s), received 3
Error: Process exited with status 125

Describe the results you expected

Machine should be started successfully

podman info output

OS: windows/amd64
provider: hyperv
version: 5.4.0

Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:59529: connectex: No connection could be made because the target machine actively refused it.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Win11Pro

Additional information

podman machine start --log-level debug h1
time="2025-03-07T09:10:00+01:00" level=info msg="podman filtering at log level debug"
time="2025-03-07T09:10:00+01:00" level=debug msg="Using Podman machine with `hyperv` virtualization provider"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinehyperv is 60"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinehyperv is 65"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinehypervcache is 71"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJEFFMA~1AppDataLocalTemppodman is 43"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinehypervh1.json is 68"
Starting machine "h1"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinewsl is 57"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinewsl is 62"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinewslcache is 68"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJEFFMA~1AppDataLocalTemppodman is 43"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinewslpodman-machine-default.json is 85"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinehyperv is 60"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinehyperv is 65"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.localsharecontainerspodmanmachinehypervcache is 71"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJEFFMA~1AppDataLocalTemppodman is 43"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinehypervh1.json is 68"
time="2025-03-07T09:10:00+01:00" level=debug msg="socket length for C:UsersJeff Maury.configcontainerspodmanmachinehypervh3.json is 68"
Error: unable to start "h1": already running
time="2025-03-07T09:10:00+01:00" level=debug msg="Shutting down engines"