From: Brian Hays <brian.hays@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Mike Wray <mike.wray@hpl.hp.com>, xen-devel@lists.xensource.com
Subject: Re: Xend stop/start
Date: Fri, 15 Apr 2005 19:40:22 -0400 [thread overview]
Message-ID: <e4ca66ec05041516406c604ef4@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3BCC@liverpoolst.ad.cl.cam.ac.uk>
Thanks!
Is there a workaround for the xend stop/start issue that won't
interrupt the domU's?
Brian
On 4/15/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > I've noticed that if I try to restart Xend via "/etc/init.d/xend stop"
> > then "/etc/init.d/xend start", I won't receive any errors but
> > then when trying to execute "xm" commands after the restart I
> > get error asking if Xend is started. Is there anything else I
> > need to make sure gets stopped/started with Xend?
>
> We know about this bug -- its top of the tool bug list.
>
> > Another question ... domU reboots -
> > I can only get a domU to come back up after issuing a reboot
> > from within it if I then do a "xm list" command from within
> > dom0 ...otherwise the status of the domU never changes to
> > --s-- , then to
> > ----- , then to -b---.
>
> I'll add this one to the list to investigate. I thought it had been got.
>
> > I currently have a cron job executing "xm list"
> > every couple of minutes. Is this going to be a problem? will
> > running that cron job cause any adverse reactions as far as
> > performance or the health of dom0?
>
> There's been reports of a slow memory leak in xend, which will be
> investigated.
>
> Thanks,
> Ian
>
next prev parent reply other threads:[~2005-04-15 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 22:25 Xend stop/start Ian Pratt
2005-04-15 23:40 ` Brian Hays [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 21:47 Brian Hays
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=e4ca66ec05041516406c604ef4@mail.gmail.com \
--to=brian.hays@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mike.wray@hpl.hp.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.