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

Re: [Xen-users] Remus: network buffering problem


  • To: Wenda Ni <wonda.ni@xxxxxxxxx>
  • From: Todd Deshane <todd.deshane@xxxxxxx>
  • Date: Sat, 19 Feb 2011 02:44:50 +0000
  • Cc: Shriram Rajagopalan <rshriram@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 18 Feb 2011 18:46:12 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=qhEWkHn4m5JZC44xYztiTV04AmPnugzOKK9P24bglUCC3+Manzo5UlwemWHhZx3HLb 2CEMPH8rXPKwxM959a3BK1m8eHkKwrjRkN3AYOje4OSHezu+oOOn71IDz2vzhcQoxLru q9qqfyfP7ow1UY5XrwLOUdE5gZEDf1MX5AH0c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Adding our new remus maintainer to the CC

On Fri, Feb 18, 2011 at 6:24 AM, Wenda Ni <wonda.ni@xxxxxxxxx> wrote:
> Hello,
>
> Many thanks to Simon for his trouble shooting on live migration. I have now
> started testing remus according to the remus link
> http://nss.cs.ubc.ca/remus/doc.html
>
> 1) Remus in its simplest mode (--no-net option), without disk replication or
> network protection, is now working good.
>
> 2) When we add the network buffering protection (remove the --no-net
> option), remus gives the error as follows:
>
> modprobe -q ifb
>
> modprobe -q imq
>
> Traceback (most recent call last):
>   File "/usr/bin/remus", line 210, in <module>
>     run(cfg)
>   File "/usr/bin/remus", line 119, in run
>     bufs.append(BufferedNIC(vif))
>   File "/usr/local/lib/python2.6/dist-packages/xen/remus/device.py", line
> 272, in __init__
>     self.pool = Netbufpool(selectnetbuf())
>   File "/usr/local/lib/python2.6/dist-packages/xen/remus/device.py", line
> 174, in selectnetbuf
>     raise BufferedNICException('no net buffer available')
> xen.remus.device.BufferedNICException: no net buffer available
> Exception AttributeError: "'BufferedNIC' object has no attribute 'bufdev'"
> in <bound method BufferedNIC.__del__ of <xen.remus.device.BufferedNIC object
> at 0xd9dd90>> ignored
>
> I googled, but find little useful info. Could anyone know my problem?
>
> --
> Cheers,
>
> Wenda Ni, Ph.D.
> Dept. of Computer Science and Engineering
> State University of New York (SUNY) at Buffalo
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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


 


Rackspace

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