where are the vm files?

[joec22]

Where are the files associated with kvm vms and configs? I've created a vm with 2 hard disks on an LVM storage type, but I can't locate where this is mounted. The storage is a 6TB partition created by gpt on /dev/sdb1. When I search by vmid, I only find 2 tiny byte files located in /dev/mapper/.

Thanks

 

[udo]

Where are the files associated with kvm vms and configs? I've created a vm with 2 hard disks on an LVM storage type, but I can't locate where this is mounted. The storage is a 6TB partition created by gpt on /dev/sdb1. When I search by vmid, I only find 2 tiny byte files located in /dev/mapper/.

Thanks

Hi,
try

vgdisplay
lvdisplay

and you will find your disks...

Udo

 

[joec22]

Yes, but I can't do anything with an lv, like copy the raw disk files or config to another server. I also can't see the config file. I can only access once I do a backup.

Maybe there is no need? Or is it advisable to use a different storage method?

 

[udo]

Yes, but I can't do anything with an lv, like copy the raw disk files or config to another server. I also can't see the config file. I can only access once I do a backup.

Maybe there is no need? Or is it advisable to use a different storage method?

Hi,
why not?
the content of the logical volume is the raw-disk like your harddisk at your home-pc. Therefore you can also copy (dd if=/dev/vgname/vm-122-disk-1 of=/backup/disk-122.raw bs=1024k) the lv.

The config of the vm is on the same place: /etc/qemu-server/

Udo

 

[joec22]

Thank you. Is there a better storage method than what I've described?

 

[dietmar]

Thank you. Is there a better storage method than what I've described?

What do you consider 'better'?

 

[joec22]

Performance, manageability, simplicity, I'm not sure, guess that's why I'm asking the question.

 

[JustaGuy]

manageability, simplicity, I'm not sure, guess that's why I'm asking the question.

I think it's an awkward feeling going from a more traditional filesystem-based path structure- where it's possible to browse the contents via GUI like Filezilla for example, to a LVM group storage where the contents are more-less 'hidden' to someone not knowing how to browse the contents of LV-based storage. It's a different animal.

It's worth getting used to though IMO, so as to not have the additional overhead of yet another filesystem management layer eating away at CPU cycles.