[GitHub] [cloudstack] weizhouapache edited a comment on issue #3720: VM stopped/crashing while Migration with Maintenance Mode (KVM)

2019-12-03 Thread GitBox 
weizhouapache edited a comment on issue #3720: VM stopped/crashing while 
Migration with Maintenance Mode (KVM)
URL: https://github.com/apache/cloudstack/issues/3720#issuecomment-561073274
 
 
   @svenvogel @andrijapanicsb 
   ```
   vm is stopped due to some cloudstack bugs. for example, when we put a
   host to maintenance, the vm will be stopped if (1) no other host is Up in
   same cluster, or (2) vm migration fails and no retry in cloudstack, or (3)
   multiple vms are migrated to same destination at the same time but there is
   no enough memory on the destination.
   ```
   (1) has been tracked in #3707 and discussed by some comments in this ticket.
   (2) is changed in #3425 but not done.
   (3) is fixed by #3727 and #3728. which caused crashed vm in host maintenance 
on our platforms.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack] weizhouapache edited a comment on issue #3720: VM stopped/crashing while Migration with Maintenance Mode (KVM)

2019-11-27 Thread GitBox 
weizhouapache edited a comment on issue #3720: VM stopped/crashing while 
Migration with Maintenance Mode (KVM)
URL: https://github.com/apache/cloudstack/issues/3720#issuecomment-559039297
 
 
   > @ustcweizhou @andrijapanicsb i think this sounds good.
   > 
   > one question.
   > 
   > > (2.2.1) if forceMaintenance = true, schedule a task to stop/start the vm.
   > 
   > @ustcweizhou why we should stop and start them?
   > 
   @svenvogel if vm cannot be migrated after 5 times, to continue with the 
maintenance (because forceMaintenance is true), we need to stop it and start it 
on another server. make sense ?
   > additional we encounter the following problem.
   > 
   > 1. iso could not be mounted or storage pool on destination host, i dont 
know why this is a problem, manually mounting was no problem. maybe anyone has 
information about that?
   
   yes, it is one root cause of failed migration.
   
   > 2. if QEMU or Host Version version are different machine type will change 
the flags `hvm`
   >i think this should be on view of the infrastructure admin.
   
   If hosts have different cpu model or qemu version, they should use custom 
cpu or cpu flags. It is not an issue in my point of view.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services