starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Debian 12 VM Install Error #789

New Issue
Closed
opened 2026-02-04 21:32:45 +03:00 by OVERLORD · 22 comments
OVERLORD commented 2026-02-04 21:32:45 +03:00
Owner
Copy Link

Originally created by @alloylab on GitHub (Apr 9, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Debian 12 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-vm.sh)"

📝 Provide a clear and concise description of the issue.

Install script fails with Proxmox 8.4

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Run Install Script
  2. Select Default Settings
  3. Error:
    Creating a Debian 12 VM curl: (22) The requested URL returned error: 400

[ERROR] in line 459: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null

  1. Run Install Script
  2. Select Advanced Settings
  3. Error:
    Creating a Debian 12 VM 400 Parameter verification failed.
    bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf'
    qm create [OPTIONS]
    curl: (22) The requested URL returned error: 400

[ERROR] in line 456: 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

❌ Paste the full error output (if available).

Full Output for Advanced Settings:

🧩 Using Advanced Settings
🆔 Virtual Machine ID: 151
📦 Machine Type: i440fx
💾 Disk Size: 256G
💾 Disk Cache: None
🏠 Hostname: vm1
🖥️ CPU Model: Host
🧠 CPU Cores: 8
🛠️ RAM Size: 65536
🌉 Bridge: vmbr0
🔗 MAC Address: *
🏷️ VLAN: Default
⚙️ Interface MTU Size: Default
🌐 Start VM when completed: yes
🚀 Creating a Debian 12 VM using the above advanced settings
✔️ Using vm-disks for Storage Location.
✔️ Virtual Machine ID is 151.
✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2
####################################################################################################################################################### 100.0%
✔️ Downloaded debian-12-nocloud-amd64.qcow2
Creating a Debian 12 VM 400 Parameter verification failed.
bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf'
qm create [OPTIONS]
curl: (22) The requested URL returned error: 400

[ERROR] in line 456: 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 @alloylab on GitHub (Apr 9, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Debian 12 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-vm.sh)" ### 📝 Provide a clear and concise description of the issue. Install script fails with Proxmox 8.4 ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Run Install Script 2. Select Default Settings 3. Error: Creating a Debian 12 VM curl: (22) The requested URL returned error: 400 [ERROR] in line 459: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null 1. Run Install Script 2. Select Advanced Settings 3. Error: Creating a Debian 12 VM 400 Parameter verification failed. bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf' qm create <vmid> [OPTIONS] curl: (22) The requested URL returned error: 400 [ERROR] in line 456: 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 ### ❌ Paste the full error output (if available). Full Output for Advanced Settings: 🧩 Using Advanced Settings 🆔 Virtual Machine ID: 151 📦 Machine Type: i440fx 💾 Disk Size: 256G 💾 Disk Cache: None 🏠 Hostname: vm1 🖥️ CPU Model: Host 🧠 CPU Cores: 8 🛠️ RAM Size: 65536 🌉 Bridge: vmbr0 🔗 MAC Address: * 🏷️ VLAN: Default ⚙️ Interface MTU Size: Default 🌐 Start VM when completed: yes 🚀 Creating a Debian 12 VM using the above advanced settings ✔️ Using vm-disks for Storage Location. ✔️ Virtual Machine ID is 151. ✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2 ####################################################################################################################################################### 100.0% ✔️ Downloaded debian-12-nocloud-amd64.qcow2 Creating a Debian 12 VM 400 Parameter verification failed. bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf' qm create <vmid> [OPTIONS] curl: (22) The requested URL returned error: 400 [ERROR] in line 456: 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_
OVERLORD added the bug label 2026-02-04 21:32:45 +03:00
OVERLORD commented 2026-02-04 21:32:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

And in Default settings? My Installation just now worked

@MickLesk commented on GitHub (Apr 9, 2025): And in Default settings? My Installation just now worked
OVERLORD commented 2026-02-04 21:33:04 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

just tried again with Default settings, and still getting
Creating a Debian 12 VM curl: (22) The requested URL returned error: 400

[ERROR] in line 459: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null

@alloylab commented on GitHub (Apr 9, 2025): just tried again with Default settings, and still getting Creating a Debian 12 VM curl: (22) The requested URL returned error: 400 [ERROR] in line 459: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null
OVERLORD commented 2026-02-04 21:33:09 +03:00
Author
Owner
Copy Link

@fabiocatalao commented on GitHub (Apr 9, 2025):

The same is happening here. I'm trying to install a Docker VM and it's failing with the same erorr.
[ERROR] in line 457: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null
Tried with different VMs and the same issue is happening.
Running on VE 8.4.0

@fabiocatalao commented on GitHub (Apr 9, 2025): The same is happening here. I'm trying to install a Docker VM and it's failing with the same erorr. `[ERROR] in line 457: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null` Tried with different VMs and the same issue is happening. Running on VE 8.4.0
OVERLORD commented 2026-02-04 21:33:16 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

I found the issue... its with the double quotes that were committed this morning on lines 456-462,

the following forked script worked for me when I removed the double quotes,
https://raw.githubusercontent.com/alloylab/ProxmoxVE/refs/heads/main/vm/debian-vm.sh

I have confirmed that removing the quotes fixes both the default and advanced settings issues in my original post

@alloylab commented on GitHub (Apr 9, 2025): I found the issue... its with the double quotes that were committed this morning on lines 456-462, the following forked script worked for me when I removed the double quotes, https://raw.githubusercontent.com/alloylab/ProxmoxVE/refs/heads/main/vm/debian-vm.sh I have confirmed that removing the quotes fixes both the default and advanced settings issues in my original post
OVERLORD commented 2026-02-04 21:33:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

strange, ok will be fixed in next 1h

@MickLesk commented on GitHub (Apr 9, 2025): strange, ok will be fixed in next 1h
OVERLORD commented 2026-02-04 21:33:22 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

@MickLesk what version of proxmox & OS are you running?
I am currently running 8.4 installed from the Promox ISO... details below...

Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.8.12-9-pve
Architecture: x86-64

I can only assume if works for you but not me or @fabiocatalao ... must be a difference in Proxmox version or OS

@alloylab commented on GitHub (Apr 9, 2025): @MickLesk what version of proxmox & OS are you running? I am currently running 8.4 installed from the Promox ISO... details below... Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.8.12-9-pve Architecture: x86-64 I can only assume if works for you but not me or @fabiocatalao ... must be a difference in Proxmox version or OS
OVERLORD commented 2026-02-04 21:33:31 +03:00
Author
Owner
Copy Link

@ziggornif commented on GitHub (Apr 9, 2025):

I have the same issue with Home Assistant OS VM script on my Proxmox 8.4

Debian GNU/Linux 12 (bookworm)
Kernel : Linux 6.8.12-9-pve
Architecture: x86-64

Installation logs :

Using Default Settings
Using HAOS Version: 15.1
Using Virtual Machine ID: 101
Using Machine Type: i440fx
Using Disk Cache: Write Through
Using Hostname: haos15.1
Using CPU Model: Host
Allocated Cores: 2
Allocated RAM: 4096
Using Bridge: vmbr0
Using MAC Address: *
Using VLAN: Default
Using Interface MTU Size: Default
Start VM when completed: yes
Creating a HAOS VM using the above default settings
 ✓ Using local-lvm for Storage Location.
 ✓ Virtual Machine ID is 101.
 ✓ https://os-artifacts.home-assistant.io/15.1/haos_ova-15.1.qcow2.xz
############################################################################################################################################################################################################################## 100.0%
 ✓ Downloaded haos_ova-15.1.qcow2.xz
 ✓ Extracted KVM Disk Image
 /400 Parameter verification failed.
bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf'
qm create <vmid> [OPTIONS]
curl: (22) The requested URL returned error: 400

[ERROR] in line 464: exit code 0: 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
@ziggornif commented on GitHub (Apr 9, 2025): I have the same issue with Home Assistant OS VM script on my Proxmox 8.4 Debian GNU/Linux 12 (bookworm) Kernel : Linux 6.8.12-9-pve Architecture: x86-64 Installation logs : ```sh Using Default Settings Using HAOS Version: 15.1 Using Virtual Machine ID: 101 Using Machine Type: i440fx Using Disk Cache: Write Through Using Hostname: haos15.1 Using CPU Model: Host Allocated Cores: 2 Allocated RAM: 4096 Using Bridge: vmbr0 Using MAC Address: * Using VLAN: Default Using Interface MTU Size: Default Start VM when completed: yes Creating a HAOS VM using the above default settings ✓ Using local-lvm for Storage Location. ✓ Virtual Machine ID is 101. ✓ https://os-artifacts.home-assistant.io/15.1/haos_ova-15.1.qcow2.xz ############################################################################################################################################################################################################################## 100.0% ✓ Downloaded haos_ova-15.1.qcow2.xz ✓ Extracted KVM Disk Image /400 Parameter verification failed. bios: value 'ovmf -cpu host' does not have a value in the enumeration 'seabios, ovmf' qm create <vmid> [OPTIONS] curl: (22) The requested URL returned error: 400 [ERROR] in line 464: exit code 0: 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 ```
OVERLORD commented 2026-02-04 21:33:33 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

can you try again in 5min?

@MickLesk commented on GitHub (Apr 9, 2025): can you try again in 5min?
OVERLORD commented 2026-02-04 21:33:37 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

following scripts works with default & advanced settings bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh)"

@alloylab commented on GitHub (Apr 9, 2025): following scripts works with default & advanced settings bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh)"
OVERLORD commented 2026-02-04 21:33:40 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

now all fixed, strange that pve 8.4 that doesnt support.

@MickLesk commented on GitHub (Apr 9, 2025): now all fixed, strange that pve 8.4 that doesnt support.
OVERLORD commented 2026-02-04 21:33:43 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

thanks for getting it fixed

@alloylab commented on GitHub (Apr 9, 2025): thanks for getting it fixed
OVERLORD commented 2026-02-04 21:33:47 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

@MickLesk it just stopped working again, https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh issue with PVE version check, if ! pveversion | grep -Eq "pve-manager/8.1-3*"; then

you maybe making other changes... just wanted to make you aware

@alloylab commented on GitHub (Apr 9, 2025): @MickLesk it just stopped working again, https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh issue with PVE version check, if ! pveversion | grep -Eq "pve-manager/8\.[1-3](\.[0-9]+)*"; then you maybe making other changes... just wanted to make you aware
OVERLORD commented 2026-02-04 21:33:57 +03:00
Author
Owner
Copy Link

@herobrauni commented on GitHub (Apr 9, 2025):

Still not working here

[ERROR] in line 458: exit code 1: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null

Proxmox 8.3.5 + ZFS

@herobrauni commented on GitHub (Apr 9, 2025): Still not working here [ERROR] in line 458: exit code 1: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null Proxmox 8.3.5 + ZFS
OVERLORD commented 2026-02-04 21:34:01 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

y

@MickLesk it just stopped working again, https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh issue with PVE version check, if ! pveversion | grep -Eq "pve-manager/8.1-3*"; then

you maybe making other changes... just wanted to make you aware

give me 10min, github failed my pushs (500) - very slow today and break sometimes

@MickLesk commented on GitHub (Apr 9, 2025): y > [@MickLesk](https://github.com/MickLesk) it just stopped working again, https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/debian-vm.sh issue with PVE version check, if ! pveversion | grep -Eq "pve-manager/8.[1-3](.%5B0-9%5D+)*"; then > > you maybe making other changes... just wanted to make you aware give me 10min, github failed my pushs (500) - very slow today and break sometimes
OVERLORD commented 2026-02-04 21:34:04 +03:00
Author
Owner
Copy Link

@herobrauni commented on GitHub (Apr 9, 2025):

Apparently the bugged version created a zfs volume with the ID of the new vm
after failing the VM gets deleted but the volume remains, messing with the next installations (which try to use the same ID)
removing the zfs volume fixed my issue and the newest version of the script works with default settings for me.

@herobrauni commented on GitHub (Apr 9, 2025): Apparently the bugged version created a zfs volume with the ID of the new vm after failing the VM gets deleted but the volume remains, messing with the next installations (which try to use the same ID) removing the zfs volume fixed my issue and the newest version of the script works with default settings for me.
OVERLORD commented 2026-02-04 21:34:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

and all other scripts should be work now fine. Github finally accepted my push and didn't throw something together with bad requests

@MickLesk commented on GitHub (Apr 9, 2025): and all other scripts should be work now fine. Github finally accepted my push and didn't throw something together with bad requests
OVERLORD commented 2026-02-04 21:34:15 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

Curiously, the pveam alloc no longer works with 8.4

My turn....

@MickLesk commented on GitHub (Apr 9, 2025): Curiously, the pveam alloc no longer works with 8.4 My turn....
OVERLORD commented 2026-02-04 21:34:22 +03:00
Author
Owner
Copy Link

@alloylab commented on GitHub (Apr 9, 2025):

all of the double quotes are back...

@alloylab commented on GitHub (Apr 9, 2025): all of the double quotes are back...
OVERLORD commented 2026-02-04 21:34:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 9, 2025):

I've never felt so screwed by Github as I do today. I have reverted and pushed all the commits and it keeps pushing old values.

Have a look here, should actually be correct everywhere now... 30fbcb5ba8

look better:

Image

@MickLesk commented on GitHub (Apr 9, 2025): I've never felt so screwed by Github as I do today. I have reverted and pushed all the commits and it keeps pushing old values. Have a look here, should actually be correct everywhere now... https://github.com/community-scripts/ProxmoxVE/commit/30fbcb5ba8c413b2662b5f61af25338903c1d780 look better: ![Image](https://github.com/user-attachments/assets/ff934bbc-8c6e-4d22-88a2-19319e622e9d)
OVERLORD commented 2026-02-04 21:34:39 +03:00
Author
Owner
Copy Link

@ziggornif commented on GitHub (Apr 9, 2025):

Install OK with haos-vm script, thanks @MickLesk !

@ziggornif commented on GitHub (Apr 9, 2025): Install OK with haos-vm script, thanks @MickLesk !
OVERLORD commented 2026-02-04 21:34:42 +03:00
Author
Owner
Copy Link

@scuffedjosh commented on GitHub (Jun 18, 2025):

This is happening again. Default settings. Tried both Debian 12 and Ubuntu 24.10 VMs. Running 8.4.1

@scuffedjosh commented on GitHub (Jun 18, 2025): This is happening again. Default settings. Tried both Debian 12 and Ubuntu 24.10 VMs. Running 8.4.1
OVERLORD commented 2026-02-04 21:34:49 +03:00
Author
Owner
Copy Link

@lyneld commented on GitHub (Jan 7, 2026):

I have this issue with both the Debian 12 and Debian 13 VMs. Both the default settings and advanced settings throw the same error. Specifically:

[ERROR] in line 515: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null

Just tried the Docker VM to see if that works, and it ran fine.

@lyneld commented on GitHub (Jan 7, 2026): I have this issue with both the Debian 12 and Debian 13 VMs. Both the default settings and advanced settings throw the same error. Specifically: `[ERROR] in line 515: exit code 255: while executing command qm importdisk "$VMID" "${FILE}" "$STORAGE" "${DISK_IMPORT:-}" >&/dev/null` Just tried the Docker VM to see if that works, and it ran fine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#789
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?