From: Florian Heigl <florian.heigl@gmail.com>
To: mike.a.collins@ark-net.org
Cc: rshriram@cs.ubc.ca, xen-devel@lists.xensource.com,
xen-users@lists.xensource.com
Subject: Re: [Xen-users] BLKTAP
Date: Tue, 22 Nov 2011 16:29:39 +0100 [thread overview]
Message-ID: <CAFivhP==_ivB=1i-Evv0xYP73EwtBeL3OY4DNDWNUnZBtWLJtA@mail.gmail.com> (raw)
In-Reply-To: <eddb8c9332cad034094fae78cc1b7549@www.ark-net.org>
2011/11/22 Michael A. Collins <mike.a.collins@ark-net.org>:
> 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:...).
> The drbd:<resource> syntax works for xm, but not for xl. I'll have to work
That's what I ended up with, too
>> 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.
wasn't there something in remus that demands you have a drbd: device
if you're not using blktap?
>> 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.
Currently there's no alternate reality available in which one can run Remus?
blktap - not really there (and it would have other nice features)
dr:bd - doesn't play with xl
xm - not supposed to use that any more
older distros - will not take remus patches i guess
older howtos - broken since Remus is already part of Xen by now
(And I don't think it will get better by pointing at a workaround else
if one thing that should work isn't working.
Instead, soon, it will no longer work at all)
next prev parent reply other threads:[~2011-11-22 15:29 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 ` BLKTAP Michael A. Collins
2011-11-22 15:29 ` Florian Heigl [this message]
2011-11-22 17:27 ` [Xen-users] BLKTAP 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='CAFivhP==_ivB=1i-Evv0xYP73EwtBeL3OY4DNDWNUnZBtWLJtA@mail.gmail.com' \
--to=florian.heigl@gmail.com \
--cc=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).