Paul Holzinger 8472bf223e machine/hyperV: move ssh mounts to after the ready check ...

We are seeing frequent flakes in hyperV machine tests. The machine start
fails with an ssh handshake failure:

ssh: handshake failed: read tcp 127.0.0.1:56425->127.0.0.1:56377:
wsarecv: An existing connection was forcibly closed by the remote host.

Normally we do the ssh probe in conductVMReadinessCheck() with a retry
mechanism, however because the hyperV mount code already used ssh in
PostStartNetworking() we never got there and failed early.

PostStartNetworking seems the wrong place to mount anyway so move this
to MountVolumesToVM() instead which is placed after the ready check
already so it should have a working ssh by then.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>

2026-06-05 18:34:44 +02:00

..

vsock

Add command podman system hyperv-prep

2026-04-29 23:00:29 +02:00

hutil.go

hyperv: propagate detailed error from Hyper-V permission checks

2026-05-25 00:10:18 +02:00

stubber_test.go

hyperv: propagate detailed error from Hyper-V permission checks

2026-05-25 00:10:18 +02:00

stubber.go

machine/hyperV: move ssh mounts to after the ready check

2026-06-05 18:34:44 +02:00

volumes.go

Add command podman system hyperv-prep

2026-04-29 23:00:29 +02:00