[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx, Christophe Saout <christophe@xxxxxxxx>
  • From: Thomas DuBuisson <thomas.dubuisson@xxxxxxxxx>
  • Date: Wed, 15 Apr 2009 11:36:58 -0700
  • Cc:
  • Delivery-date: Wed, 15 Apr 2009 11:37:29 -0700
  • 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 :content-type:content-transfer-encoding; b=BtbiNaDyvpeK68oNbwI26k3WkLuQh2yZYbh5DqEn3D77aTaAaifXU2RFyjHQvvyrGc 7wDNrBMfyFBarg/V6X1PFaUtWnDT/03LohSKT1WzaAtpRcp45X0TS9pHB3D2Dq7kZ01P ciKc9O6RAsDUEyDtKHJQEvCb/F7Rf9dkaimuk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>  I'm using xen-3.4.0-rc2-pre.  I'm actually running a
> cleaned and rebuilt kernel from that repo right now... no issues yet.
> I'll start compiling some CPU hungry processes and see what happens
> (thats what I was doing last time).

For the above-mentioned run of xen-3.4.0-rc2-pre I had noreboot -
_when_ it locked up, the X display remained but there was no response
/ no mouse etc.  I didn't check if it was responding to network
activity.

I've been running with xen-3.3.2-rc1-pre for about an hour now and
haven't had issues.  The work load is the same as when I was using
xen-3.4 so the explainations that come to mind are 1) I'm lucky 2) The
issue is xen-unstable 3) Its still a kernel issue but isn't triggered
by xen 3.3.

Thomas

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.