From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Schinker <ba1020@homie.homelinux.net>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH for-4.8] ipxe: update to newer commit
Date: Thu, 13 Oct 2016 17:45:07 +0100 [thread overview]
Message-ID: <20161013164507.GO3687@citrix.com> (raw)
In-Reply-To: <1633715062.155.1476375972276.JavaMail.zimbra@homie.homelinux.net>
Add back xen-devel
On Thu, Oct 13, 2016 at 05:26:12PM +0100, Juergen Schinker wrote:
>
>
> ----- On 13 Oct, 2016, at 14:53, Wei Liu wei.liu2@citrix.com wrote:
>
> > Hmm... I think no amount of hand-holding is going to help you.
> >
> > In your situation I would suggest you to use various tools available on
> > Linux to figure out why it hang. Tools like strace, ldd, gdb etc, but
> > that's going to be rather technical and the finding isn't going to be
> > useful or interesting to you in the long run. The hang is likely due to
> > mismatch in various bits in the system.
> >
> > I think your best bet is to have a clean installation of Xen.
> >
> > Wei.
>
> I don't want hand holding - this is a bug report dude
>
> I;m very technical and it is useful and interesting
Sorry if that came out offensive to you -- I didn't mean to.
If you're really interested in going down this rabbit hole, I think you
will need to do the following:
1. Make sure all the Xen related libraries are properly installed into
the location you specified when building Xen.
2. Use ldd to check if xl / xenstored are the ones you installed.
3. Make sure they can find all the libraries (ldd should be handy).
4. Use strace to identify when and where they hang.
There is a lot information about Xen in general on wiki.xenproject.org.
If you need to get more information about the architecture / moving
parts of Xen, check out the wiki.
After identifying why they don't work, you will have a lot more
information to either submit a detailed bug report or start hunting down
these issues for fun and profit (!). :-)
There isn't enough information in the current report for me to tell what
goes wrong in your setup. The basic life cycle of running Xen (the
operations in your bug report) is constantly tested in Xen project CI
and all developers -- neither CI nor humans spotted bugs in those areas
in the past week.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-13 16:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 12:50 [PATCH for-4.8] ipxe: update to newer commit Wei Liu
2016-10-10 15:34 ` Ian Jackson
2016-10-10 15:44 ` Wei Liu
2016-10-10 15:51 ` Ian Jackson
2016-10-10 16:33 ` Wei Liu
2016-10-10 17:38 ` Boris Ostrovsky
2016-10-11 9:40 ` Wei Liu
2016-10-11 9:52 ` Ian Jackson
2016-10-11 12:52 ` Boris Ostrovsky
2016-10-11 13:32 ` Ian Jackson
2016-10-11 14:27 ` Boris Ostrovsky
2016-10-11 14:54 ` Ian Jackson
2016-10-11 17:11 ` Boris Ostrovsky
2016-10-12 7:45 ` Jan Beulich
2016-10-12 11:00 ` [PATCH for-4.8] ipxe: update to newer commit [and 1 more messages] Ian Jackson
2016-10-12 14:09 ` Boris Ostrovsky
2016-10-12 14:14 ` Wei Liu
2016-10-12 14:16 ` Ian Jackson
2016-10-11 21:11 ` [PATCH for-4.8] ipxe: update to newer commit Andrew Cooper
2016-10-11 21:17 ` Andrew Cooper
2016-10-12 7:50 ` Jan Beulich
2016-10-10 18:28 ` Juergen Schinker
2016-10-11 9:37 ` Wei Liu
2016-10-11 9:42 ` Juergen Schinker
2016-10-11 9:45 ` Wei Liu
2016-10-11 19:31 ` Juergen Schinker
2016-10-11 19:45 ` Konrad Rzeszutek Wilk
2016-10-12 9:27 ` Wei Liu
2016-10-12 21:03 ` Boris Ostrovsky
2016-10-13 9:04 ` Wei Liu
2016-10-13 9:10 ` Juergen Schinker
2016-10-13 9:29 ` Wei Liu
2016-10-13 10:02 ` Juergen Schinker
2016-10-13 14:53 ` Wei Liu
[not found] ` <1633715062.155.1476375972276.JavaMail.zimbra@homie.homelinux.net>
2016-10-13 16:45 ` Wei Liu [this message]
2016-10-13 19:58 ` ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16 Juergen Schinker
2016-10-13 9:32 ` [PATCH for-4.8] ipxe: update to newer commit Wei Liu
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=20161013164507.GO3687@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ba1020@homie.homelinux.net \
--cc=xen-devel@lists.xenproject.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 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.