[SOLVED] File upload?

robert.kuropkat

New Member
Mar 31, 2022
15
2
3
All,

I seem to be missing something basic. I am looking to migrate a VM from ESXI to Proxmox. My assumption was I would export the VM, then upload it to Proxmox and import it through some process there. What I can't seem to find is how to actually upload files? There is a place to upload ISO images, but I don't see the equivalent in Proxmox to ESXI's data storage browser with the ability to upload files. All I see in the documentation after exporting the ESXI VM is to put the resulting OVF file "on storage accessible to the Proxmox server." The local storage IS the storage available. Since those file systems are not mounted when you login to the server via ssh, and I don't see how to upload files for via the UI, I am stumped.

All help appreciated....

Robert Kuropkat
 
PVEs webUI got no file/folder browser to edit/move/upload/delete files/folders. You can only upload ISOs. Simple way to upload files would be by using SSH. For example with WinSCP in case you are using a Windows client to manage your PVE. Using network shares and cp or mv commands from CLI is also a very convenient way to copy stuff to PVE.
 
  • Like
Reactions: ericcl
So just using ssh/scp was my original thought but that is not in the file system space used by the VMs. Are you saying when I do the import command it doesn't matter? I can put it in /home or some-such, import it and it will end up where it needs to be?
 
In the the current release of PVE the "import" option of "qm" is not tied into storage objects. You will need to provide a path to the file. Either absolute or relative will do.

You have two options to import the qcow :
- after vm creation: "qm importdisk $vmid $ISO/$OSIMAGE $STORAGE --format raw"
- during VM creation by using import-from, ie "--scsi0 $STORAGE:0,import-from=$ISO/$OSIMAGE"

Keep in mind the ISO in naming is really a misnomer in this case. The files that you want to import are not ISO but rather qcow or raw.
There is really no special place, at the moment, for qcow/raw files in PVE structure. Keeping them in you template/iso folder probably makes most sense organizationally.

There is also no import function in the GUI, so you are stuck doing that operation from CLI or API.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: ericcl and Dunuin
Okay, so I solved the file transfer problem the easy way, I just saved my VM to a USB drive and walked it over. I created an OVF file using the ESXI GUI. I've started the import of the OVF using this directions (https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE) under the Virtual-to-Virtual (V2V) section for VMWare. I used the command 'qm importovf 102 /media/usb/WWW7ovf/WWW7.ovf local-lvm' The VM has appeared in the Proxmox GUI. However, when I tried to start it I got a kernel panic. It looks like it could not mount the drives. Not sure what I missed...
 
However, when I tried to start it I got a kernel panic. It looks like it could not mount the drives. Not sure what I missed...
thats a different problem and probably different thread. You should mark this one solved if the original issue is resolved.


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