From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename `nodhcp' to `ensurebridge' Date: Fri, 23 Oct 2015 09:14:43 +0100 Message-ID: <1445588083.32735.30.camel@citrix.com> References: <1443181028-22705-1-git-send-email-ian.jackson@eu.citrix.com> <1443208522-24905-1-git-send-email-ian.jackson@eu.citrix.com> <1443208522-24905-18-git-send-email-ian.jackson@eu.citrix.com> <9E79D1C9A97CFD4097BCE431828FDD310192D1E2@SHSMSX101.ccr.corp.intel.com> <9E79D1C9A97CFD4097BCE431828FDD3102320BEC@SHSMSX103.ccr.corp.intel.com> <9E79D1C9A97CFD4097BCE431828FDD31023253CF@SHSMSX103.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZpXUu-0001zx-VY for xen-devel@lists.xenproject.org; Fri, 23 Oct 2015 08:14:49 +0000 In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD31023253CF@SHSMSX103.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Hu, Robert" , 'Ian Jackson' , "'xen-devel@lists.xenproject.org'" List-Id: xen-devel@lists.xenproject.org On Fri, 2015-10-23 at 06:16 +0000, Hu, Robert wrote: > [Hu, Robert] > Seems the failure log shall be this, any idea? I've spent days on > debugging this:( > (XEN) traps.c:3290: GPF (0000): ffff82d080195082 -> ffff82d080243d9d > (XEN) PCI add device 0000:00:00.0 > (XEN) PCI add device 0000:00:01.0 > (XEN) PCI add device 0000:00:01.1 > (XEN) PCI add device 0000:00:01.2 > (XEN) PCI add device 0000:00:01.3 > (XEN) PCI add device 0000:00:02.0 > (XEN) PCI add device 0000:00:03.0 > (XEN) d0: Forcing read-only access to MFN fed00 > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > Issued domain 3 reboot > qemu: terminating on signal 1 from pid 4322 Please can you report this as a regular bug in a fresh thread, that way the relevant Xen maintainers are likely to see and react to it, rather than just us osstest folks. Please include whatever information you can, e.g. the guest config file used, details about the type of guest, which level of nesting this is happening at, the contents of any logs under /var/log/xen in L0 and L1 host etc. If this crash is in an L1 host then you might also want to CC the nested hvm maintainers at Intel. See http://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen_Project for general advice on reporting a bug and other things to consider including. Thanks, Ian.