[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] remus error


  • To: ashish.bijlani@xxxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Ashish Bijlani <ashish.bijlani@xxxxxxxxx>
  • Date: Thu, 4 Mar 2010 03:54:54 -0500
  • Cc: brendan@xxxxxxxxx
  • Delivery-date: Thu, 04 Mar 2010 00:55:50 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mg7lTQa7e9UV2agO06uuHc+Cl+ACwbDh47WmRXgrik2aBd90YSdj3cNdNst89BX+hS /BE15Pqv63NidXB6dkkNs/xZ2vu2Cnc2HiRUuiERjTV68CQK7wqkNmqPhagQwxqitDLi 7A3Djp7CPVgiC/vPIAugbt3LZSf3tKZV4eQDg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Couldn't get it to work. Could you please look at the modules I'm
using. Posting the relevant files.

May be you can fix these and post upstream as well.

Thanks,
Ashish

On Thu, Mar 4, 2010 at 2:59 AM, Ashish Bijlani <ashish.bijlani@xxxxxxxxx> wrote:
> Yes I was successfully able to run " tc qdisc add dev vif3.0 root queue"
>
> "tc qdisc show" prints this:
>
> 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 queue 8001: dev vif3.0 root
>
> all the modules are loaded
>
> Module                  Size  Used by
> sch_queue               3384  1
> ebtable_filter          2696  1
> ebtables               16008  1 ebtable_filter
> ebt_imq                 1640  1
> imq                     6192  0
> xt_IMQ                  2056  0
>
> I think I may have made a mistake while porting rtnetlink to new
> netlink API. I'm looking at that. Hopefully should be able to fix
> that. I'll update soon.
>
> Thanks,
> Ashish
>
> On Thu, Mar 4, 2010 at 2:46 AM, Brendan Cully <brendan@xxxxxxxxx> wrote:
>> On Thursday, 04 March 2010 at 02:16, Ashish Bijlani wrote:
>>> "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?
>>
>> Hmm, and sch_queue and ebt_imq are loaded? Can you run
>> $ tc qdisc add dev vif3.0 root queue
>> ?
>>
>> Do you have ebt: filter table support built? How about the netfilter
>> netlink interface?
>>
>> I haven't actually tried recent pvops myself. With luck I'll get some
>> time tomorrow to do so.
>>
>>> Thanks,
>>> Ashish
>>>
>>> On Thu, Mar 4, 2010 at 2:09 AM, Brendan Cully <brendan@xxxxxxxxx> 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@xxxxxxxx> 
>>> >> 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
>>> >> >
>>> >>
>>> >
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>
>

Attachment: sch_queue.c
Description: Text Data

Attachment: ebt_imq.c
Description: Text Data

Attachment: Makefile
Description: Binary data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.