03-29-2024-ProxMox-QCOW2-Image-Location-Issue-Resolved
1 Attachment(s)
Hope this helps someone trying to attach/import a .qcow2 image into ProxMox ...:
03-29-2024-ProxMox-QCOW2-Image-Location-Issue-Resolved.txt ...: Regarding Gerard's great ProxMox Tutorial ( part 2 ).... Building the Ultimate Cybersecurity Lab - Episode 2 https://www.youtube.com/watch?v=Gm_olWLLCqo&t=8s Hey Guys, in reference to the tutorial above for the Cybersecuirty lab setup, I got hung up on the Metasploitable.qcow2 file implementation in ProxMox. In Short I had to wrap my head around ProxMox's Storage types of where and how images are stored ( i.e. File Based or Device Based ). The Table 1 Diagram in the link below shows the distinc Storage types. The two main Storage Types for the storage.cfg file were dir and lvm/lvm-thin. I kept trying to get the Metalsploitable.qcow2 file to work on the device type storage lvm and lvm-thin, until I finally realized I couldn't get the import command to work. So I pursued the file storage type option ( because as table-1 explains it is an actual file to be stored as the image ). Although I pasted Fix 1 and Fix 2 below, what was really only needed was to insert 'images' in the content type for dir: local and it worked!!! Location of the actual file Meta*.qcow2 was the following path ... { /var/lib/vz/images/204 } https://pve.proxmox.com/pve-docs/chapter-pvesm.html ============================================= File Based ...: Fix:1... /etc/pve/storage.cfg dir: local path /var/lib/vz content images,vztmpl,iso,backup *** LVM and LVM-THIN section removed for brevity in the storage.cfg file. *** Fix:2... ide0: file=local:204/Metasploitable.qcow2,size=32G *** Again this is mentioned in the video already, but wanted to show both sides /etc/pve/storage.cfg and my actual VM's config file /etc/pve/qemu-server/204.conf Device Based ...: Tried this link below of importing .qcow2 guide images into ProxMox *** But couldn't get it to work?? *** https://ostechnix.com/import-qcow2-into-proxmox/ ========================================== Location of this File to Edit that will Fix the .qcow2 Image-Location-Issue ...: /etc/pve/storage.cfg dir: local path /var/lib/vz content images,vztmpl,iso,backup lvmthin: local-lvm thinpool data vgname pve content images,rootdir lvm: MyExtra-500gb vgname MyExtra-500gb content images,rootdir nodes pve shared 0 ========================================= Location of this file to Edit that will also Fix the .qcow2 Image-Location_issue... : *** Same as Gerard's Video, but showing for emphasis and completion of .qcow2 implementation of the Metasploit.qcow2 file. *** /etc/pve/qemu-server/204.conf boot: order=ide0;ide2;net0 cores: 1 cpu: x86-64-v2-AES ide0: file=local:204/Metasploitable.qcow2,size=32G ide1: local-lvm:vm-204-disk-1,size=8G ide2: none,media=cdrom ide3: MyExtra-500gb:vm-204-disk-0,size=8G memory: 2048 meta: creation-qemu=8.1.5,ctime=1711496195 name: prod-metasploit2 net0: virtio=BC:24:11:F3:AC:B7,bridge=vmbr2,firewall=1,tag=10 numa: 0 ostype: l26 scsihw: virtio-scsi-single smbios1: uuid=6fcdbe6b-c32e-4195-b03a-2c374d2b81e6 sockets: 1 vmgenid: 4f1ea3db-78c7-4f99-8d5f-478d1aa4395b |
All times are GMT -5. The time now is 01:10 PM. |