From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Full virtualization with Pacifica crashes Date: 25 Apr 2006 16:21:40 +0200 Message-ID: References: <200604251520.59763.aosthof@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <200604251520.59763.aosthof@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alexander Osthof Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Alexander Osthof writes: > I'm currently trying to get Xen working on an Pacifica system. But each time I > try to start a fully virtualized guest domain, the system hangs just after > the start with a black screen (paravirtualization works, btw). > > I've also tried to monitor the system with the serial console, but I get > nearly no useful info. If I don't specify the memory used by dom0 (with boot > option "dom0_mem=xxx"), I can see the following error: > > Unable to open display. This means your $DISPLAY is wrong and it can't open the window and it probably goes downwards after that. The problem is that xend not xm tries to open the window and it not always gets all the environment variables needed for it. There were some fixes in this area but maybe they were not enough. One workaround is to restart xend on your current terminal to fix up its environment. Of course even with that it shouldn't hang, but error handling paths tend to be often undertested. -Andi