From owner-freebsd-virtualization@FreeBSD.ORG Mon May 4 14:24:40 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 DCDEB834; Mon, 4 May 2015 14:24:39 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 7CD91151A; Mon, 4 May 2015 14:24:39 +0000 (UTC) Received: by wiun10 with SMTP id n10so111995312wiu.1; Mon, 04 May 2015 07:24:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OaiOPZvdvpLmVra1mOunEQX0xiuCwug3TpDzp5RxlB4=; b=TS91gjUceogAPQumF0/PkScnZ0VNbaKJ264nLEsUeLoD8cGKVHHdWVZEOe7hcKjgru NdHmAFIdLHobF04wXwlRUCBurHwsYeL6X9AicoXAuGSJTXEg30d9fIrT8u9tsSuEvPCL JOYhkayX3MlIAY4HSLe7yfEAiWihKO+CV4bA+4yE7YNA4l/03xG6SfQ2WibS9Hi0gTXU KIGImqIyFpjXpFBWhBUDo3zrQppYp2l4oY9JI5rweKHWvKuVVckYTqz/4S+cUNXrXtVz 7iZyb6soORyEAkb2xGztFx9ApjJ9fwfXnEp+/yckGts7+LNVNX4pfTzsFifKT5663aFV lP6w== X-Received: by 10.180.98.195 with SMTP id ek3mr19961719wib.57.1430749477420; Mon, 04 May 2015 07:24:37 -0700 (PDT) Received: from [172.16.1.30] (53.Red-88-9-170.dynamicIP.rima-tde.net. [88.9.170.53]) by mx.google.com with ESMTPSA id dz4sm11440393wib.17.2015.05.04.07.24.36 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2015 07:24:36 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Message-ID: <55478123.3050807@FreeBSD.org> Date: Mon, 04 May 2015 16:24:35 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Roman Bogorodskiy CC: freebsd-virtualization@freebsd.org, bapt@freebsd.org Subject: Re: xen_kernel, console and X11 References: <20150502154340.GA8333@kloomba> <55473E2A.3020306@FreeBSD.org> <20150504140727.GA983@kloomba> In-Reply-To: <20150504140727.GA983@kloomba> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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:24:40 -0000 Hello, El 04/05/15 a les 16.16, Roman Bogorodskiy ha escrit: > Roger Pau Monné wrote: > >> Hello, >> >> El 02/05/15 a les 17.43, Roman Bogorodskiy ha escrit: >>> Hi, >>> >>> I'm trying to get Xen running and following these instructions: >>> >>> https://wiki.freebsd.org/Xen >>> >>> and >>> >>> http://wiki.xen.org/wiki/FreeBSD_Dom0 >>> >>> I'm running two days old -CURRENT and ports. I've installed the >>> emulators/xen port and followed instructions in pkg-message. >>> >>> 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? >> >> 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. >> >>> My setup is as follows: >>> >>> - Intel i5-4690 that supports IOMMU: >>> $ sudo acpidump -t|grep DMAR >>> DMAR: Length=128, Revision=1, Checksum=90, >>> $ >>> - vm.max_wired=-1 in /etc/sysctl.conf >>> - xc0 "/usr/libexec/getty Pc" xterm on secure in >>> /etc/ttys >>> >>> In loader.conf I have: >>> >>> xen_kernel="/boot/xen" >>> xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 >>> guest_loglvl=all loglvl=all console=com1" >> >> 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=vga. > > Sorry for confusion, actually 'console=com1' 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=com1' works unless I do 'startx'. I'm not sure I would call it working if you don't get any kernel messages while booting. What happens if you set console=vga? > >> Do you have anything else in your /boot/loader.conf apart from this two >> lines? >> >>> >>> 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. >> >> 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. Another user also reported a similar problem with Xen and X, and it was solved by the following patch: https://people.freebsd.org/~royger/0001-xen-introduce-a-newbus-function-to-allocate-unused-m.patch Could you apply it and rebuild your kernel to see if that also solves your issues? Roger.