Upload VM disk files to CephFS/RBD? (webGUI)

BloodyIron

Renowned Member
Jan 14, 2013
329
33
93
I'm not entirely seeing how to upload VM Disk images (qcow2/raw/whatever) to a CephFS/RBD storage aspect in a Proxmox VE cluster. Even from a manual/CLI regard I'm not exactly seeing my options here. Can anyone advise?

I have a qcow2 VM disk image file I need to get into this space, and I have a hunch I'll need to convert it to raw (.img? maybe?) format before putting it on there (due to what I have found for info on this mentioning qcow2 is redundant & problematic on CephFS/RBD).

Either way, would appreciate advice on this aspect, thanks! :)
 
I'm not entirely seeing how to upload VM Disk images (qcow2/raw/whatever) to a CephFS/RBD storage aspect in a Proxmox VE cluster. Even from a manual/CLI regard I'm not exactly seeing my options here. Can anyone advise?

I have a qcow2 VM disk image file I need to get into this space, and I have a hunch I'll need to convert it to raw (.img? maybe?) format before putting it on there (due to what I have found for info on this mentioning qcow2 is redundant & problematic on CephFS/RBD).

Either way, would appreciate advice on this aspect, thanks! :)
One way is to import qcow:
qm importdisk $VMID $ISO/$OSIMAGE $STORAGE --format raw


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
One way is to import qcow:
qm importdisk $VMID $ISO/$OSIMAGE $STORAGE --format raw


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Well doesn't that require the image be _on_ a Proxmox VE Node to begin with? I don't have it on any of them yet, and none of the available "Storages" in the cluster support qcow2, so I don't really have a "nice Storage space" to upload it to without getting grubby and uploading it directly to a local dir on a PVE node (ew).
 
I just realized that you were perhaps asking about WebGUI import integration since you mentioned it in the subject.
The qcow import is not wired into GUI today.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Well I was hoping to find a webGUI method first, yes. But failing that, I still need to get this data on the cluster so I'm open to alternative recommendations :)

Also, in this particular case, I have not made a specific VM for this disk to be attached to. This is an "appliance" style qcow2 image from VyOS "for Proxmox" (so to say). So hoping to take this disk image and maybe clone/re-use it in multiple VMs if it ends up being useful for us. So that could influence your responses.

Either way, thanks for your time!
 
Well doesn't that require the image be _on_ a Proxmox VE Node to begin with?
Yes, it also has to be on a file storage pool. Currently, the "disk import" command does not understand storage pools so the path to the file needs to be fully specified. You can spin up a VM, make it an NFS server, and have it serve the images to all nodes in the cluster. You can even back that VM with a Ceph storage pool.
upload it to without getting grubby and uploading it directly to a local dir on a PVE node (ew).
Sometimes you have to do things that you are not fond of. Other options include:
- initiating a feature request in https://bugzilla.proxmox.com (after checking that such a request does not exist already)
- submitting a code patch that enables import functionality in the way that you feel is right
Best


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: BloodyIron
Also, in this particular case, I have not made a specific VM for this disk to be attached to. This is an "appliance" style qcow2 image from VyOS "for Proxmox" (so to say). So hoping to take this disk image and maybe clone/re-use it in multiple VMs if it ends up being useful for us. So that could influence your responses.
You'd create a VM first:
qm create 100
qm importdisk $VMID $ISO/$OSIMAGE $STORAGE --format raw
// plus whatever other commands are needed

The original file is not modified, so you can continue using/re-using/re-importing it as needed. If you plan to clone the VM - make it a template.

There are many approaches, but the minute details are very case-dependent.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: BloodyIron