[SOLVED] Can't change disk image format when cloning VM

Skip

New Member
Dec 14, 2014
3
0
1
I'm not sure if I'm missing something, but I can't change the vdisk format for the destination VM when cloning. It defaults to raw and is a disabled drop-down.

This wouldn't be that big a deal to me, but it seems that raw disks can't use the snapshot feature.

What am I doing wrong?

Thanks,
-Skip

Proxmox ver: 3.3-5
 
Last edited:
I'm not sure if I'm missing something, but I can't change the vdisk format for the destination VM when cloning. It defaults to raw and is a disabled drop-down.

this could happen if the destination storage can't host files directly (like lvm), so raw is the only possible choice. if you can choose a destination storage like nfs, the format list should be selectable.

Marco
 
this could happen if the destination storage can't host files directly (like lvm), so raw is the only possible choice. if you can choose a destination storage like nfs, the format list should be selectable.

Marco

Thanks for the reply Marco.

I don't understand by "destination storage can't host files directly" ... this is the local storage, which is LVM, so maybe that's the issue, but I still don't understand that statement. I can choose any disk format when creating the VM initially on LVM, so I would expect I could choose any format as the destination.

Mind clarifying?

-Skip
 
I don't understand by "destination storage can't host files directly" ... this is the local storage, which is LVM, so maybe that's the issue, but I still don't understand that statement. I can choose any disk format when creating the VM initially on LVM, so I would expect I could choose any format as the destination.

well when you do a full clone, which I assume you're doing, selecting "local" target storage, the list is enabled and all formats available. the same usgin a nfs target storage. selecting a lvm storage, the list greys out and raw is mandatory. that's because lvm is not a file system, so it cannot host files like .qcow2 or .vmdk.

if you "local" storage is lvm, maybe that is the problem..? my local storage is defined as folder

see
http://pve.proxmox.com/wiki/Storage_Model

Marco
 
well when you do a full clone, which I assume you're doing, selecting "local" target storage, the list is enabled and all formats available. the same usgin a nfs target storage. selecting a lvm storage, the list greys out and raw is mandatory. that's because lvm is not a file system, so it cannot host files like .qcow2 or .vmdk.

if you "local" storage is lvm, maybe that is the problem..? my local storage is defined as folder

see
http://pve.proxmox.com/wiki/Storage_Model

Marco

Thanks!

When first looking into this I noticed that I was on version 3.1 and not the latest because I was using an out-dated repo. After the upgrade, I didn't go as far to actually select the target. I incorrectly assumed that the format would start available.

So... While I have no way to verify that it was the upgrade, that's what I think fixed the issue, and I'd never stepped through far enough to notice.

Of coarse the other possible answer is that I messed up the original clones I'd done in some way to make that option also not available.

Either way, thanks for the help, it looks like I can change the format! :)

-Skip
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!