From owner-freebsd-xen@freebsd.org Sat Aug 25 16:55:18 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66BA41090447 for ; Sat, 25 Aug 2018 16:55:18 +0000 (UTC) (envelope-from kai_otto@duckster.net) Received: from woodhouse.mariphil-volunteers.com (woodhouse.mariphil-volunteers.com [IPv6:2a03:4000:10:14::dead:beef]) by mx1.freebsd.org (Postfix) with ESMTP id D837A79974; Sat, 25 Aug 2018 16:55:17 +0000 (UTC) (envelope-from kai_otto@duckster.net) Received: from localhost (localhost [127.0.0.1]) by woodhouse.mariphil-volunteers.com (Postfix) with ESMTP id 340613FE; Sat, 25 Aug 2018 18:56:36 +0200 (CEST) X-Virus-Scanned: amavisd-new at woodhouse.mariphil-volunteers.com Received: from woodhouse.mariphil-volunteers.com ([127.0.0.1]) by localhost (woodhouse.mariphil-volunteers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E8wVq-cD7Ov9; Sat, 25 Aug 2018 18:56:15 +0200 (CEST) Received: from [IPv6:2001:16b8:2211:6e0:2c60:5ab1:74a7:1d94] (200116b8221106e02c605ab174a71d94.dip.versatel-1u1.de [IPv6:2001:16b8:2211:6e0:2c60:5ab1:74a7:1d94]) by woodhouse.mariphil-volunteers.com (Postfix) with ESMTPSA id 3F1722C3; Sat, 25 Aug 2018 18:56:15 +0200 (CEST) Subject: Re: HEADS UP: merged PVHv2 support and future plans To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= References: <20180719090444.jojyziar2c6wy735@mac> <20180730101924.aatt5ug33kg6dfil@mac.bytemobile.com> <3781a579-f00f-96fd-8f73-f3f344cd0aad@duckster.net> <20180813171954.2nilwiwsq6yyji66@mac> Cc: freebsd-xen@freebsd.org From: Kai Otto Message-ID: <9d28c30b-36f5-4533-c9b4-e40dca3c1621@duckster.net> Date: Sat, 25 Aug 2018 18:54:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180813171954.2nilwiwsq6yyji66@mac> Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.27 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: Sat, 25 Aug 2018 16:55:18 -0000 On 13/08/18 19:19, Roger Pau Monné wrote: > On Mon, Aug 13, 2018 at 05:24:04PM +0200, Kai Otto wrote: >> On 30/07/18 12:19, Roger Pau Monné wrote: >>> Packages for Xen 4.11 are now available in pkg. >>> >>> Remember that in order to use those you need a very recent FreeBSD >>> kernel (r336475 or newer) and the Xen command line has slightly changed, >>> so dom0=pvh must be used instead of dom0pvh in order to boot. I will >>> see about changing this in the handbook. >>> >>> Roger. >>> _______________________________________________ >>> freebsd-xen@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-xen >>> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >>> >> >> Hi Roger, >> I tried to get some VMs running on >> FreeBSD-12.0-CURRENT-amd64-20180802-r337160. >> System is a Supermicro X9DRi-LN4F+ mainboard with dual Intel E5-2680v2 >> (ivy bridge). [...] >> When using xen-tools411/xen-kernel411, I can boot without problems, but >> when running "xl create", neither a PVH nor HVM config work (see configs >> and logs attached). >> They both throw "libxl: info: >> libxl_create.c:109:libxl__domain_build_info_setdefault: qemu-xen is >> unavailable, using qemu-xen-traditional instead: No such file or directory" > > Hello, > > This is a mistake of the port makefile which should be fixed in > r477080 that I've just committed. I hope updated packages will be > generated soon. Thanks for the testing! > Hello again :-) Today I gave it another try with FreeBSD 12.0-ALPHA3 r338287 and the current packages for xen-tools411 and xen-kernel411. Sadly, I didn't get very far, even with the above bug being fixed. When attempting to start a HVM config, the console (xl console ) stays empty and unresponsive. Connecting via vnc, the screen only shows this message: "Guest has not initialized the display (yet)". When repeatedly running 'xl list', I can see that the domU almost consumes 1 second of CPU per second walltime. Trying out PVH, the console also doesn't show any sign of life, and VNC says: "This VM has no graphic display device." Running 'xl list' shows, that the domU consumed about 1.4s of CPU, and then switched to 'blocked' state. I can't see any errors in the log file either. Do you or anyone else have a working .cfg file that you could share, or any ideas what might be going wrong? - Kai