[GH-ISSUE #10640] Debian 13 VM #2296

Closed
opened 2026-02-26 12:51:57 +03:00 by kerem · 3 comments
Owner

Originally created by @Mortvert on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10640

Originally assigned to: @MickLesk on GitHub.

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Debian 13 (VM)

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-13-vm.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

VM creation fails when trying to create the VM /w host CPU

🔄 Steps to reproduce the issue.

Run the setup script
Select advanced setup
Change CPU type to Host

Paste the full error output (if available).

____       __    _                ________

/ __ ___ / /_ ()__ _____ < /__ /
/ / / / _ / __ / / __ `/ __ \ / / /_ <
/ // / __/ // / / // / / / / / // /
/
/_/.//_,// // ///___/
(Trixie)
🧩 Using Advanced Settings
🆔 Virtual Machine ID: 108
📦 Machine Type: i440fx
💾 Disk Size: 256G
💾 Disk Cache: None
🏠 Hostname: dockert-intranet
🖥️ CPU Model: Host
🧠 CPU Cores: 4
🛠️ RAM Size: 16384
🌉 Bridge: vmbr0
🔗 MAC Address: 02:E4:4F:37:0F:4B
🏷️ VLAN: Default
⚙️ Interface MTU Size: Default
☁️ Configure Cloud-init: no
🌐 Start VM when completed: yes
🚀 Creating a Debian 13 VM using the above advanced settings
✔️ Using General for Storage Location.
✔️ Virtual Machine ID is 108.
✔️ https://cloud.debian.org/images/cloud/trixie/latest/debian-13-nocloud-amd64.qcow2
✔️ Downloaded debian-13-nocloud-amd64.qcow2
Creating a Debian 13 VM 400 Parameter verification failed.
bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf'
qm create [OPTIONS]

[ERROR] in line 512: exit code 255: while executing command qm create "$VMID" -agent 1"${MACHINE}" -tablet 0 -localtime 1 -bios ovmf"${CPU_TYPE}" -cores "$CORE_COUNT" -memory "$RAM_SIZE" -name "$HN" -tags community-script -net0 virtio,bridge="$BRG",macaddr="$MAC"$VLAN"$MTU" -onboot 1 -ostype l26 -scsihw virtio-scsi-pci

🖼️ Additional context (optional).

No response

Originally created by @Mortvert on GitHub (Jan 8, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10640 Originally assigned to: @MickLesk on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Debian 13 (VM) ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-13-vm.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. VM creation fails when trying to create the VM /w host CPU ### 🔄 Steps to reproduce the issue. Run the setup script Select advanced setup Change CPU type to Host ### ❌ Paste the full error output (if available). ____ __ _ ________ / __ \___ / /_ (_)___ _____ < /__ / / / / / _ \/ __ \/ / __ `/ __ \ / / /_ < / /_/ / __/ /_/ / / /_/ / / / / / /___/ / /_____/\___/_.___/_/\__,_/_/ /_/ /_//____/ (Trixie) 🧩 Using Advanced Settings 🆔 Virtual Machine ID: 108 📦 Machine Type: i440fx 💾 Disk Size: 256G 💾 Disk Cache: None 🏠 Hostname: dockert-intranet 🖥️ CPU Model: Host 🧠 CPU Cores: 4 🛠️ RAM Size: 16384 🌉 Bridge: vmbr0 🔗 MAC Address: 02:E4:4F:37:0F:4B 🏷️ VLAN: Default ⚙️ Interface MTU Size: Default ☁️ Configure Cloud-init: no 🌐 Start VM when completed: yes 🚀 Creating a Debian 13 VM using the above advanced settings ✔️ Using General for Storage Location. ✔️ Virtual Machine ID is 108. ✔️ https://cloud.debian.org/images/cloud/trixie/latest/debian-13-nocloud-amd64.qcow2 ✔️ Downloaded debian-13-nocloud-amd64.qcow2 Creating a Debian 13 VM 400 Parameter verification failed. bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf' qm create <vmid> [OPTIONS] [ERROR] in line 512: exit code 255: while executing command qm create "$VMID" -agent 1"${MACHINE}" -tablet 0 -localtime 1 -bios ovmf"${CPU_TYPE}" -cores "$CORE_COUNT" -memory "$RAM_SIZE" -name "$HN" -tags community-script -net0 virtio,bridge="$BRG",macaddr="$MAC"$VLAN"$MTU" -onboot 1 -ostype l26 -scsihw virtio-scsi-pci ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:51:57 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Jan 8, 2026):

https://github.com/community-scripts/ProxmoxVE/issues/9040

<!-- gh-comment-id:3723601144 --> @MickLesk commented on GitHub (Jan 8, 2026): https://github.com/community-scripts/ProxmoxVE/issues/9040
Author
Owner

@Mortvert commented on GitHub (Jan 8, 2026):

#9040

Sorry, but this is something entirely different. This is not about the Docker VM script, this is the Debian 13 VM script - it straight up fails if you change CPU type from Q35 to Host.

It does not even create the VM to begin with.

<!-- gh-comment-id:3723689457 --> @Mortvert commented on GitHub (Jan 8, 2026): > [#9040](https://github.com/community-scripts/ProxmoxVE/issues/9040) Sorry, but this is something entirely different. This is not about the Docker VM script, this is the Debian 13 VM script - it straight up fails if you change CPU type from Q35 to Host. It does not even create the VM to begin with.
Author
Owner

@MickLesk commented on GitHub (Jan 8, 2026):

Its an issue with " (shellcheck). should be fixed asap

<!-- gh-comment-id:3723775917 --> @MickLesk commented on GitHub (Jan 8, 2026): Its an issue with " (shellcheck). should be fixed asap
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2296
No description provided.