sbeaudoin

It works now. ChatGPT gave me the answer. The question was : The answer was : So, the process is the following, for those interested : Stop the VM. In a ssh session, go to the vDisk directory who should be : '/mnt/user/domains/[machine name]/" and you should see your vdisk file probably named 'vidks1.img'. Convert it to a qcow 2 format with the following command : qemu-img convert -f raw -O qcow2 vdisk1.img vdisk1.qcow2 The qcow2 extension is not necessary, it could still use the img extension, only the content of the file matters. But as we need a different file name, I found it convenient to use this extension. Edit the vm xml file who should be at : '/etc/libvirt/qemu/[machine name].xml' after making a backup copy. In the "devices" element, find the child "disk" element where his child "source" element point to the original vdisk and change the path and type. For example, for a vdisk at '/mnt/user/domains/srvr-windows/vdisk1.img'. I had the following : <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/srvr-windows/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> I changed the file attribute of the source element to point to the qcow2 file and I changed the type attribute of the driver element to qcow2. <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/srvr-windows/vdisk1.qcow2'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> And the missing element given to me by chatGPT is to execute the following command to make the virtualization platform aware of the change : virsh define /etc/libvirt/qemu/[machine name].xml The file path is the same you edited and it should answer you with : Domain '[machine name]' defined from /etc/libvirt/qemu/[machine name].xml You can then start your VM and after the confirmation of success, confirm the vm configuration in the GUI that the path is really the qcow2 file before removing the img file at '/mnt/user/domains/[machine name]/vidks1.img'. Press F5 to refresh the page and confirm it again. Just in case... Disclaimer : I leave these instructions to help, not to maintain it or to support anyone else. It is POSSIBLE I intervene though... Enjoy.

I finally did a backup of all the content and transfered it back to an xfs array. I suppose now I should have selected the disks in an array and not in a pool. Thank you for the effort anyway.

I couldn't wait... I stopped the VM, went to '/etc/libvirt/qemu' and edited the srvr-windows.xml file. I changed the drvier type 'raw' for 'qcow2' here : <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/srvr-windows/vdisk1.qcow2'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> No joy, same symptoms when I restart the VM.

Thanks for the fast reply. There is no type field on the Gui. I understand I should manually put it on the VM xml file. I will try your suggestion later and keep this post informed.

I have the same problem and would like also a solution. The goal is to convert my vDisks to qcow2 so I could do a snapshot with virsh. I took a Windows VM vDisk "vdisk1.img" with format raw and executed the following from "/mnt/user/domains/srvr-windows" while the VM was running as a proof of concept. qemu-img convert -f raw -O qcow2 vdisk1.img vdisk1.qcow2 The img file have 50GB and the QCow2 have 17GB but I suspect this is caused by differences in how they store zeroes. I then stopped the VM, changed the primary vdisk location to /mnt/user/domains/[vm-name]/vdisk1.qcow2 and kept the vDisk bus to VirtIo. Following that, I start the machine and I have the following (see attached 'boot error.png'). Note that I have also 4 disks passed through from the host to this VM. I then tried all other vDisk bus except IDE and USB without any change on the result. Do someone have any informations for us?

Hi, purchased the UnRaid pro licence and I am migrating from TrueNAS Core to Unraid and I am tryning to reproduce the same shares I had so my existing applications continue to work and I have difficulties to find out how to do it with UnRaid. As an example, I have a ZFS pool named "Main" I imported from TrueNAS. In this pool, I have "Data", "Download" and "Media" folders, each one was a SMB share on TrueNAS. All I can find in unraid is to share "Main". I can't find no way to specify each directory under it. The questions is : Must I do it directly from the smb.conf file or if it is still not possible this way, what do you suggest as an alternative? Thank you.