10 Apr
2019
10 Apr
'19
10:39 a.m.
nardusg@gmail.com writes:
Wonder if this issue is related to our problem and if there is a way around it. We upgraded from 4.2.8. to 4.3.2. Now when we start some of the VM's fail to start. You need to deattach the disks, create new VM, reattach the disks to the new VM and then the new VM starts.
Hi, were those VMs previously migrated from a 4.2.8 to a 4.3.2 host or to a 4.3.[01] host (which have the given bug)? Would it be possible to provide Vdsm logs from some of the failed and successful (with the new VM) starts with the same storage and also from the destination host of the preceding migration of the VM to a 4.3 host (if the VM was migrated)? Thanks, Milan