WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU guest for xcp 0.1.1

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Thu, 18 Mar 2010 08:28:18 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Thu, 18 Mar 2010 08:29:03 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=0zVr8x74ruS3VVozn4COBBVK17EGtnz4+ijYfzSBUVc=; b=igoWy46gvv4SBnJeK9XgGFX+MjrLV5vQ4x2EroYHXjsKi1+e0FHLp8KOkwJoepMez3 IssxiNnxjV2uIm6rp27Pj3HdXROhqPw4M2ZJcR86FqyTvfnpAQiwU9DCXD7YZ+9vFVvN us23DkYmLNsbdLdz1dGpmoUvuIOF0xrFJvACw=
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=Ex+Fi9OnwkfykxX05M2yN0MABpHiX79cVgtsFowG09Jr5+9pQYY+o3P2Wz6oqbWEBf XgEikox0HRQKsADV768In/wWE60g9HiiaMLDqxoBdlx6elRarZTXE7aLqg3KblLSE48E 5vDGrFZK0klG5g+soc1aQGLj00RJtQkwdckgM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100318143906.GH14445@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1268660645.10129.25070.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx> <1268725069.8652.4179.camel@xxxxxxxxxxxxxxxxxxxxx> <20100316152259.GO1878@xxxxxxxxxxx> <29b32d341003161625w2969f2daib3408561920793d3@xxxxxxxxxxxxxx> <29b32d341003171144k628a7741x17b6658731f96e4b@xxxxxxxxxxxxxx> <1268903824.10129.38718.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003180643o326f7f43h97c25bd104f3b658@xxxxxxxxxxxxxx> <1268921503.10129.39640.camel@xxxxxxxxxxxxxxxxxxxxxx> <20100318143906.GH14445@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Ian for clarification on interrupt handling mechanism.

Thanks Konrad. Should I use xen/next in dom0 or domU?

Thanks

On Thu, Mar 18, 2010 at 7:39 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
> > Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> > devices in dom0.
>
> This may be your problem, I don't know if this is expected to work or
> not.

Oh yeah. That got fixed in the xen/next (or rather in the
pv/pcifront-2.6.32 branch and pv/pciback-2.6.32).

It should work with the newer kernel (xen/next from Jeremy's PV-OPS git
tree).

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