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

[Xen-users] Live migration under drbd


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, drbd-user@xxxxxxxxxxxxxxxx
  • From: "Paras pradhan" <pradhanparas@xxxxxxxxx>
  • Date: Fri, 19 Sep 2008 17:49:50 -0500
  • Cc:
  • Delivery-date: Fri, 19 Sep 2008 15:50:29 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=J3izlAJ9TmOJP3uCdaffqxooFw95bc+KdsUXTpOP8yejKbyyLjsMvegDg+cvI4k40r R4ED9bEpLo51R9j84B+9VEpLGe76uukVJM63CdopZIDP7NWFFVSSz6n8l1PlCEANRZjV tBFB+agIR8BKyuE8G2gRg7Kn60tW/uBR6XiYk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello all,

When I live migrate my centos guest from node1 to node2,  I can ping the guest, but on node 2 if i do: xm console guest01 , I am not able to access it. When migrating back to node1 , I can access the console.

What I noticed is, to access the console, the node 's drbd resource/disk needs to be in primary status . 

Is it typical or only I am having this problem.

Is there any way out, after migrating a guest from node1 to node2, node2's drbd resource/disk automatically becomes primary and node1 secondary.

I am running xen 3.0.3 under CentOS 5.2.

Thanks
Paras.
_______________________________________________
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®.