This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Full virtualization with Pacifica crashes

To: Alexander Osthof <aosthof@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Full virtualization with Pacifica crashes
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Tue, 25 Apr 2006 15:40:46 +0200
Delivery-date: Tue, 25 Apr 2006 06:37:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200604251520.59763.aosthof@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200604251520.59763.aosthof@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Mardi 25 Avril 2006 15:20, Alexander Osthof a écrit :
> 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.
>   (XEN) domain_crash called from shadow_public.c:1564
>   (XEN) Domain 1 reported crashed by domain 0 on cpu#0:
> If I specify explicitely the amount of memory to be used by dom0, no error
> message appears, but the screen wents black, too. So I don't really know if
> to blame shadow_public.c and thus memory mapping respectively.
> Have you ever been successful in running such a full virtualized guest
> domain on a Pacifica system, or do you have a clue or a secret tip how to
> manage to get this done?
> Attached is the config file for the guest domain.
Your disk= configuration line seems a little bit strange: you are using a 
non-hvm configuration.

At this time, hvm only accepts a file as a disk image.  You can't use a 
partition nor a disk!


Xen-devel mailing list