From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Schinker <ba1020@homie.homelinux.net>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16
Date: Mon, 24 Oct 2016 19:16:31 +0100 [thread overview]
Message-ID: <20161024181631.GP30231@citrix.com> (raw)
In-Reply-To: <170201836.333.1477331870070.JavaMail.zimbra@homie.homelinux.net>
On Mon, Oct 24, 2016 at 06:57:50PM +0100, Juergen Schinker wrote:
>
> >> Then why don't you write an Tes Report ?
> >
> > Juergen, please be courteous to fellow users. :-)
> >
> sorry
>
> > There could be many reasons why Pry didn't send out a report. I think we
> > should be grateful that he took the time to response to the issue you
> > discovered.
> >
> >>
> >> and I tested "your" Flags they set mostly Feature which are defaults
> >> and you didn't test or report
> >>
> >> so what is the Point?
> >>
> >> Xen should compile cleanly with none or all Flags set...
> >>
> >
> > I bet to differ.
> >
> > Those flags exist for a reason -- so that users can configure Xen as
> > they see fit.
> >
> > It is quite often downstream packagers need to tune the paths to fit
> > into the file system hierarchy of his or her distro.
> >
>
> but you will not say that you have to have a minimum set of Flags and without them it will not compile?
I think the expectation is that ./configure will do necessary probing.
If it discovers something is missing, it stops.
So I guess the "minimum set of flags" should be "none".
But, there is a caveat: Xen's configure can't cover completely what is
needed by other software we need, so there could be some fallouts.
In any case, fixing the build is probably the easier ones of all the
bugs we face.
> >
>
> >> I don't know which systemd service starts xentored coz it refuses
> >> intentionally the restart and is not supposed to be an service on its
> >> own
> >>
> >> maybe the devs can shed some light
> >
> > There are a bunch of systemd service files under
> > tools/hotplug/Linux/systemd. I think you should build and install all of
> > them. The logic in those scripts should sort out all the dependencies
> > all by themselves.
>
> hm but none of the others services calls xenstored so
>
There is one called xenstored.service.
> is xenstore supposed to start just because it is systemd enabled?
>
I think so -- when you configure it properly when building Xen, those
files will be properly installed to the desired location of your test
host. Make sure you have systemd development package(s) installed on
your build host.
My limited experience with those script shows that they work just fine.
I don't remember making any special adjustment to them.
Wei.
> J
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-24 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 20:04 Test Xen 4.8 RC3 FULL SUCCESS 21.10.16 Pry Mar
2016-10-24 13:14 ` Juergen Schinker
2016-10-24 13:27 ` Wei Liu
2016-10-24 17:57 ` Juergen Schinker
2016-10-24 18:16 ` Wei Liu [this message]
2016-10-24 18:49 ` Juergen Schinker
2016-10-25 9:42 ` Wei Liu
2016-10-25 12:55 ` Juergen Schinker
2016-10-25 13:22 ` Wei Liu
2016-10-24 19:42 ` Pry Mar
-- strict thread matches above, loose matches on Subject: below --
2016-10-21 21:27 Juergen Schinker
2016-10-26 16:09 ` Dario Faggioli
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=20161024181631.GP30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ba1020@homie.homelinux.net \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).