From owner-freebsd-xen@freebsd.org Thu Nov 5 15:19:03 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 138D2A2733C for ; Thu, 5 Nov 2015 15:19:03 +0000 (UTC) (envelope-from prvs=7445e0bd4=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C04651235 for ; Thu, 5 Nov 2015 15:19:02 +0000 (UTC) (envelope-from prvs=7445e0bd4=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.20,248,1444694400"; d="scan'208";a="310585453" Subject: Re: Does a Xen Dom0 require X to function To: , References: <5633A2B0.22403.45280A@lausts.acm.org> <56379E8A.3030701@citrix.com> <563B631D.22122.FDB9F@lausts.acm.org> From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Message-ID: <563B7357.3040002@citrix.com> Date: Thu, 5 Nov 2015 16:18:47 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <563B631D.22122.FDB9F@lausts.acm.org> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 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 15:19:03 -0000 Hello, El 05/11/15 a les 15.09, Thomas Laus ha escrit: >> 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' Is there anything else in the Qemu logs? Also, can you post the output of `xl -vvv create ` and `xl list` while the domain is running? > 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? No, gnttab is not critical, Qemu should work without it. Roger.