Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Podman Machine Init] not allocating Memory/Compute/Storage Properly #11831

Closed
n0rig opened this issue Oct 1, 2021 · 2 comments
Closed

[Podman Machine Init] not allocating Memory/Compute/Storage Properly #11831

n0rig opened this issue Oct 1, 2021 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@n0rig
Copy link

n0rig commented Oct 1, 2021

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description
On podman v3.4.0, it seems all podman machine are being initialized with zero memory, zero cpus, and zero disk_size.

[machine]
  cpus = 0
  disk_size = 0
  memory = 0

Even when supplying values via podman machnine init, the machine that is created has no compute/memory/storage.

Steps to reproduce the issue:

  1. install podman 3.4.0
brew install podman
  1. delete your default podman vm

This should do the trick

podman machine stop ; sleep 5; podman machine rm --force
  1. Create a new vm with desired memory/compute/storage
podman machine init --cpus 2 --disk-size 40 --memory 4096

Describe the results you received:
The VM has no mem/compute/disk:

$ podman machine list

NAME                     VM TYPE     CREATED        LAST UP            CPUS        MEMORY      DISK SIZE
podman-machine-default*  qemu        5 minutes ago  Currently running  0           0B          0B

You also cannot 'start' the vm:

podman machine start
INFO[0000] waiting for clients...
INFO[0000] listening tcp://0.0.0.0:7777
INFO[0000] new connection from  to /var/folders/3n/f7qwz9_923xd492c57tbplkh0000gp/T/podman/qemu_podman-machine-default.sock
Waiting for VM ...

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

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. failed to create sshClient: Connection to bastion host (ssh://core@localhost:60358/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:60433->[::1]:60358: read: connection reset by peer

Output of podman info --debug:

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. failed to create sshClient: Connection to bastion host (ssh://core@localhost:60358/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:60439->[::1]:60358: read: connection reset by peer

Package info (e.g. output of rpm -q podman or apt list podman):

N/A (installed via brew on macos)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

$ uname -a

Darwin <redacted> 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 1, 2021
@n0rig
Copy link
Author

n0rig commented Oct 1, 2021

Seems related to #11824

@n0rig
Copy link
Author

n0rig commented Oct 1, 2021

Closing in favor of #11824 as it's already been worked on.

@n0rig n0rig closed this as completed Oct 1, 2021
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

1 participant