From owner-freebsd-virtualization@FreeBSD.ORG Mon May 4 14:16:59 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7BECE458; Mon, 4 May 2015 14:16:59 +0000 (UTC) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (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 F376E13D7; Mon, 4 May 2015 14:16:58 +0000 (UTC) Received: by labbd9 with SMTP id bd9so105146896lab.2; Mon, 04 May 2015 07:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=lSNGJ0Mega9alB1GAD7s3Y5vBpjXB80sD+LeenXLpSI=; b=zZTTvjsO9PwqiyOoGKhwKK8shNHTaZ+eLndz0LvbU2aWL9a90I3Bf0jQqpFE70OZ9M 7I2dEY0grLQAgTMi66SDkwjTeRCj4gyoLx49smCZS8irAfGevKf6Y0mHQV6L8ZrjZORn Fe64dLnphL7+pGOll0w4/g1+Vi72EMGEAuDYyQ5M20zJTHsxdzXjwiURuE3d+ZbwNuuN OLsQ/muu5Vd6upWVL7NqtEvAkO0LkYwKw9p0u9WDy/ynSgaghClvXY4LXfKMtTckfX5m mkdG83H9+OcOUDYpYZx3STLMBFc/0YMbAqYq96+Ced38YDDbSspMwYV8JdyxeeyryhX5 Asbw== X-Received: by 10.152.246.34 with SMTP id xt2mr14023440lac.110.1430749016185; Mon, 04 May 2015 07:16:56 -0700 (PDT) Received: from kloomba ([31.29.239.59]) by mx.google.com with ESMTPSA id wl9sm3385806lbb.11.2015.05.04.07.16.54 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2015 07:16:55 -0700 (PDT) Sender: Roman Bogorodskiy Date: Mon, 4 May 2015 17:16:46 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: freebsd-virtualization@freebsd.org, bapt@freebsd.org Subject: Re: xen_kernel, console and X11 Message-ID: <20150504140727.GA983@kloomba> References: <20150502154340.GA8333@kloomba> <55473E2A.3020306@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fig2xvG2VGoz8o/s" Content-Disposition: inline In-Reply-To: <55473E2A.3020306@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2015 14:16:59 -0000 --Fig2xvG2VGoz8o/s Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roger Pau Monn=E9 wrote: > Hello, >=20 > El 02/05/15 a les 17.43, Roman Bogorodskiy ha escrit: > > Hi, > >=20 > > I'm trying to get Xen running and following these instructions: > >=20 > > https://wiki.freebsd.org/Xen > >=20 > > and > >=20 > > http://wiki.xen.org/wiki/FreeBSD_Dom0 > >=20 > > I'm running two days old -CURRENT and ports. I've installed the > > emulators/xen port and followed instructions in pkg-message. > >=20 > > I'm having some problems with console. I'm wondering if it's possible to > > have X running on the same box running xen kernel? >=20 > It should be, although I had issues while using the vesa driver with a > FreeBSD Xen Dom0, mainly because Dom0 doesn't have access to the BDA and > EBDA, I'm working on fixing this in Xen upstream. >=20 > > My setup is as follows: > > =20 > > - Intel i5-4690 that supports IOMMU: > > $ sudo acpidump -t|grep DMAR > > DMAR: Length=3D128, Revision=3D1, Checksum=3D90, > > $ > > - vm.max_wired=3D-1 in /etc/sysctl.conf > > - xc0 "/usr/libexec/getty Pc" xterm on secure in > > /etc/ttys > >=20 > > In loader.conf I have: > >=20 > > xen_kernel=3D"/boot/xen" > > xen_cmdline=3D"dom0_mem=3D2048M dom0_max_vcpus=3D4 dom0pvh=3D1 com1=3D1= 15200,8n1 > > guest_loglvl=3Dall loglvl=3Dall console=3Dcom1" >=20 > So you are trying to use the serial console but you are not getting any > output? If that's not the case, please drop the com1 parameter and set > console=3Dvga. Sorry for confusion, actually 'console=3Dcom1' works for me. Initially I didn't realize that it doesn't display kernel messages and after some failed attempts to run startx and hard reboots it took much longer to see a login prompt because I have background fsck disabled. So, 'console=3Dcom1' works unless I do 'startx'. > Do you have anything else in your /boot/loader.conf apart from this two > lines? >=20 > >=20 > > With this setup I get my system booted and at some point I can see a > > login screen. When I type 'startx' the system freezes. Have to hard > > reboot it to get working again. >=20 > On which device do you get a login prompt? Is it xc0, ttyv0 or ttyu0? I get a login prompt on ttyv0. BTW, I use the nvidia driver. >=20 Roman Bogorodskiy --Fig2xvG2VGoz8o/s Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVR39NAAoJEMltX/4IwiJqmvMH/iPI91+x08QFlANhrFf5/zOH XFME7VoveDcph+nXoYeWqQLYt68R0odP3cs+FLUR6wFbTwGCWJxBanxlCtJRdYXU B68OpjleACKf0yr10dPX8Tg9KNdrzEm1Zyd4lru4TCo7m60t6oPeBmVWw1zjMB4o eniLq50646xWUNEUeuahNo33W9nOztLt8LqdJyvYVyRqKQa2k7vZc3Y0hG2dXWE7 xzRvYPSBkox3NjAdYDhF3Wp5F21a9NonfvLdqNb+HJIa6264CFIC3fgOKtcRCq0g t6SycciMg3UAmFSWr1rOe7HTblOeIVBq7sLIAWHuT55TAu3YI31ZWWgu0yWhxRI= =aKxx -----END PGP SIGNATURE----- --Fig2xvG2VGoz8o/s--