All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian Hays" <brian.hays@gmail.com>
To: Ewan Mellor <ewan@xensource.com>,
	Brian Hays <brian.hays@gmail.com>,
	xen-devel@lists.xensource.com
Subject: Re: DomU not rebooting in 3.0.1
Date: Mon, 27 Feb 2006 14:10:24 -0500	[thread overview]
Message-ID: <e4ca66ec0602271110v48a32044jac6e38df8a1daa48@mail.gmail.com> (raw)
In-Reply-To: <20060227190613.GA24879@dargo.dague.pvt>


[-- Attachment #1.1: Type: text/plain, Size: 1582 bytes --]

My domU is on the same physical CPU as dom0 but still doesn't come back from
reboots.

Brian

On 2/27/06, Sean Dague <japh@us.ibm.com> wrote:
>
> On Mon, Feb 27, 2006 at 03:33:17PM +0000, Ewan Mellor wrote:
> > On Sat, Feb 25, 2006 at 11:31:57AM -0500, Brian Hays wrote:
> >
> > > In 3.0.1 it appears that reboots from within a domU result in the domU
> > > shutting down but not coming back up.
> > >
> > > /var/log/xen-hotplug.log reports something similar to "xenstore-list:
> > > could not read path backend/vbd/40"
> > >
> > > Attempts to manually start the domU up again via "xm create" fail
> until
> > > first running "xenstore-rm backend/vbd/40"
> > >
> > > This has happened on several occasions within different domU's on
> > > different machines. Is there a known workaround... Is this already
> fixed
> > > in unstable?
> >
> > This is being tracked as bug #514.  I think I have a fix, which should
> be in
> > today, all being well.
>
> Ewan, I didn't notice 514, but I submitted a related bug
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=549.  It appears
> that
> the big deciding factor on whether or not I see the race is is the DomU
> that
> is rebooting running on a fully independant CPU from Dom0.  If it is, it
> breaks every time, if it isn't (i.e. it is on the *same* phys CPU as Dom0)
> it works every time.
>
>         -Sean
>
> --
> Sean Dague
> IBM Linux Technology Center                     email: japh@us.ibm.com
> Open Hypervisor Team                           alt: sldague@us.ibm.com
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2421 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2006-02-27 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 16:31 DomU not rebooting in 3.0.1 Brian Hays
2006-02-27 15:33 ` Ewan Mellor
2006-02-27 19:06   ` Sean Dague
2006-02-27 19:10     ` Brian Hays [this message]
2006-02-27 19:13     ` Ewan Mellor
2006-02-27 19:37       ` Sean Dague
2006-03-01 23:14         ` Tiago Teresa Teodosio
2006-03-01 23:32     ` Ewan Mellor

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=e4ca66ec0602271110v48a32044jac6e38df8a1daa48@mail.gmail.com \
    --to=brian.hays@gmail.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.