Proxmox: Unable to parse lvm volume name

gjacobse

Been following the guidance of a previous thread here on how to import a .VMDK file into Proxmox as a .qcow2 file and have run into this error.

Import was successful, folder and file are correct - as near as I can tell.

mkdir /mnt/usb
mount /dev/sdc1 /mnt/usb
mkdir 100

qemu-img convert -f vmdk /mnt/usb/DietPi_VMware-x86_64-Buster/DietPi_VMware-x86_64-Buster.vmdk -O qcow2 /var/lib/vz/images/100/DietPi_VMware.qcow2

nano /etc/pve/local/qemu-server/100.conf

boot: order=ide0;ide2;net0
cores: 1
ide0: local-lvm:DietPi_VMware.qcow2
ide2: cdrom,media=cdrom
memory: 1024
name: dPi-ubnt
net0: virtio=1A:E8:3D:C6:20:4D,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=d64891b9-9df2-4411-907a-69e632d0e2d9
sockets: 1
unused0: local-lvm:vm-100-disk-0
vmgenid: b85b3fb6-47aa-4bbb-8986-8b8d68b5ced8

qm rescan

Unrelated - looks like I can easily remove ide2:

this was less than helpful:
https://forum.proxmox.com/threads/unable-to-parse-directory-volume-name.8068/

I have indeed read:
Import a qcow2 by SAM

killmasta93

@gjacobse

why dont you just import it directly?

qm importdisk 100 DietPi_VMware-x86_64-Buster.vmdk zfs-vmdata

this case im running ZFS just change the zfs-vmdata to your lvm location

gjacobse

@killmasta93 said in Proxmox: Unable to parse lvm volume name:

@gjacobse

why dont you just import it directly?
qm importdisk 100 DietPi_VMware-x86_64-Buster.vmdk zfs-vmdata
this case im running ZFS just change the zfs-vmdata to your lvm location

I will give that a look, and it follows what I received from Proxmox Staff. Interestingly enough, it was said that qcow2 isnt supported and I should use qm importdisk and references a WIKI page. Funny thing is, that's exactly the page I followed getting to my starting point.

JaredBusch

@gjacobse said in Proxmox: Unable to parse lvm volume name:

@killmasta93 said in Proxmox: Unable to parse lvm volume name:
@gjacobse

why dont you just import it directly?
qm importdisk 100 DietPi_VMware-x86_64-Buster.vmdk zfs-vmdata
this case im running ZFS just change the zfs-vmdata to your lvm location
I will give that a look, and it follows what I received from Proxmox Staff. Interestingly enough, it was said that qcow2 isnt supported and I should use qm importdisk and references a WIKI page. Funny thing is, that's exactly the page I followed getting to my starting point.

I have no idea wtf you followed, but the article we have posted here, and that you linked...., is not what you did.

gjacobse

@jaredbusch said in Proxmox: Unable to parse lvm volume name:

@gjacobse said in Proxmox: Unable to parse lvm volume name:
@killmasta93 said in Proxmox: Unable to parse lvm volume name:
@gjacobse

why dont you just import it directly?
qm importdisk 100 DietPi_VMware-x86_64-Buster.vmdk zfs-vmdata
this case im running ZFS just change the zfs-vmdata to your lvm location
I will give that a look, and it follows what I received from Proxmox Staff. Interestingly enough, it was said that qcow2 isnt supported and I should use qm importdisk and references a WIKI page. Funny thing is, that's exactly the page I followed getting to my starting point.
I have no idea wtf you followed, but the article we have posted here, and that you linked...., is not what you did.

@JaredBusch I don't know why you have to be such an ass . I read this and I quote

Move the image to the Proxmox VE Server
Plug a USB Hard Drive into the server

From the Proxmox VE command line:

mkdir /mnt/usb
mount /dev/sdc1 /mnt/usb/
ls /mnt/usb
You should see the contents of the USB drive. In my case, the vmdk file was located in /mnt/usb/windows-server/

Converting to qcow2
We want to convert the .vmdk image file to qcow2. To do this, use the following command:

qemu-img convert -f vmdk /mnt/usb/windows-server/windows-server.vmdk -O qcow2 /var/lib/vz/images/100/windows-server.qcow2
This can take a while depending on the size of file and speed of your system.

Final Steps
Once the conversion is complete, we need to edit the configuration file for the VM.

nano /etc/pve/local/qemu-server/100.conf
In the line with ide0: we want to change vm-100-disk-1.raw,size=32G to windows-server.qcow2

You may delete the empty disk created by Proxmox VE when you created the VM.

rm /var/lib/vz/images/100/vm-100-disk-1.raw
Start the VM and open the console. Windows should boot up normally. It’ll take a few minutes to detect the hardware changes. If the Windows system had a static IP address, you'll have to reconfigure the settings.

That is directly from the WIKI - Their Own WIKI - Did I follow the wrong section - maybe. But I will learn nothing from you responding in the manner you do. I have seriously long gotten to the point that I hate coming here to ask a question to learn something because of the CONTIUNUED BELITTLING and BERATING.

Your attitude is absolute shit when it comes to my asking and attempting to learn.

Now - if you want to constructively contribute, you can point a directly in a kind manner. This Forum is suppose to be Supportive. It's not a football game with losers and winners.

JaredBusch

@gjacobse said in Proxmox: Unable to parse lvm volume name:

I have indeed read:
Import a qcow2 by SAM

Read, did not follow.

Unsolved Proxmox: Unable to parse lvm volume name