From owner-freebsd-xen@freebsd.org Thu Nov 5 14:10:47 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57725A26416 for ; Thu, 5 Nov 2015 14:10:47 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.232]) by mx1.freebsd.org (Postfix) with ESMTP id 1270A1E14 for ; Thu, 5 Nov 2015 14:10:46 +0000 (UTC) (envelope-from lausts@acm.org) Received: from [173.88.10.122] ([173.88.10.122:28153] helo=mail.laus.org) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 72/9C-15038-2236B365; Thu, 05 Nov 2015 14:09:39 +0000 Received: from [192.168.1.100] (laust2 [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id tA5E9c2Y003980 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 5 Nov 2015 09:09:38 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host laust2 [192.168.1.100] claimed to be [192.168.1.100] From: "Thomas Laus" Organization: ABB To: freebsd-xen@freebsd.org Date: Thu, 05 Nov 2015 09:09:33 -0500 Subject: Re: Does a Xen Dom0 require X to function Reply-to: lausts@acm.org Message-ID: <563B631D.22122.FDB9F@lausts.acm.org> Priority: normal In-reply-to: <56379E8A.3030701@citrix.com> References: <5633A2B0.22403.45280A@lausts.acm.org>, <56379E8A.3030701@citrix.com> X-mailer: Pegasus Mail for Windows (4.70) X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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: Thu, 05 Nov 2015 14:10:47 -0000 > So the VNC client attaches successfully to the server, but the output is > just a black screen? IMHO, that looks more like a guest or VNC issue > rather than a Xen/Qemu one. Have you tried different guest OSes and > different VNC clients? (TigerVNC Viewer has always worked fine for me). > > But regarding your question: no, Xen Dom0 doesn't require X at all in > order to run. > I tried other guest OS's and VNC clients with the same result and came to the conclusion that all of my guest OS's were not booting. All of my VNC clients displayed the name of the guest OS in the margin, but had a black screen. I looked at the 'xl list' billboard and the guest OS did not have a 'r' in the column. The startup log for all of the guests had this line: 'xen be core: can't open gnttab device' My guess is that the 'gnttab' device is critical to a guest startup. I could not find any reference to this item. What am I missing? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF