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

[Xen-devel] XEN migration architecture question


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
  • From: Eric Tessler <maiden1134@xxxxxxxxx>
  • Date: Thu, 20 Jan 2005 12:44:40 -0800 (PST)
  • Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
  • Delivery-date: Thu, 20 Jan 2005 20:45:29 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Uu9rp6ZQI00MPv6Qf88ytYjeV8uT7rIjzhSGcgUNrvdrz2E9i41FCEBSHD5Vl3WKUXIml7Ue54KeyX+wRGkLxBdIF6XuFjYIuo+0GwRzE/3yn1xqmopPPqr2zD7JCDTT94f8EygsryUmSJdE7cNTAkcQ6oqgZwfaVVdTNJKaOBw= ;
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>

I have an important question about XEN's migation operation related to the XEN block and network back/front drivers.  If I migrate a domain from one machine to another in the middle of heavy disk/network activity, what happnens to the back/front end XEN drivers? (I see they have suspend/resume operations but I don't believe they are being used)  I see that the front end drivers are passing machine addresses to the back-end drivers - are these pointers somehow still valid when a domain is moved to another machine?  Shouldn't the drivers wait until there is no I/O activity before being migrated?
 
Thanks,
Eric


Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term'

 


Rackspace

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