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: Tue, 22 Nov 2011 08:33:01 -0500	[thread overview]
Message-ID: <eddb8c9332cad034094fae78cc1b7549@www.ark-net.org> (raw)
In-Reply-To: <CAP8mzPMeW5N+iia5UudX5PCQUApKww2MCazZtx7HcweNG=FUSA@mail.gmail.com>

On 22.11.2011 01:56, Shriram Rajagopalan wrote:

> eh? I dont think so. with drbd based backend for xen VMs (with or 
> without remus),
> you just use the drbd:<resourceName> syntax (much like phy:...).
> And then the block-drbd script in /etc/xen/scripts/ takes care of the 
> rest of the magic.
> There is no tapdisk involved in this procedure.

> In essence, the block-drbd script just
> 1. parses the drbd:<resourceName> syntax to determine which one of
>  the /dev/drbd[X] devices belong to the <resourceName>,
> 2. does some sanity checks
> 3. promotes <resourceName> in the host to "Primary" and then

> the rest of the control flow happens akin to a phy device, with 
> /dev/drbd[X] being
> supplied as the path to the disk backend.
>
> You could do this manually too in two simple steps.
>  1. On the host where you want to launch the VM, promote the drbd 
> disk to Primary
>  (ensure that the other end is in secondary state)
>  2. change the VM's disk config to 
> phy:/dev/drbd/by-res/<resourceName>
>  and you are good to go.
>  [Though with remus, you ll have to hack the 
> tools/python/xen/remus/device.py script to
>  recognize the /dev/drbd/* URI.]>

The drbd:<resource> syntax works for xm, but not for xl.  I'll have to 
work on that.  Below is what xl spits out trying to create the domain.

dc.xl: config parsing error in disk specification: unknown value for 
format: near `xvda' in `drbd:dc,xvda,w'

> 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
> [5], 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
>
>>
>> Is the remusified drbd (8.3.9) not compiling under the 3.1.x kernel
>> anymore or are you interested in
>> the latest version of DRBD + the remus stuff ?
>>  
>>
>> shriram

I am interested in running the latest drbd changes with remus.  But I 
am interested in getting this to work through the xl interface more than 
anything.



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

  reply	other threads:[~2011-11-22 13:33 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   ` BLKTAP Michael A. Collins
2011-11-22  6:56     ` BLKTAP Shriram Rajagopalan
2011-11-22 13:33       ` Michael A. Collins [this message]
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=eddb8c9332cad034094fae78cc1b7549@www.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).