Closed jeffmaury closed 10 hours ago
This is expected, there can only ever be one running VM (WSL is the exception), see https://github.com/containers/podman/issues/18415
This is expected, there can only ever be one running VM (WSL is the exception), see #18415
The error message is kinda cryptic then and I can start several HyperV machines:
podman machine init h1 --now
podman machine init h2
podman machine start h2
I don't have access to a windows system but looking at the code this should be impossible, it fails correctly for we with qemu and it uses the exact same code with hyperV as well. Are you sure your didn't create WSL machines there?
How should the error look in your opinion then?
I don't have access to a windows system but looking at the code this should be impossible, it fails correctly for we with qemu and it uses the exact same code with hyperV as well. Are you sure your didn't create WSL machines there?
No I switched to provider=hyperv in containers.conf so WSL is not in the scenario
How should the error look in your opinion then?
Either can't create 2 HyperV machines or can't start 2 HyperV machines
you can create as many machines as you want you just cannot have more than one running at the same time.
No I switched to provider=hyperv in containers.conf so WSL is not in the scenario
I am not sure I can follow here. You reported this bug saying it does not work but now you are saying it does work? What is the difference?
you can create as many machines as you want you just cannot have more than one running at the same time.
No I switched to provider=hyperv in containers.conf so WSL is not in the scenario
I am not sure I can follow here. You reported this bug saying it does not work but now you are saying it does work? What is the difference?
I was just answering that WSL was not involved in the scenario as I switched containers.conf and I made sure I had no existing WSL machines
Right but you reported this issue saying you cannot start more than one hyperV machine which as I said is expected.
Then you answered that in fact you can start more than one hyperV machine so that just leaves me totally confused. Which is it now? I can just look at the code here and say it works the same way on qemu, applehv, hyperV and libkrun so it should rightfully error out when you try to start another VM when one is already running.
If I create and start the machines in 1 step then it fails. If I create the machines then start them, then it works. That's why I think multi machines are supported but the error reported is a bug
Issue Description
I created and started a first HyperV Podman machine (h1). When I do the same for a second one (h2), it gets created but start is rejected with the error message:
Error: unable to start "h2": machine h1: VM already running or starting
Steps to reproduce the issue
Steps to reproduce the issue
podman machine init h1 --rootful --now
podman machine init h2 --rootful --now
Describe the results you received
Describe the results you expected
Both podman machines running
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting