All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xend bug? restart = 'never'
Date: Tue, 11 Oct 2005 13:59:35 -0500	[thread overview]
Message-ID: <1129057175.31509.17.camel@dbarrera_tp> (raw)
In-Reply-To: <20051010235835.GD6264@linford.intra>

On Tue, 2005-10-11 at 00:58 +0100, Ewan Mellor wrote:
> On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote:
> 
> > Hello,
> > 
> > I'm observing a situation where domU crashes and xend continuously tries 
> > to restart it.  For example, I have to write commands like this to 
> > actually get it to stop:
> > 
> > for i in `seq 80 90`; do xm destroy $i; done
> > 
> > I've tried adding restart = "never" and restart = 'never' to the domain 
> > config file (the file that gets passed to `xm create`).  Is this a known 
> > issue?  Am I doing something wrong?

I don't know if this is the same thing, but I noticed that my guest
domain (vm1) seems to have died twice and resurrected, leaving zombies
behind.

x235:~ # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       121    0      1  r-----   3333.5
Zombie-vm1         4         0    1      1  ----cd      0.3
Zombie-1-vm1       5         0    1      1  ----cd      0.3
vm1                6       126    1      1  -b----    745.7
vm2                7       126    1      1  -b----    866.3

I am also seeing this messages on 'xm dmesg':
(XEN) (file=/tmp/xen-unstable.hg/xen/include/asm/mm.h, line=203) Error
pfn 0: rd=ff1ab080, od=ffbfb080, caf=80000002, taf=f0000002
(XEN) DOM2: (file=mm.c, line=350) Could not get page ref for pfn 0
(XEN) DOM2: (file=mm.c, line=2220) Could not get page for mach->phys
update
(XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB.
expected dom 0)
(XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no
reservation headroom (32567,32768) or provided a bad grant ref
(00000000) or is dying (11)
(XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB.
expected dom 0)
(XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no
reservation headroom (32567,32768) or provided a bad grant ref
(00000000) or is dying (11)
(XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB.
expected dom 0)
(XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no
reservation headroom (32567,32768) or provided a bad grant ref
(00000000) or is dying (11)


> 
> I've assigned this bug #309.
> 
> Ewan.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> 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

  reply	other threads:[~2005-10-11 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 18:53 xend bug? restart = 'never' Jonathan M. McCune
2005-10-10 19:41 ` Ewan Mellor
2005-10-10 22:45   ` Ewan Mellor
2005-10-10 23:58 ` Ewan Mellor
2005-10-11 18:59   ` David F Barrera [this message]
2005-10-11 22:50   ` Khoa Huynh

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=1129057175.31509.17.camel@dbarrera_tp \
    --to=dfbp@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /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.