kimchi icon indicating copy to clipboard operation
kimchi copied to clipboard

Can't add existing storage device to VM

Open ghost opened this issue 7 years ago • 3 comments

I recently reorganized mount points and switched to NFS instead of CIFS on ubuntu server 16.04. So my windows 10 vm no longer pointed to the right spot for the virtual hard disk. So i'm trying to add the same hard disk, at the new location.

On the Add a Storage Device to VM modal, I select existing disk option, the NFS storage pool, but "Storage Volume" never enables and I'm unable to select the image

I added drive instead of choosing existing one, "win101488484816798.img"

This new image "win101488484816798.img" shows up, unlike my original image

I renamed my old image to something similar to the new image just to see if it would do anything but it still doesnt show up in the drop down list

2

ghost avatar Mar 02 '17 20:03 ghost

Use virsh to export the domain to xml, then edit it manually and undefine and redefine the domain.#

But if you moved from CIFS to NFS don't you need to set up the storage space on Kimchi?

image

NotoriousPyro avatar Apr 03 '17 22:04 NotoriousPyro

Hi @meffect

I suppose you have added a new NFS pool to point to your NFS server as you were be able to see the new volume you added in the drop down menu.

Kimchi lists only the volumes not in use by any other virtual machines. So my guess is that the image file is not showing up because it is in use by other resource. One way to confirm that is on "Storage tab". Go to the pool you want to check the volumes and, list the volumes there. If the volume is in use by other resource, there would be a warning icon telling that to you.

screenshot from 2017-06-06 14-34-04

alinefm avatar Jun 06 '17 17:06 alinefm

I have the same issue. Moving img files from a different KVM installation and they are not available under "Add a Storage Voume to VM" even though they show up under the Storage tab in Kimchi under the respective pool. Also tried renaming the imgs to match a working storage volume created under Kimchi, but still does not show up. Additionally, I tried using chmod to clone the attributes of a working storage volume, but no difference.

The migrated img works perfectly fine when using virt-manager on the same host as I am trying with Kimchi and in the same storage pool.

ghost avatar Sep 23 '19 16:09 ghost