From: Andi Kleen <ak@suse.de>
To: Alexander Osthof <aosthof@suse.de>
Cc: Xen-devel@lists.xensource.com
Subject: Re: Full virtualization with Pacifica crashes
Date: 25 Apr 2006 16:21:40 +0200 [thread overview]
Message-ID: <p73slo191mz.fsf@bragg.suse.de> (raw)
In-Reply-To: <200604251520.59763.aosthof@suse.de>
Alexander Osthof <aosthof@suse.de> 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
next prev parent reply other threads:[~2006-04-25 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 13:20 Full virtualization with Pacifica crashes Alexander Osthof
2006-04-25 13:40 ` Tristan Gingold
2006-04-25 14:21 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-25 13:41 Ian Pratt
2006-04-25 13:52 ` Tristan Gingold
2006-04-25 18:38 ` Ray Bryant
2006-04-25 21:26 Ian Pratt
2006-04-27 16:41 Woller, Thomas
2006-04-28 11:48 ` Alexander Osthof
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73slo191mz.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=Xen-devel@lists.xensource.com \
--cc=aosthof@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.