All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Matt Ayres <matta@tektonic.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A few outstanding xenstore/hotplug issues...
Date: Mon, 05 Jun 2006 15:48:33 -0500	[thread overview]
Message-ID: <448498A1.9030605@us.ibm.com> (raw)
In-Reply-To: <4484479F.5070500@tektonic.net>

Matt Ayres wrote:
> Greetings!
>
> I am still noticing a few issues related to xenstore and hotplug.
>
> 1) xenstored will periodically die.  I do have xenstore tracing 
> enabled, but not much is shown.  A transaction is running one second 
> and then nothing (no "FATAL ERROR" or anything). This does not happen 
> very frequently, but does happen now and then. As is known, once 
> xenstored dies the only way to get it running again is with a reboot. 
> A bad effect lies in the fact that domains can't be shutdown properly 
> without xenstored running!

Define "die".  Does it seg fault?  Can you try to repro with ulimit -c 
unlimited and check / to see if there's a core?

If it doesn't drop a core, that is also useful to know as that would 
suggest an exit() of some sort (although no message is rather odd!).

> 2) I get the old "Cannot connect VBD" on boot-up while running 
> xendomains start, I'd assume due to xenstore getting bogged down. It's 
> completely random as to which domains it will do it to.  I've worked 
> around this by having xendomains run from init.d and then also re-run 
> it from rc.local to start all the domains that didn't start the first 
> time.  Even doing this causes some domains to not start properly 
> sometimes (it seems based on how many failed to start the first time).

What changeset are you using and do you have any custom patches going?  
Have you ever seen this without xendomains?

> I remember reading that xenstore is getting an overhaul in the near 
> future and want to know if these are "known issues" and if I should 
> bother submitting bug reports or if I should just sit tight and watch 
> the lists.

I'm not aware of any overhaul although that doesn't mean it isn't 
happening.  I'd appreciate knowing if anyone was planning on doing this 
myself.

Regards,

Anthony Liguori

> Thank you,
> Matt Ayres
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-06-05 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 15:02 A few outstanding xenstore/hotplug issues Matt Ayres
2006-06-05 20:48 ` Anthony Liguori [this message]
2006-06-06 10:57 ` Ewan Mellor
2006-06-06 13:30   ` Matt Ayres

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=448498A1.9030605@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=matta@tektonic.net \
    --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.