Date: Mon, 04 May 2015 16:24:35 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <royger@FreeBSD.org> To: Roman Bogorodskiy <novel@FreeBSD.org> Cc: freebsd-virtualization@freebsd.org, bapt@freebsd.org Subject: Re: xen_kernel, console and X11 Message-ID: <55478123.3050807@FreeBSD.org> In-Reply-To: <20150504140727.GA983@kloomba> References: <20150502154340.GA8333@kloomba> <55473E2A.3020306@FreeBSD.org> <20150504140727.GA983@kloomba>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55478123.3050807>