volume_size_info error when setting up vms

SpiderUnderUrBed

New Member
Feb 17, 2025
4
0
1
Code:
proxmoxer.core.ResourceException: 500 Internal Server Error: volume_size_info on 'local:iso/fg6h0pjs26025yxhr0zv9rxw2dwyabga-latest-nixos-minimal-x86_64-linux.iso' failed

^ error

Code:
[spiderunderurbed@daspidercave:~/nixnuc/nixmoxer]$ du -h latest-nixos-minimal-x86_64-linux.iso
1.2G    latest-nixos-minimal-x86_64-linux.iso

^ size of my ISO

Code:
[spiderunderurbed@intelnuc:~]$ df -h /
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           7.8G  1.5G  6.3G  20% /

^ space

The reason I show the size of my iso and root space is because I think it could be related. Also, I am configuring this with nixos-proxmox, however the nix module is not the cause of the error as the error is from proxmoxer core. here is the configuration, pretty easy to read, might give some insight:

Code:
{ config, lib, pkgs, ... }:

{
  networking.hostName = "myvm";

  virtualisation.proxmox = {
    node = "intelnuc";
    autoInstall = lib.mkForce true;
#    iso = pkgs.runCommand "nixos-minimal.iso" {
#      src = ../latest-nixos-minimal-x86_64-linux.iso;
#    } ''
#      mkdir -p $out
#      mkdir $out/iso
#      cp $src $out/iso/
#    '';

    vmid = 100;
    memory = 12288;
    cores = 3;
    sockets = 1;
    boot.order = [ "disk" ];
    scsi = [
      { file = "/home/spiderunderurbed/hdds/vms/vm-1/result/nixos.qcow2"; size = "20G"; }
    ];
  };

  services.openssh.enable = true;
  time.timeZone = "UTC";

  #  Fix conflicting image.baseName
#  image.baseName = lib.mkForce "nixos-custom";
}

There is no more information I think I can give. If anything else is needed I will share it. The iso mentioned is in the error log.
 
Hi,
Code:
proxmoxer.core.ResourceException: 500 Internal Server Error: volume_size_info on 'local:iso/fg6h0pjs26025yxhr0zv9rxw2dwyabga-latest-nixos-minimal-x86_64-linux.iso' failed
looks like the volume ID is corrupted? The path you checked manually does not have the fg6h0pjs26025yxhr0zv9rxw2dwyabga- prefix. Please provide the API calls and parameters that lead to the failure, i.e. try to capture what calls your API client issues.