Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 472BDC433DB for ; Wed, 27 Jan 2021 20:13:30 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BC44E64DA3 for ; Wed, 27 Jan 2021 20:13:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BC44E64DA3 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=m5p.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.76389.137818 (Exim 4.92) (envelope-from ) id 1l4rBi-0007Xd-9V; Wed, 27 Jan 2021 20:13:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 76389.137818; Wed, 27 Jan 2021 20:13:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l4rBi-0007XW-6L; Wed, 27 Jan 2021 20:13:14 +0000 Received: by outflank-mailman (input) for mailman id 76389; Wed, 27 Jan 2021 20:13:13 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l4rBh-0007XP-HY for xen-devel@lists.xenproject.org; Wed, 27 Jan 2021 20:13:13 +0000 Received: from mailhost.m5p.com (unknown [74.104.188.4]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id b4f0d5fa-10d9-4883-acab-686cba1ba37d; Wed, 27 Jan 2021 20:13:10 +0000 (UTC) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:f7]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPS id 10RKCx8g027114 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 27 Jan 2021 15:13:05 -0500 (EST) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.15.2/8.15.2/Submit) id 10RKCxFw027113; Wed, 27 Jan 2021 12:12:59 -0800 (PST) (envelope-from ehem) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: b4f0d5fa-10d9-4883-acab-686cba1ba37d Date: Wed, 27 Jan 2021 12:12:59 -0800 From: Elliott Mitchell To: Jan Beulich Cc: Andrew Cooper , George Dunlap , Wei Liu , Roger Pau Monn?? , xen-devel@lists.xenproject.org Subject: Re: [PATCH] x86/pod: Do not fragment PoD memory allocations Message-ID: References: <202101242308.10ON8Umj004866@m5p.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Jan 27, 2021 at 10:47:19AM +0100, Jan Beulich wrote: > On 26.01.2021 18:51, Elliott Mitchell wrote: > > Okay, this has been reliably reproducing for a while. I had originally > > thought it was a problem of HVM plus memory != maxmem, but the > > non-immediate restart disagrees with that assessment. > > I guess it's not really clear what you mean with this, but anyway: > The important aspect here that I'm concerned about is what the > manifestations of the issue are. I'm still hoping that you would > provide such information, so we can then start thinking about how > to solve these. If, of course, there is anything worse than the > expected effects which use of PoD can have on the guest itself. Manifestation is domain 0 and/or Xen panic a few seconds after the domain.cfg file is loaded via `xl`. Everything on the host is lost and the host restarts. Any VMs which were present are lost and need to restart, similar to power loss without UPS. Upon pressing return for `xl create domain.cfg` there is a short period of apparently normal behavior in domain 0. After this there is a short period of very laggy behavior in domain 0. Finally domain 0 goes unresponsive and so far by the time I've gotten to the host's console it has already started to reboot. The periods of apparently normal and laggy behavior are perhaps 5-10 seconds each. The configurations I've reproduced with have had maxmem substantially larger than the total host memory (this is intended as a prototype of a future larger VM). The first recorded observation of this was with Debian's build of Xen 4.8, though I recall running into it with Xen 4.4 too. Part of the problem might also be attributeable to QEMU touching all memory on start (thus causing PoD to try to populate *all* memory) or OVMF. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445