WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Guest domains dying and resurrecting

Thanks for the reply. My concern is why the domains are crashing. I'll
try to get more detail, as I saw the same situation this morning on the
same machine.

On Tue, 2005-10-11 at 17:36 -0500, Khoa Huynh wrote:
> dfbp@xxxxxxxxxxxxxxxxxxxxxxx wrote on 10/11/2005 04:28:56 PM:
> 
> > changeset:   7313:4e335372ace8
> > tag:         tip
> > parent:      7312:713328270fb3
> > parent:      7308:959d33fbd660
> > user:        emellor@ewan
> > date:        Tue Oct 11 09:23:19 2005 +0100
> > summary:     Merged.
> >
> > Machine: IBM xSeries 235, 1GB RAM, SCSI drives.
> >
> > This is what 'xm list' shows initially:
> >
> > Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> > Domain-0           0       120    0      1  r-----    899.8
> > vm1                1       127    1      1  -b----    684.8
> > vm2                2       127    1      1  -b----    555.7
> >
> > Later on, the domain IDs have incremented. I have neither manually
> > stopped nor started any guest domains:
> >
> > Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
> > Domain-0           0       121    0      1  r-----   1171.5
> > vm1                3       126    1      1  -b----    163.4
> > vm2                5       126    1      1  -b----     11.0
> >
> 
> This is because the domains crashed and then were restarted.
> In the domain config file (in /etc/xen), the default is:
> on_crash = restart
> You can set on_crash = preserve to prevent the domains from
> being restarted after they crash.
> 
> >
> > x235:/tmp/xen-unstable.hg # xm dmesg
> > (XEN)  Phys-Mach map: c0633000->c0652400
> > (XEN)  Start info:    c0653000->c0654000
> > (XEN)  Page tables:   c0654000->c0657000
> > (XEN)  Boot stack:    c0657000->c0658000
> > (XEN)  TOTAL:         c0000000->c0800000
> > (XEN)  ENTRY ADDRESS: c0100000
> > (XEN) Scrubbing Free RAM: ...........done.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> > input to Xen).
> > (XEN) DOM1: (file=mm.c, line=462) Non-privileged attempt to map I/O
> > space 00000000
> 
> I have seen this error previously on my system.  After making sure that
> the domain config file is correct(several options have been changed),
> and doing a 'make mrproper' before rebuilding Xen stuff, this error
> went away (at least on my system).
> 
> Regards,
> 
> Khoa H.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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

<Prev in Thread] Current Thread [Next in Thread>