From: Ashish Bijlani <ashish.bijlani@gmail.com>
To: ashish.bijlani@gmail.com, jeremy@goop.org, xen-devel@lists.xensource.com
Subject: Re: remus error
Date: Thu, 4 Mar 2010 02:16:42 -0500 [thread overview]
Message-ID: <ec55b17e1003032316q2506c2a1wea87208eb773f789@mail.gmail.com> (raw)
In-Reply-To: <20100304070958.GA92259@zanzibar.quuxuum.com>
"tc qdisc" works fine I guess:
qdisc pfifo_fast 0: dev peth0 root bands 3 priomap 1 2 2 2 1 2 0 0 1
1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev imq0 root bands 3 priomap 1 2 2 2 1 2 0 0 1 1
1 1 1 1 1 1
qdisc pfifo_fast 0: dev vif3.0 root bands 3 priomap 1 2 2 2 1 2 0 0 1
1 1 1 1 1 1 1
what could be missing?
Thanks,
Ashish
On Thu, Mar 4, 2010 at 2:09 AM, Brendan Cully <brendan@cs.ubc.ca> wrote:
> Sounds like your kernel is missing netlink support. I don't remember
> the exact config option required, but if 'tc qdisc' (from the iproute
> package) works, that probably means you've enabled the right
> option. As I think I mentioned before, turning on something like Token
> Bucket Filter ought to drag in the necessary dependencies.
>
> On Thursday, 04 March 2010 at 01:50, Ashish Bijlani wrote:
>> I'd to modify remus sch_queue ebt_imq kmod to work with pvops (2.6.31.6)
>>
>> Now, I'm getting a different error with "remus -i 100 PVM 192.168.1.5"
>>
>> PROF: suspending at 1267684430.539464
>> installing buffer on imq0
>> RTNETLINK answers: No such file or directory
>> ERROR Internal error: Suspend request failed
>> ERROR Internal error: Domain appears not to have suspended
>> Save exit rc=1
>> Traceback (most recent call last):
>> File "/usr/bin/remus", line 359, in <module>
>> run(cfg)
>> File "/usr/bin/remus", line 340, in run
>> for buf in bufs:
>> File "/usr/bin/remus", line 277, in postsuspend
>> buf.postsuspend()
>> File "/usr/bin/remus", line 159, in postsuspend
>> self._setup()
>> File "/usr/bin/remus", line 185, in _setup
>> self.rth.talk(req.pack())
>> File "/usr/local/lib/python2.6/dist-packages/xen/remus/netlink.py",
>> line 314, in talk
>> self._rth.talk(req)
>> IOError: error sending message
>>
>>
>> "remus --no-net PVM 192.168.1.5" works and imq0 exists, I don't know
>> what is missing...any inputs?
>>
>> Thanks,
>> Ashish
>>
>> On Sun, Feb 28, 2010 at 12:47 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>> > On 02/27/2010 07:54 PM, Ashish Bijlani wrote:
>> >>
>> >> I fail to use remus with xen-unstable (4.0.0-rc4)+ Linux-2.6-pvops:
>> >>
>> >> # sudo remus -i 100 PVM 192.168.1.3
>> >> modprobe sch_queue
>> >> FATAL: Module sch_queue not found.
>> >>
>> >
>> > As far as I know, there hasn't been enough work done to make remus work with
>> > pvops kernels yet.
>> >
>> > J
>> >
>>
>
next prev parent reply other threads:[~2010-03-04 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 3:54 remus error Ashish Bijlani
2010-02-28 5:47 ` Jeremy Fitzhardinge
2010-03-04 6:50 ` Ashish Bijlani
2010-03-04 7:09 ` Brendan Cully
2010-03-04 7:16 ` Ashish Bijlani [this message]
2010-03-04 7:46 ` Brendan Cully
2010-03-04 7:59 ` Ashish Bijlani
2010-03-04 8:54 ` Ashish Bijlani
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 8:54 taojiang628
2010-07-07 18:07 ` Shriram Rajagopalan
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=ec55b17e1003032316q2506c2a1wea87208eb773f789@mail.gmail.com \
--to=ashish.bijlani@gmail.com \
--cc=jeremy@goop.org \
--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).