[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [XCP] xe live-migration


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Tue, 03 Aug 2010 19:51:01 +0400
  • Delivery-date: Tue, 03 Aug 2010 08:51:54 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=aJRQ/QYAs6zWuutYITTFMy0RQz/lSKLPyGtOb4XTtpEbecwgunrp7Gg2DUY1sLp5df d/sYEnqj1kY+zJgj0uOwbZ6dZAwmlFyooCEoBKtZ3jzn4Q2KPnRdHVCJFfgi2zJWE2eV 8ZO4OHmcSPzKH7HEa7OUSrTMv8XJwOo6NDnGs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Right now I got very strange message while trying to evacuate all VM
from host for host maintenance. 

   xe host-evacuate uuid=343e128d-3436-4348-90df-e2b1ebac6277 
   VM didn't acknowledge the need to shutdown.

As I understand, this message appear when I do simple xe
vm-reboot/shutdown for VM without guest tools.

I perform VM migration to different hosts 'by hand' (xe vm-migrate) one
by one and found 'bad' VM.

(I think, xe shall print vm-uuid in message "didn't acknowledge the need
to shutdown").

And why this message can appears during live migration?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.