From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: remus error
Date: Sat, 27 Feb 2010 21:47:33 -0800
Message-ID: <4B8A0375.6040207@goop.org>
References: <ec55b17e1002271954u24ff87cbt5bb397d3b8f9d783@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <ec55b17e1002271954u24ff87cbt5bb397d3b8f9d783@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ashish Bijlani <ashish.bijlani@gmail.com>
Cc: brendan@cs.ubc.ca, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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