This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Remus crashes

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Remus crashes
From: Jean Baptiste FAVRE <xen-users@xxxxxxxxxxx>
Date: Tue, 16 Nov 2010 21:31:03 +0100
Delivery-date: Tue, 16 Nov 2010 12:32:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CE2A706.9020707@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4CE2A706.9020707@xxxxxxxxx>
Reply-to: xen-users@xxxxxxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101110 Lightning/1.0b2 Icedove/3.1.6
Seems that remus tries to use "tc" command. Think it's for traffic
shaping to take priority.
Is the package installed on your dom0 ?


Le 16/11/2010 16:45, Darko Petrović a écrit :
> Hello everyone,
> I've managed to configure and start Remus. However, it works only while
> the protected server is not loaded. As soon as I start a
> memory-intensive server application, the stream of Remus messages stops,
> leaving me with an error message. I think the message is not always the
> same, but here is what I've got from the last run:
> PROF: suspending at 1289921328.328959
> PROF: resumed at 1289921330.903716
> xc: error: Error when flushing output buffer (32 = Broken pipe):
> Internal error
> tc filter del dev vif1.0 parent ffff: proto ip pref 10 u32
> RTNETLINK answers: Invalid argument
> We have an error talking to the kernel
> Exception xen.remus.util.PipeException: PipeException('tc failed: 2, No
> such file or directory',) in <bound method BufferedNIC.__del__ of
> <xen.remus.device.BufferedNIC object at 0x7f27844df210>> ignored
> I have tried to pin one physical core to Domain 0 and another one to the
> protected domain, using vcpu-pin but it doesn't help.
> Currently I am running the Xen-unstable tree (last updated 3-4 days
> ago), pv-ops kernel as Dom-0 and as Dom-U, but I had
> a very similar problem with Xen 4.0.0 and as Dom-0.
> Any suggestions?
> Thanks
> Darko
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>