xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Michael A. Collins" <mike.a.collins@ark-net.org>
To: rshriram@cs.ubc.ca
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: BLKTAP
Date: Mon, 21 Nov 2011 21:04:51 -0500	[thread overview]
Message-ID: <000301cca8bb$1ebfaa90$5c3effb0$@ark-net.org> (raw)
In-Reply-To: <CAP8mzPPfHBA+nq_y7QxiwLJGa0P+eyaHFhJbFNZR_uL-D_zyZA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1960 bytes --]

From: Shriram Rajagopalan [mailto:rshriram@cs.ubc.ca] 
Sent: Monday, November 21, 2011 12:03 AM
To: Michael A. Collins
Cc: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
Subject: Re: [Xen-devel] BLKTAP

 

.


drbd/remus - why  do you need blktap ?

shriram

 

>From my readings, I have found only a few examples of using remus.  Most of
them refer to using the following stanza in the disk section of a VM's cfg
file:

tap2:remus:backuphost:anyfreeport|

 

That doesn't work for xl, but even using it with xm causes issues, since
there isn't a tap device without the kernel module.  So I also found out
that drbd uses a tap device to handle the hook in with Xen, so if you want
to have automagic working with block-drbd xen scripts then you have to use
tap.  With all that said and done, I'm currently running drbd 8.3.11 since
that's the version of the kernel module included with Linux 3.1, but I'm
just using Xen's phy handler for the disk section of my VM's cfg file.

 

I see that there is a nice howto for debian on remusha.wikidot.com, but
again it uses a 2.6.32 kernel from Jeremy's git repo, which has the tap
kernel module.  I again assert that currently there is very little out there
that would help to get someone started using remus with drbd in the linux
3.1.x world.  I run remus at work, but it's using shared storage and have no
need to use it with drbd, but at home I don't really want to set that up, so
I thought drbd would be a nice start.

 

I've started diffing the 8.3.9 branch of drbd with your changes for remus
and will see how hard it is to get that in the 8.3.11 version I'm using. 

 

With that being said, I mostly use xl for everything at home, I don't even
have the xend service running, which makes matters worse, since I'm sure
that most of remus uses the xend service and not the API to do the magic.  I
am willing to document my steps and post to the wiki, so that others could
benefit from it!

Mike


[-- Attachment #1.2: Type: text/html, Size: 6070 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2011-11-22  2:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  0:45 BLKTAP Michael A. Collins
2011-11-21  5:03 ` BLKTAP Shriram Rajagopalan
2011-11-22  2:04   ` Michael A. Collins [this message]
2011-11-22  6:56     ` BLKTAP Shriram Rajagopalan
2011-11-22 13:33       ` BLKTAP Michael A. Collins
2011-11-22 15:29         ` [Xen-users] BLKTAP Florian Heigl
2011-11-22 17:27           ` Shriram Rajagopalan
2011-11-22 18:15             ` Michael A. Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000301cca8bb$1ebfaa90$5c3effb0$@ark-net.org' \
    --to=mike.a.collins@ark-net.org \
    --cc=rshriram@cs.ubc.ca \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).