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-devel] domU can't start, Non-priv warnings

To: "Jerone Young" <jyoung5@xxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] domU can't start, Non-priv warnings
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Tue, 16 Aug 2005 13:23:08 -0700
Cc: Andrew Theurer <habanero@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2005 20:21:33 +0000
Envelope-to: www-data@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWind5jwuV4tWl+TUKKQ6NyNl22fgAAe03A
Thread-topic: [Xen-devel] domU can't start, Non-priv warnings
Try to remove the network stuff. The warnings are harmless. I've got
domU working at least yesterday, seeing the warnings.

Intel Open Source Technology Center

Jerone Young wrote:
> On Tue, 2005-08-16 at 20:45 +0100, Keir Fraser wrote:
>> On 16 Aug 2005, at 20:19, Andrew Theurer wrote:
>>> They boot partially, ending with:
>>> xen_mem: Initialising balloon driver.
>>> Grant table initialized
>>> IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
>>> audit: initializing netlink socket (disabled)
>>> audit(1124251914.348:0): initialized
>>> VFS: Disk quotas dquot_6.5.1
>>> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
>>> This is with the default kernel configs xen-unstable provides.  NX
>>> is enabled on the EM64T.  I could not find a similar BIOS option for
>>> Opteron.  Even through they are "stuck", cpu time for these domains
>>> increments steadily.  Any ideas?
>> Probably getting stuck in a page-fault loop. We also have observed
>> this probnlem but haven;t narrowed down what changeset causes the
>> problem. We think it's one from sometime last week though (before
>> the weekend). If you can give info on the last changeset that works
>> for you, that would be very useful.
> I'll take sometime tonight & go through the changesets & see if I can
> narrow it down further.
>>   -- Keir
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel

Xen-devel mailing list