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] xen 4 via nano u2300 troubles

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] xen 4 via nano u2300 troubles
From: Hans de Bruin <jmdebruin@xxxxxxxxx>
Date: Fri, 21 May 2010 22:54:53 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 May 2010 13:56:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BF59587.5040402@xxxxxxxx>
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: <4BF59370.9050501@xxxxxxxxx> <4BF59587.5040402@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
On 05/20/2010 10:03 PM, Jeremy Fitzhardinge wrote:
On 05/20/2010 12:54 PM, Hans de Bruin wrote:
I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It
has a via nano u2300 cpu and via vx8800 chipset.


...


Since i am not interested in hvm i changed CONFIG_HVM := y in
config/x86_64.mk to n, but that did not make the error disapear.

I think you're treading into lightly tested or completely untested
territory if you disable that.

I have undone my CONFIG_HVM change.

(XEN) Initing memory sharing.
(XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
(XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c480137644>] iommu_setup+0xd4/0x110

Does booting with iommu=0 help?

yep. The kernel has some difficulty in finding the rootfs, but that will be fixed by some recompiling.

--
Hans

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

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