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

Re: [Xen-users] Xen and iSCSI


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Andy Repton <xen@xxxxxxxxxx>
  • Date: Mon, 30 Jan 2006 09:13:46 +0000
  • Delivery-date: Mon, 30 Jan 2006 09:23:23 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LXmvZy90yov4ILTImQlkf/6nSOjGXsy0paRAe447OHxmPHKJrRhZyg/niWrp1AVnL86r/GAnXOT0Xqmxa9m5AR/OePOfm0iJIPGJZqd/hBU9cfZEs8J+1xAUL2zxt/2thJ76Y31yfeLLrTcgqYn2QAxGUfkPVJHzK40DrLizbTk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> And Xen itself handles the migration.. access to block device on host1 is
> stopped when the access is started on host2 (after the migration).

Are you saying that the change from dom0 handling the block device to
the second dom0 handling the block device is completely transparent?

E.g. I have a dom0 on one machine, A, importing a SAN block device and
exporting it as /dev/sda to a domU, and an identical machine, B, with
the dom0 importing the same block device. If I migrate the domU from 
A to B, will the migration be seamless in the same way it would be if
the domU was using iscsi to access the SAN?

If this is the case then why would anyone want the overhead of running
iscsi in the domU?

BTW, this is an interesting discussion for me as I now have my dom0
setup to export evms drives as iscsi root to my domUs, before I go any
further down this avenue, I am interested in investigating the
alternative setups that allow easy migration.

Andy
--
pteron.net services

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


 


Rackspace

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