kubernetes-sigs / kubernetes-sigs/image-builder

Proxmox using 2 CPU and 2 sockets in stead of 4 CPU and 1 socket?

Open
#2,003 0 comments 0 reactions 0 assignees View on GitHub
kind/bug
Dominant language
Go Template
Stars
550
Forks
508
Avg merge
7d 10h
Merged PRs (30d)
8

Description

## Environment

- **Make target:** `make proxmox`
- **Run using container image? (Y/N):** Y
- **Environment vars:**
```

```
- **Vars file:**
```

```

## What steps did you take and what happened?
The VM that is created in proxmox has 2 CPU's and 2 sockets.

## What did you expect to happen?
4 CPU's and 1 socket.

## Relevant log output

Log Output

```

```

## Anything else you would like to add?
Is there a reason that it uses 2 sockets? Otherwise I'll create a PR for 1 socket and 4 CPU's!

Thank you.

---

/kind bug

Contributor guide

Open the contributing guide

Research direction

Start with the `make proxmox` target and trace how the Proxmox VM CPU and socket settings are produced. Reproduce the issue with the container image and inspect the resulting VM configuration. Done means the created VM uses 4 CPUs and 1 socket, with the existing behavior and any relevant tests updated accordingly.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.