From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: [V8 PATCH 0/8] pvh dom0.... Date: Mon, 24 Mar 2014 14:36:10 -0700 Message-ID: <20140324143610.5db70509@mantra.us.oracle.com> References: <1395452357-1598-1-git-send-email-mukesh.rathor@oracle.com> <533001780200007800001326@nat28.tlf.novell.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 1WSCXf-0000nQ-2a for xen-devel@lists.xenproject.org; Mon, 24 Mar 2014 21:36:23 +0000 In-Reply-To: <533001780200007800001326@nat28.tlf.novell.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: Jan Beulich Cc: George.Dunlap@eu.citrix.com, xen-devel@lists.xenproject.org, keir.xen@gmail.com, tim@xen.org List-Id: xen-devel@lists.xenproject.org On Mon, 24 Mar 2014 08:57:12 +0000 "Jan Beulich" wrote: > >>> On 22.03.14 at 02:39, wrote: ....... > > Caveat: > > > > With these patches, an HVM guest during boot intermittantly takes > > unresolved fault in load_module() path. This for PVH dom0 and not <=== > > PV, and latest upstream kernel. I was not able to reproduce > > with older stock fedora 19 kernel. So, it appears the problem might > > be on the guest side, and not xen. Hence I decided to go ahead and > > submit these while I debug that. > > Without proper understanding of this I don't see a way for us to apply > the series, and it should therefore have been tagged as RFC. Just to > avoid any misunderstanding - even if the root cause was on the guest > side, if without your patches the issue never surfaces, this would > still need to be treated as a regression, and a way would need to be Well, the problem doesn't happen with PV dom0, only PVH dom0, so not quite a regression IMO :). > found to make those guests work flawlessly again. Furthermore, with > the issue being in HVM guests, it is rather unlikely (but admittedly > not entirely impossible) that the issue is in the guest, as similar > problems aren't - aiui- known from Linux running on native hardware. > > Apart from that, assuming you spent quite some time in isolating the > problem - did you determine which of the patches in this series > introduces it? Knowing that might help in determining possible reasons No, since the problem only occurs on PVH dom0 and not PV dom0, I need all patches to boot dom0 in PVH mode and be able to create guests on it. Will continue debug it. thanks a lot for your time, Mukesh