From owner-freebsd-xen@freebsd.org Wed Jan 25 11:58:28 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 B75BECBF4E3 for ; Wed, 25 Jan 2017 11:58:28 +0000 (UTC) (envelope-from alexander.nusov@nfvexpress.com) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A036C87E; Wed, 25 Jan 2017 11:58:28 +0000 (UTC) (envelope-from alexander.nusov@nfvexpress.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1485345501; s=zoho; d=nfvexpress.com; i=alexander.nusov@nfvexpress.com; h=Date:From:To:Cc:Message-Id:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=3517; bh=wqnR98HUL6+LWjuzrBc6jyUN1yDZV+19ylX7gfHL2+o=; b=YjWqoZhbhieCF3pwZU6P1Mc2bRGY3HlFCmqn/b4hRB/SZvgRFP1AGodDZ8UMBTnG iHY2lXEDpwTAXQMG3gw6N0rjY4GTMMFbriS2yuWcia6pdjplqP1hPzGXKSAIGSnKOm6 4GVxTPDQG0SWxu7aG9wFvc4TX5JWwYNcsuIuvbd4= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1485345499407371.2166860166391; Wed, 25 Jan 2017 03:58:19 -0800 (PST) Date: Wed, 25 Jan 2017 14:58:19 +0300 From: Alexander Nusov To: =?UTF-8?Q?=22Roger_Pau_Monn=C3=A9=22?= Cc: "Akshay Jaggi" , "FreeBSD-Xen" Message-Id: <159d57da8bb.e9fea5dc25161.6113276104371162720@nfvexpress.com> In-Reply-To: <20170125115051.sasgqxwgt47p7pwi@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> <159d55b6b65.dc9b3b1720453.5847395326743424395@nfvexpress.com> <20170125115051.sasgqxwgt47p7pwi@dhcp-3-221.uk.xensource.com> Subject: Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb) MIME-Version: 1.0 X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail 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 11:58:28 -0000 Cool, many thanks! -- Alex ---- On Wed, 25 Jan 2017 14:50:51 +0300 Roger Pau Monn=C3=A9 <roger.pau@= citrix.com> wrote ---- On Wed, Jan 25, 2017 at 02:20:55PM +0300, Alexander Nusov wrote:=20 > Got it, thanks.=20 >=20 >=20 >=20 > I found a workaround to avoid XENBUS delay in Linux DomUs by adding xe= n_platform_pci =3D 0 to the configuration file.=20 >=20 > 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 wor= ks with QCOW2 overlay images)=20 >=20 =20 On FreeBSD you can boot with QCOW2 by not setting "xen_platform_pci =3D 0" = on the=20 guest config file and adding "hw.xen.disable_pv_disks=3D1" to the=20 /boot/loader.conf file of the guest. This will prevent FreeBSD from using t= he=20 PV disk, but you will still get the PV network interfaces.=20 =20 >=20 > Can you tell me please what is the disadvantage of not using /dev/xen/= vbd devices and drivers in guests? like slow I/O?=20 =20 Slow IO only.=20 =20 > May it lead to data corruption?=20 =20 No.=20