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

[Xen-users] drbd + xen + heartbeat


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, drbd-user-request@xxxxxxxxxxxxxxxx, linux-ha@xxxxxxxxxxxxxxxxxx
  • From: "Paras pradhan" <pradhanparas@xxxxxxxxx>
  • Date: Thu, 18 Sep 2008 17:48:55 -0500
  • Cc:
  • Delivery-date: Thu, 18 Sep 2008 15:49:33 -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=dinMnRn/gKNseX9iWhKy5Uxo23tCwMaKmoV8xw3XCbwF8Ai95PjT997jw1riAP1BnP ke23C5r3Ni2TgWEcFWLhXPR/LBQ4XnhDNDc8/SIzdq1ZDZ5gZ4P2M2IB1ZbrHEtEFf0k L69NCKGJyNo8iMohDser9BTFNW4bcH/Yip9lE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I am on the way to setup a 2 node xen cluster using drbd.

To automatically control the role (Secondary -> Secondary, Primary-> Secondary, Secondary->Primary) of my drbd resource, it seems like (not sure though) i need to use 

disk = [ 'drbd1:guest01-disk,xvda,w' ]

instead of

disk = [ "phy:/dev/vg/guest01-disk,xvda,w" ]

And it is only possible with xen 3.2 or later. Is it true? With xen 3.0.3. I get Error: Disk not acceptable. If yes, is there any way out so that xen controls the role automatically without upgrading xen.


My current problem: if i want to start the xen domU, first i need to manually make the drbd resource primary using: drbdsetup /dev/drbd0 primary -o
And after migration I can not access the console in the other node. It hangs after few seconds. If I migrate back the domU to the original node, then I can again access the console easily.


Right now I have xen 3.0.3 running 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®.