Oke, this makes sense!
Knowing this now makes the error message meaningful. And explains why the newly created test vm moved as expected.
@wbumiller
Looking back in my notes, indeed that disk is not created by pve but was an already existing machine. The disk is imported as following:
qm set...
I don't quite understand how this relates to the 'volume ID' parsing?
Besides a newly test VM with its disk on the same lvm volume group worked well.
There seems to be a work around:
Manually copy the logical volume to a raw disk file on <GlusterFS mount point>/images/<vmid>/ using 'dd', and...
Goal:
Move lvm disks to GlusterFS, to move some vms to new hardware and have the mail gateway HA.
Test:
I got one newly created test VM moved, to GlusterFS, First it did not boot, but after setting the disk cache to write through it did.
Failure:
Shutdown an existing vm , backed it up. and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.