Hi Daniel, You can move the config files trough /etc/pve/node etc in the right dir
Verstuurd vanaf mijn iPhone > Op 26 mei 2016 om 23:20 heeft Daniel Eschner <dan...@linux-nerd.de> het > volgende geschreven: > > Configurationfiles and LVM still exist in the Host-System. > > ACTIVE '/dev/pve/vm-100-disk-1' [20.00 GiB] inherit > ACTIVE '/dev/pve/vm-101-disk-1' [50.00 GiB] inherit > > Just proxmox need to know the the VM is located on that server ;) > > >> Am 26.05.2016 um 23:09 schrieb Daniel Eschner <dan...@linux-nerd.de>: >> >> Hi All, >> >> i played a bit with the HA feature. It seems now i damaged 2 VMs which are >> located on the local LVM-THIN >> After i placed the nodes in the HA and rebootet the Host-Systems all VMs has >> been migrated to another Host which is OK but now i am not able to start the >> VM or not able to migrate it back to host01 where the nodes was located >> before. >> >> When i start the Migration i get these errors: >> >> May 26 23:04:10 starting migration of CT 100 to node 'host01' (10.0.2.110) >> May 26 23:04:10 copy mountpoint 'rootfs' (local-lvm:vm-100-disk-1) to node ' >> host01' >> May 26 23:04:10 ERROR: unable to migrate 'local-lvm:vm-100-disk-1' to >> 'local-lvm:vm-100-disk-1' on host '10.0.2.110' - source type 'lvmthin' not >> implemented >> May 26 23:04:10 aborting phase 1 - cleanup resources >> May 26 23:04:10 start final cleanup >> May 26 23:04:10 ERROR: migration aborted (duration 00:00:00): unable to >> migrate 'local-lvm:vm-100-disk-1' to 'local-lvm:vm-100-disk-1' on host >> '10.0.2.110' - source type 'lvmthin' not implemented >> TASK ERROR: migration aborted >> >> When i try to start i get the following error: >> >> lxc-start: lxc_start.c: main: 344 The container failed to start. >> lxc-start: lxc_start.c: main: 346 To get more details, run the container in >> foreground mode. >> lxc-start: lxc_start.c: main: 348 Additional information can be obtained by >> setting the --logfile and --logpriority options. >> TASK ERROR: command 'lxc-start -n 100' failed: exit code 1 >> >> It seems that it happend because its not a shared storage. >> >> Is there anyway to fix the problem then i can run my VMs again? ;) >> >> P.S. The VM in my shared Ceph Storage works fine. >> >> >> Cheers >> >> Daniel >> _______________________________________________ >> pve-user mailing list >> pve-user@pve.proxmox.com >> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > _______________________________________________ > pve-user mailing list > pve-user@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
