From: mailinglist@modernbiztonsag.org
To: "\"Pasi Kärkkäinen\"" <pasik@iki.fi>
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
mailinglist@modernbiztonsag.org, xen-devel@lists.xensource.com
Subject: Re: remus fail with SMP domU
Date: Thu, 9 Feb 2012 10:02:34 +0100 [thread overview]
Message-ID: <a14d74fa7ee7c544e1221c69466d3e28.squirrel@admin.modernbiztonsag.org> (raw)
In-Reply-To: <20120208174912.GX12984@reaktio.net>
> On Wed, Feb 08, 2012 at 04:59:18PM +0100, mailinglist@modernbiztonsag.org
> wrote:
>> Dear List,
>>
>
> Hello,
>
>> i'm experimenting with remus with the following setup.
>>
>> dom0:
>> - Debian Squeeze
>> - Jeremy's 2.6.38.48 kernel
>> - xen 4.1.2 recompiled from sid
>> - DRBD for block device backend
>>
>
Hello,
> Did you try xen-unstable? There are many Remus related fixes/enhancements
> in xen-unstable.
>
Nope, not yet, and i would avoid it if possible because we would like to
use this in a "production" environment. (Shriram's suggestion work though
so i'm onto testing with heavy load now.)
> -- Pasi
Best regards,
Mate
>
>
>> domU
>> - Debian Squeeze
>>
>> Remus is working fine unless i try to give more than 1 core to the domU.
>>
>> Here's the error from remus when i'm trying to enable it for an SMP
>> domU:
>>
>> Traceback (most recent call last):
>> File "/usr/lib/xen-4.1/lib/python/remus", line 219, in <module>
>> run(cfg)
>> File "/usr/lib/xen-4.1/lib/python/remus", line 109, in run
>> dom = vm.VM(cfg.domid)
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 32, in
>> __init__
>> self.loaddominfo()
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 35, in
>> loaddominfo
>> self.dom = parsedominfo(self.dominfo)
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 77, in
>> parsedominfo
>> return s2d(dominfo[1:])
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 61, in s2d
>> val = s2d(elem[1:])
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 64, in s2d
>> return s2d(elem)
>> File "/usr/lib/xen-4.1/lib/python/xen/remus/vm.py", line 66, in s2d
>> for k, v in val.iteritems():
>> AttributeError: 'int' object has no attribute 'iteritems'
>>
>> I've attached the domU configuration file.
>>
>> Please let me know if you need more info on this.
>>
>> Best regards,
>> Mate
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
prev parent reply other threads:[~2012-02-09 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 15:59 remus fail with SMP domU mailinglist
2012-02-08 17:49 ` Pasi Kärkkäinen
2012-02-08 18:54 ` Shriram Rajagopalan
2012-02-09 9:03 ` mailinglist
2012-02-09 9:02 ` mailinglist [this message]
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=a14d74fa7ee7c544e1221c69466d3e28.squirrel@admin.modernbiztonsag.org \
--to=mailinglist@modernbiztonsag.org \
--cc=pasik@iki.fi \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@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).