Unable to parse volume ID

J

jicheng81

New Member
Apr 1, 2024
1
0
1
Hi,

I am encountering an error when trying to import a qcow2 to my newly created VM. The VM storage is in a network folder. Appreciate if anyone can point out things that I overlook.

Code: 
Error message:
root@pve2:~# qm import 160 /var/lib/vz/template/qcow/haos_generic-aarch64-13.1.qcow2 --storage pve1-nfs
unable to parse volume ID '/var/lib/vz/template/qcow/haos_generic-aarch64-13.1.qcow2'

root@pve2:~# lsblk
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1                      259:0    0 119.2G  0 disk
├─nvme0n1p1                  259:1    0  1007K  0 part
├─nvme0n1p2                  259:2    0     1G  0 part /boot/efi
└─nvme0n1p3                  259:3    0 118.2G  0 part
  ├─pve-swap                 252:0    0     8G  0 lvm  [SWAP]
  ├─pve-root                 252:1    0  39.6G  0 lvm  /
  ├─pve-data_tmeta           252:2    0     1G  0 lvm
  │ └─pve-data-tpool         252:4    0  53.9G  0 lvm
  │   ├─pve-data             252:5    0  53.9G  1 lvm
  │   ├─pve-vm--150--disk--0 252:6    0     4M  0 lvm
  │   ├─pve-vm--150--disk--1 252:7    0    32G  0 lvm
  │   ├─pve-vm--150--disk--2 252:8    0     4M  0 lvm
  │   └─pve-vm--157--disk--0 252:9    0   350G  0 lvm
  └─pve-data_tdata           252:3    0  53.9G  0 lvm
    └─pve-data-tpool         252:4    0  53.9G  0 lvm
      ├─pve-data             252:5    0  53.9G  1 lvm
      ├─pve-vm--150--disk--0 252:6    0     4M  0 lvm
      ├─pve-vm--150--disk--1 252:7    0    32G  0 lvm
      ├─pve-vm--150--disk--2 252:8    0     4M  0 lvm
      └─pve-vm--157--disk--0 252:9    0   350G  0 lvm

root@pve2:~# df
Filesystem                    1K-blocks      Used Available Use% Mounted on
udev                           16269256         0  16269256   0% /dev
tmpfs                           3260620      1732   3258888   1% /run
/dev/mapper/pve-root           40516856  16876932  21549532  44% /
tmpfs                          16303084     49920  16253164   1% /dev/shm
tmpfs                              5120         0      5120   0% /run/lock
efivarfs                            192        85       103  46% /sys/firmware/efi/efivars
/dev/nvme0n1p2                  1046512     11924   1034588   2% /boot/efi
192.168.68.200:/mnt/pve1sata1 960303104 173369344 738079744  20% /mnt/nfs_share_for_vm
/dev/fuse                        131072        20    131052   1% /etc/pve
tmpfs                           3260616         0   3260616   0% /run/user/0

root@pve2:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,backup,vztmpl

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

dir: pve1-nfs
        path /mnt/nfs_share_for_vm
        content images,iso
        prune-backups keep-all=1
        shared 0

root@pve2:~# cat /etc/pve/qemu-server/160.conf
bios: ovmf
boot: order=ide2;net0
cores: 2
cpu: x86-64-v2-AES
ide2: none,media=cdrom
memory: 4096
meta: creation-qemu=9.0.0,ctime=1725206093
name: kullinapp160-HomeAssistant-DND
net0: virtio=BC:24:11:D3:F3:8F,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=1bc7466f-6d67-4a37-b031-33452d146272
sockets: 1
vmgenid: 37dbc9e6-5751-4f06-ab98-d065bbf6d59d
 
You are looking for "qm disk import" not "qm import"

Code: 
qm import <vmid> <source> --storage <string> [OPTIONS]

       Import a foreign virtual guest from a supported import source, such as an ESXi storage.

Code: 
qm disk import <vmid> <source> <storage> [OPTIONS]

       Import an external disk image as an unused disk in a VM. The image format has to be supported by qemu-img(1).

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
I think I just hosed my disk file as I saw a command start trying to format my disk image apparently after mounting it.

qm disk import 201 vm-201-disk-0.qcow xfs_dir
vm-201-disk-0.qcow: non-existent or non-regular file

But then the file mod time has not changed
1.5T Jan 11 18:59 vm-201-disk-0.qcow2
It is an directory based disk image.
 
@tomachi , while we can try to infer that you are asking for help, technically your post reads as a statement. There is no reference as to what you are trying to do and why.

Where is your image located (pwd; ls -al vm-201-disk-0.qcow2) ? Is it valid image (qemu-img info vm-201-disk-0.qcow2) ? Why not just move the file into appropriate folder since your storage pool is directory?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom