Xen devel - Apr 2006 - Full virtualization with Pacifica crashes

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.

-- 
Alexander Osthof				R&D SI Architecture Maintenance
SUSE Linux Products GmbH, Maxfeldstr.5		Phone: +49-911-74053-285
D-90409 Nuernberg				EMail: aosthof@suse.de



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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!

Tristan.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> 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!
That''s not true at all. Both LVM and raw partitions work fine as well
as
files.

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Le Mardi 25 Avril 2006 15:41, Ian Pratt a écrit :
> > 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!
>
> That''s not true at all. Both LVM and raw partitions work fine as
well as
> files.
Humm, maybe I spoke to fast.  I didn''t check recently, but about 1
month ago,
I had such a problem with xen/ia64+VTi.

Tristan.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Tuesday 25 April 2006 08:41, Ian Pratt wrote:
> > 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!
>
> That''s not true at all. Both LVM and raw partitions work fine as
well as
> files.
>
How does one set that up in the config file?    In particular, does one 
specify the device as a phys or an ioemu device?
> Ian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
-- 
Ray Bryant
AMD Performance Labs                   Austin, Tx
512-602-0038 (o)                 512-507-7807 (c)


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> > > 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!
> >
> > That''s not true at all. Both LVM and raw partitions work 
> fine as well 
> > as files.
> >
> 
> How does one set that up in the config file?    In 
> particular, does one 
> specify the device as a phys or an ioemu device?
You specify it exactly the same was as you do for pv devices, just
putting the ioemu: prefix on the 2nd (guest target device) stanza. e.g.

  disk = [ ''phy:/dev/vg/my_disk, ioemu:hda, w'' ]

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> 
> Attached is the config file for the guest domain.
Specify cpus= explicitly for core 0 (cpus = "0") for your guest, we
are
having issues with using a Dom0 SMP with 64bit hv, and then attempting
to start/pin unmodified guests to cores>0 (system reboots).  32bit hv
works fine with SMP Dom0/hv on cores>0.

Also, try using recommendation by Ian for phys
>   disk = [ ''phy:/dev/vg/my_disk, ioemu:hda, w'' ]
I''ve installed win2003 server from cdrom=iso to physical disk /dev/hdb
(100Gig partition) with this method, so it does work for SVM, using
core0 for guest.
disk=[''phy:/dev/hdb,ioemu:hda,w'']
Specifically.

Can you post output from /proc/cpuinfo from Dom0?

Can you provide last line on serial output where the system hangs when
starting up an unmodified guest? (if no valid output, that''s fine the
cpuinfo will help).

thanks
tom


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Am Donnerstag, 27. April 2006 18:41 schrieb Woller,
Thomas:
> > Attached is the config file for the guest domain.
>
> Specify cpus= explicitly for core 0 (cpus = "0") for your guest,
we are
> having issues with using a Dom0 SMP with 64bit hv, and then attempting
> to start/pin unmodified guests to cores>0 (system reboots).  32bit hv
> works fine with SMP Dom0/hv on cores>0.
>
Thanks a lot, that solved the problem. I''m able now to install
unmodified
guests.
> Also, try using recommendation by Ian for phys
>
> >   disk = [ ''phy:/dev/vg/my_disk, ioemu:hda, w'' ]
>
> I''ve installed win2003 server from cdrom=iso to physical disk
/dev/hdb
> (100Gig partition) with this method, so it does work for SVM, using
> core0 for guest.
> disk=[''phy:/dev/hdb,ioemu:hda,w'']
> Specifically.
>
> Can you post output from /proc/cpuinfo from Dom0?
>
I think you don''t need the output anymore, do you?
> Can you provide last line on serial output where the system hangs when
> starting up an unmodified guest? (if no valid output, that''s fine
the
> cpuinfo will help).
>
> thanks
> tom
Kind regards, 
Alex


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel