SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

OpenWRT vm fails to install on pve9 #2056

New Issue
Closed
opened 2025-11-20 05:22:36 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:22:36 -05:00
Owner
Copy Link

Originally created by @sgmihai on GitHub (Oct 10, 2025).

✅ Have you read and understood the above guidelines?

yes

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

OpenWRT

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/openwrt-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?

9.0.10

📝 Provide a clear and concise description of the issue.

Fails to install, wtih default settings or avanced.

🔄 Steps to reproduce the issue.

just run the provided install script line

❌ Paste the full error output (if available).

ted OpenWrt Disk Image openwrt-24.10.3-x86-64-generic-ext4-combined.img
Creating OpenWrt VM...unable to parse volume filename 'vm-100-disk-0'

[ERROR] in line 536: exit code 25: while executing command pvesm alloc "$STORAGE" "$VMID" "vm-$VMID-disk-0" 4M > /dev/null

🖼️ Additional context (optional).

No response

Originally created by @sgmihai on GitHub (Oct 10, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? OpenWRT ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/openwrt-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.10 ### 📝 Provide a clear and concise description of the issue. Fails to install, wtih default settings or avanced. ### 🔄 Steps to reproduce the issue. just run the provided install script line ### ❌ Paste the full error output (if available). ted OpenWrt Disk Image openwrt-24.10.3-x86-64-generic-ext4-combined.img Creating OpenWrt VM...unable to parse volume filename 'vm-100-disk-0' [ERROR] in line 536: exit code 25: while executing command pvesm alloc "$STORAGE" "$VMID" "vm-$VMID-disk-0" 4M > /dev/null ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:22:36 -05:00
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@sgmihai commented on GitHub (Oct 10, 2025):

Claude found the problem:

The script checks if the storage type is "dir" (directory-based), but in Proxmox 9, the logic for handling storage allocation has changed slightly. The pvesm alloc command with the filename format vm-$VMID-disk-0 is failing because Proxmox 9 is stricter about volume naming conventions.

# OLD CODE (lines 534-537):
if [[ "$(pvesm status | awk -v s=$STORAGE '$1==s {print $2}')" == "dir" ]]; then
  qm set "$VMID" -efidisk0 "${STORAGE}:0,efitype=4m,size=4M"
else
  pvesm alloc "$STORAGE" "$VMID" "vm-$VMID-disk-0" 4M >/dev/null
  qm set "$VMID" -efidisk0 "${STORAGE}:vm-$VMID-disk-0,efitype=4m,size=4M"
fi

replace with:

# NEW CODE - Let qm handle the disk allocation:
qm set "$VMID" -efidisk0 "${STORAGE}:4,efitype=4m,pre-enrolled-keys=0"

This might break pve8

@sgmihai commented on GitHub (Oct 10, 2025): Claude found the problem: `The script checks if the storage type is "dir" (directory-based), but in Proxmox 9, the logic for handling storage allocation has changed slightly. The pvesm alloc command with the filename format vm-$VMID-disk-0 is failing because Proxmox 9 is stricter about volume naming conventions.` ```bash # OLD CODE (lines 534-537): if [[ "$(pvesm status | awk -v s=$STORAGE '$1==s {print $2}')" == "dir" ]]; then qm set "$VMID" -efidisk0 "${STORAGE}:0,efitype=4m,size=4M" else pvesm alloc "$STORAGE" "$VMID" "vm-$VMID-disk-0" 4M >/dev/null qm set "$VMID" -efidisk0 "${STORAGE}:vm-$VMID-disk-0,efitype=4m,size=4M" fi ``` replace with: ```bash # NEW CODE - Let qm handle the disk allocation: qm set "$VMID" -efidisk0 "${STORAGE}:4,efitype=4m,pre-enrolled-keys=0" ``` This might break pve8
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 10, 2025):

You can Run the Script again or choose another storage

You have not posted which storage you take

@MickLesk commented on GitHub (Oct 10, 2025): You can Run the Script again or choose another storage You have not posted which storage you take
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@sgmihai commented on GitHub (Oct 10, 2025):

Why run the script again ? nothing changed.
I ran the claude fixed one and it works.
I have local-btrfs storage.

@sgmihai commented on GitHub (Oct 10, 2025): Why run the script again ? nothing changed. I ran the claude fixed one and it works. I have local-btrfs storage.
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 10, 2025):

Then do an PR. At all my systems it Work. With dir, without dir. AI is Not the Solution for all....

@MickLesk commented on GitHub (Oct 10, 2025): Then do an PR. At all my systems it Work. With dir, without dir. AI is Not the Solution for all....
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@sgmihai commented on GitHub (Oct 10, 2025):

You tried to run the script now on a proxmox 9 install ?

@sgmihai commented on GitHub (Oct 10, 2025): You tried to run the script now on a proxmox 9 install ?
saavagebueno commented 2025-11-20 05:22:38 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 10, 2025):

Yep, Work since weeks. Local. LVM, Dir, ZFS

@MickLesk commented on GitHub (Oct 10, 2025): Yep, Work since weeks. Local. LVM, Dir, ZFS
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2056
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?