From owner-freebsd-xen@freebsd.org Mon Sep 3 11:48:47 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 C3210FE683D for ; Mon, 3 Sep 2018 11:48:47 +0000 (UTC) (envelope-from prvs=7776ac630=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D90280B1C for ; Mon, 3 Sep 2018 11:48:46 +0000 (UTC) (envelope-from prvs=7776ac630=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.53,324,1531785600"; d="scan'208";a="78478354" Date: Mon, 3 Sep 2018 13:45:02 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Steven Friedrich CC: Subject: Re: Using xen host on freebsd, is com1 the only way to attach to dom0? Message-ID: <20180903114502.aduvblaqomjsitga@mac.bytemobile.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To AMSPEX02CL02.citrite.net (10.69.22.126) 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: Mon, 03 Sep 2018 11:48:47 -0000 On Fri, Aug 31, 2018 at 11:12:30PM -0400, Steven Friedrich wrote: > I can boot a xen kernel, but it appears it doesn't acquire a DHCP address > from my router. Does this mean that the box doesn't boot correctly, or just that the network card is not working when running under Xen? > Someone suggested using vga=current,keep on xen_cmdline, > but I'm unsure of the valid xen_cmdline arguments. The best option would be to hook a serial cable and get the output from the serial console. The list of valid xen_cmdline can be found here for the 4.11 ports: http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html Or here if you are using the 4.7 port: http://xenbits.xen.org/docs/4.7-testing/misc/xen-command-line.html > Do I have to configure and build a FreeBSD kernel or just use what the xen > meta-port builds? You don't have to build a specific kernel to run FreeBSD as Dom0, just using the GENERIC one from either 11.X or HEAD should work. Roger. From owner-freebsd-xen@freebsd.org Mon Sep 3 11:50:07 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 0F145FE6892 for ; Mon, 3 Sep 2018 11:50:07 +0000 (UTC) (envelope-from royger@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B684280B87; Mon, 3 Sep 2018 11:50:06 +0000 (UTC) (envelope-from royger@FreeBSD.org) Received: from localhost (247.red-88-3-116.dynamicip.rima-tde.net [88.3.116.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id E02C2215BE; Mon, 3 Sep 2018 11:50:05 +0000 (UTC) (envelope-from royger@FreeBSD.org) Date: Mon, 3 Sep 2018 13:49:58 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Kai Otto Cc: freebsd-xen@freebsd.org Subject: Re: HEADS UP: merged PVHv2 support and future plans Message-ID: <20180903114958.liefruwefijv66rv@mac.bytemobile.com> References: <20180719090444.jojyziar2c6wy735@mac> <20180730101924.aatt5ug33kg6dfil@mac.bytemobile.com> <3781a579-f00f-96fd-8f73-f3f344cd0aad@duckster.net> <20180813171954.2nilwiwsq6yyji66@mac> <9d28c30b-36f5-4533-c9b4-e40dca3c1621@duckster.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9d28c30b-36f5-4533-c9b4-e40dca3c1621@duckster.net> User-Agent: NeoMutt/20180716 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: Mon, 03 Sep 2018 11:50:07 -0000 On Sat, Aug 25, 2018 at 06:54:54PM +0200, Kai Otto wrote: > 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)". I think this should be fixed by r477953, please make sure you have the following package installed: xen-tools411-4.11.0_4 > 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. Can you paste the config file you are using to create the PVH guest? And which OS/version are you trying to boot as PVH? Roger.