From: Jody Belka <lists-xen@pimb.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: fs-backend on -unstable
Date: Thu, 26 Mar 2009 00:02:37 +0000 [thread overview]
Message-ID: <20090326000237.GP13428@pimb.org> (raw)
In-Reply-To: <49CAB50A.8040205@goop.org>
On Wed, Mar 25, 2009 at 03:49:46PM -0700, Jeremy Fitzhardinge wrote:
> Jody Belka wrote:
> >On Wed, Mar 25, 2009 at 10:38:33PM +0100, Samuel Thibault wrote:
> >
> >>Jody Belka, le Wed 25 Mar 2009 19:17:30 +0000, a écrit :
> >>
> >>>Apologies; it seems that there's some bug somewhere that means fs-backend
> >>>doesn't work with a pvops-dom0.
> >>>
> >>It'd be good to report that on xen-unstable.
> >>
> >
> >So, as mentioned above, fs-backend isn't working on a pvops-dom0. With
> >non-pvops, running fs-backend looks like this:
> >
> >Connection to the xenbus deamon opened successfully.
> >XS transaction is 3
> >xenbus_printf (backend/vfs/exports/0/name) <= default.
> >Path changed backend/vfs/exports/requests
> >Awaiting next connection.
> >
> >
> >However, under pvops, this is all I get:
> >
> >Connection to the xenbus deamon opened successfully.
> >XS transaction is 3
> >xenbus_printf (backend/vfs/exports/0/name) <= default.
> >
> >
> >And stubdom's can't make a connection to it.
>
> Hm, I had it working not too long ago. But there are still some issues
> starting hvm domains, and maybe stubdoms are also affected.
>
> Does pv-grub work?
Ok, had to sort out creating a linux domain, as had nothing I could actually
try pv-grub with on the test-box in question :)
Anyway, having done so, pv-grub is working fine under pvops0
J
next prev parent reply other threads:[~2009-03-26 0:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090325165439.GH13428@pimb.org>
[not found] ` <20090325171822.GY5737@const.bordeaux.inria.fr>
[not found] ` <20090325175037.GI13428@pimb.org>
[not found] ` <20090325180655.GA8031@const.famille.thibault.fr>
[not found] ` <20090325181412.GJ13428@pimb.org>
[not found] ` <20090325182013.GA13718@const.famille.thibault.fr>
[not found] ` <20090325182501.GK13428@pimb.org>
[not found] ` <20090325191730.GM13428@pimb.org>
[not found] ` <20090325213833.GC13718@const.famille.thibault.fr>
2009-03-25 22:41 ` fs-backend on -unstable Jody Belka
2009-03-25 22:49 ` Jeremy Fitzhardinge
2009-03-26 0:02 ` Jody Belka [this message]
2009-03-26 0:05 ` Jeremy Fitzhardinge
2009-03-26 0:16 ` Jody Belka
2009-03-26 10:21 ` Stefano Stabellini
2009-03-26 12:18 ` Boris Derzhavets
2009-03-26 13:27 ` Jody Belka
2009-03-26 18:57 ` Jeremy Fitzhardinge
2009-03-26 21:18 ` Jody Belka
2009-03-26 22:03 ` Jeremy Fitzhardinge
2009-03-26 22:41 ` Jody Belka
2009-03-26 8:32 ` Boris Derzhavets
2009-03-26 18:39 ` Jeremy Fitzhardinge
2009-03-27 10:28 ` Boris Derzhavets
2009-03-26 14:54 ` Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) Boris Derzhavets
2009-03-26 16:14 ` Boris Derzhavets
2009-03-27 23:21 ` Jeremy Fitzhardinge
2009-03-28 8:41 ` Boris Derzhavets
2009-03-28 10:18 ` Boris Derzhavets
2009-03-28 11:45 ` Boris Derzhavets
2009-03-28 18:25 ` Boris Derzhavets
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=20090326000237.GP13428@pimb.org \
--to=lists-xen@pimb.org \
--cc=jeremy@goop.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.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.