From owner-freebsd-xen@freebsd.org Thu Feb 2 23:43:47 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 70309CCB7C9 for ; Thu, 2 Feb 2017 23:43:47 +0000 (UTC) (envelope-from akshay1994.leo@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (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 EEF72E92 for ; Thu, 2 Feb 2017 23:43:46 +0000 (UTC) (envelope-from akshay1994.leo@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id n124so1649909lfd.2 for ; Thu, 02 Feb 2017 15:43:46 -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:cc; bh=uisSoHi1XCrBXwQxGuf/Syr8I97tM/XH8F1iHEz6yIQ=; b=Hgu7LOcYVFgeDy7/SARTY69/HZJxTw+8T1thOS0rt/rbEglFfpBcz8z8cPFmffVAqK BOYMnjOA71zgVp+MdC+QgSO1LAJSGwsVJrBjnpcGuyQCNQJbOuMEGpyrGN3FRMmxRqsB gIImxRGDtvk0TqERXjSLTZNmzZPfpiEXkAFefkImGio53Mi5ed7eevZXKU/4F7YzDw/T jkpJZ3pYIHHF+orWNE1cw2fP/kUZquS4h6jn3o5G3uBYvhioVfVUImLns/Ni9RwYcZHn Lj5rgvXHM6Adn8jg7s8IyD8EpEycnZDwTjTwZ2FmZS10CsQb86h7sDyiyxflMJURLSti vSkg== X-Gm-Message-State: AIkVDXL7uYm2EJYYP6HxyeO4M2jsJ4Ke/thIWS6lUPUwAqWulhOQuDp2nUnYZpdFurTjNA== X-Received: by 10.25.193.21 with SMTP id r21mr3925911lff.103.1486078642936; Thu, 02 Feb 2017 15:37:22 -0800 (PST) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com. [209.85.215.48]) by smtp.gmail.com with ESMTPSA id c143sm7072300lfc.13.2017.02.02.15.37.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Feb 2017 15:37:22 -0800 (PST) Received: by mail-lf0-f48.google.com with SMTP id x1so1646395lff.0 for ; Thu, 02 Feb 2017 15:37:22 -0800 (PST) X-Received: by 10.46.84.92 with SMTP id y28mt5286243ljd.40.1486078642653; Thu, 02 Feb 2017 15:37:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.145.68 with HTTP; Thu, 2 Feb 2017 15:37:02 -0800 (PST) In-Reply-To: <159d57da8bb.e9fea5dc25161.6113276104371162720@nfvexpress.com> References: <20170124114444.xdl3qj35lwebkso7@dhcp-3-221.uk.xensource.com> <159d0f04b55.10bbf935114648.7927688075504705395@nfvexpress.com> <20170124165621.iidjypfoyp4ccysi@dhcp-3-221.uk.xensource.com> <159d55b6b65.dc9b3b1720453.5847395326743424395@nfvexpress.com> <20170125115051.sasgqxwgt47p7pwi@dhcp-3-221.uk.xensource.com> <159d57da8bb.e9fea5dc25161.6113276104371162720@nfvexpress.com> From: Akshay Jaggi Date: Thu, 2 Feb 2017 23:37:02 +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) Cc: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , 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: Thu, 02 Feb 2017 23:43:47 -0000 [-Alex] Hi Roger, Did this get solved with the change you submitted to Xen? On 25 January 2017 at 11:58, Alexander Nusov wrote: > Cool, many thanks! > > -- > Alex > > ---- On Wed, 25 Jan 2017 14:50:51 +0300 *Roger Pau Monn=C3=A9 > >* wrote ---- > > On Wed, Jan 25, 2017 at 02:20:55PM +0300, Alexander Nusov wrote: > > Got it, thanks. > > > > > > > > I found a workaround to avoid XENBUS delay in Linux DomUs by adding > xen_platform_pci =3D 0 to the configuration file. > > > > So FreeBSD 11.0 Dom0 can boot Linux guests and Windows Server (FreeBSD > DomU still stuck on xenbusb_nop_confighook_cb) from QCOW2 images (also > works with QCOW2 overlay images) > > > > On FreeBSD you can boot with QCOW2 by not setting "xen_platform_pci =3D 0= " > on the > guest config file and adding "hw.xen.disable_pv_disks=3D1" to the > /boot/loader.conf file of the guest. This will prevent FreeBSD from using > the > PV disk, but you will still get the PV network interfaces. > > > > > Can you tell me please what is the disadvantage of not using > /dev/xen/vbd devices and drivers in guests? like slow I/O? > > Slow IO only. > > > May it lead to data corruption? > > No. > > >