From owner-freebsd-xen@freebsd.org Wed Jan 25 10:08:33 2017 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2F06CB59B7 for ; Wed, 25 Jan 2017 10:08:33 +0000 (UTC) (envelope-from akshay1994.leo@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77C55BB1 for ; Wed, 25 Jan 2017 10:08:33 +0000 (UTC) (envelope-from akshay1994.leo@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id z134so125915158lff.3 for ; Wed, 25 Jan 2017 02:08:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=T1OpzM96oI25Gg/1HDiGWSti2/IxPVrOqSIwapFRzOQ=; b=ANpIccFUAmC0o1OBAAzU+DA7rAQsVjP9/sNrlz3loeP6SiFm3lNCI4svcegbQ1fLx8 D69N1dZfBHaWNicIMnpmOMd/JTYew3EYvRQOMUGxDQj93xcxrnEi2nBS5uPf7wWICf34 seoFYtvO30ze0xeXtgTLDc0j3NCT4t4tHU4dhYjhgj5zpIo6CrWAN237hL0ZlwfSijjk ilcKOesbADddXXjxHC069nbP/e+19CspcPAtmVvldGXKYqcLHg1WlSY7X4ITG479jaEu y2tGwa6j8rKpNlepRQ0sjML2N8iC9lsK+QmvRRk2/IWA+8tvLVjSMdekDqhG8pGR0gdA Evow== X-Gm-Message-State: AIkVDXKZL0RUACcruP31VZio5XqG8wjCLA5ZIyR3JZgzZ0WK78fC660toTOLyYQO+5j5Ng== X-Received: by 10.25.20.152 with SMTP id 24mr10935224lfu.152.1485336916313; Wed, 25 Jan 2017 01:35:16 -0800 (PST) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com. [209.85.215.45]) by smtp.gmail.com with ESMTPSA id 9sm8261967ljg.33.2017.01.25.01.35.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Jan 2017 01:35:15 -0800 (PST) Received: by mail-lf0-f45.google.com with SMTP id n124so125215091lfd.2 for ; Wed, 25 Jan 2017 01:35:15 -0800 (PST) X-Received: by 10.25.38.136 with SMTP id m130mr13000425lfm.90.1485336915415; Wed, 25 Jan 2017 01:35:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.145.68 with HTTP; Wed, 25 Jan 2017 01:35:14 -0800 (PST) Received: by 10.25.145.68 with HTTP; Wed, 25 Jan 2017 01:35:14 -0800 (PST) In-Reply-To: <20170124165621.iidjypfoyp4ccysi@dhcp-3-221.uk.xensource.com> References: <20170124114444.xdl3qj35lwebkso7@dhcp-3-221.uk.xensource.com> <159d0f04b55.10bbf935114648.7927688075504705395@nfvexpress.com> <20170124165621.iidjypfoyp4ccysi@dhcp-3-221.uk.xensource.com> From: Akshay Jaggi Date: Wed, 25 Jan 2017 09:35:14 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb) To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Cc: Alexander Nusov , FreeBSD-Xen Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 10:08:34 -0000 Hi Alex and Roger, Without the patch and FreeBSD 12, qcow2 doesn't actually work. We were thinking of adding code to warn against this, but then thought gntdev implementation is in process anyway. With the patch, the crash needs to be investigated (because I did run one of the gntdev based image, most probably qcow2, iirc). Sadly, I'm still searching for housing in Dublin, and hence won't be able to look at this immediately. Two weeks, to find and then move in, if I'm lucky. Meanwhile, I'll start hunting for a development machine in office. Regards, Akshay On Jan 24, 2017 16:56, Roger Pau Monn=C3=A9 wrote: > On Tue, Jan 24, 2017 at 05:45:25PM +0300, Alexander Nusov wrote: > > Yes, it was FreeBSD 11.0-STABLE Dom0 with xen-kernel/xen-tools built > from the ports tree (head) > > > > > > > > It seems there is an issue with xen pci devices, since booting from > QCOW2 images actually works (even on FreeBSD 11.0-RELEASE branch) except > communication with /xen/vbd devices from the guest. > > Yes, I'm seeing exactly the same. The QEMU process is killed with a > segmentation fault. Akshay, here is the full debug output: > > Program terminated with signal 11, Segmentation fault. > [...] > #0 blk_handle_requests (blkdev=3D0x807463c00) at hw/block/xen_disk.c:862 > 862 rp =3D blkdev->rings.common.sring->req_prod; > [New Thread 8087f9000 (LWP 100947/)] > [New Thread 807418800 (LWP 100945/)] > [New Thread 807418300 (LWP 100944/)] > [New Thread 807417e00 (LWP 100943/)] > [New Thread 807417900 (LWP 100942/)] > [New Thread 807417400 (LWP 100941/)] > [New Thread 807416a00 (LWP 100940/)] > [New Thread 807416500 (LWP 100939/)] > [New Thread 807416000 (LWP 100091/)] > (gdb) bt > #0 blk_handle_requests (blkdev=3D0x807463c00) at hw/block/xen_disk.c:862 > #1 0x00000000005f9dcd in blk_bh (opaque=3D0x807463c00) at > hw/block/xen_disk.c:918 > #2 0x000000000080ba69 in aio_bh_call (bh=3D0x80780d810) at async.c:87 > #3 0x000000000080bb10 in aio_bh_poll (ctx=3D0x8074a0680) at async.c:115 > #4 0x000000000081c099 in aio_dispatch (ctx=3D0x8074a0680) at aio-posix.c= :303 > #5 0x000000000080c2cd in aio_ctx_dispatch (source=3D0x8074a0680, > callback=3D0, user_data=3D0x0) > at async.c:254 > #6 0x0000000802e3903b in g_main_context_dispatch () from /usr/local/lib/ > libglib-2.0.so.0 > #7 0x000000000081a34c in glib_pollfds_poll () at main-loop.c:259 > #8 0x0000000000819dc5 in os_host_main_loop_wait (timeout=3D0) at > main-loop.c:306 > #9 0x0000000000819c29 in main_loop_wait (nonblocking=3D0) at main-loop.c= :556 > #10 0x0000000000588ed7 in main_loop () at vl.c:1966 > #11 0x0000000000583b59 in main (argc=3D38, argv=3D0x7fffffffe750, > envp=3D0x7fffffffe888) at vl.c:4684 > Current language: auto; currently minimal > > It seems like the device is not properly mapping the grants, and QEMU get= s > a > SEGFAULT when trying to access the ring page. > > Roger. >