Search results

  1. M

    v4.4 move_disk (unable to parse volume ID)

    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...
  2. M

    v4.4 move_disk (unable to parse volume ID)

    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...
  3. M

    v4.4 move_disk (unable to parse volume ID)

    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...

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!