From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Harmandeep Kaur <write.harmandeep@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Error booting Xen
Date: Tue, 19 Jan 2016 15:51:35 +0100 [thread overview]
Message-ID: <1453215095.11427.144.camel@citrix.com> (raw)
In-Reply-To: <569E4A0102000078000C8917@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1526 bytes --]
On Tue, 2016-01-19 at 06:36 -0700, Jan Beulich wrote:
> > > > On 18.01.16 at 19:29, <dario.faggioli@citrix.com> wrote:
> >
> > Yeah, but again, it was booting as dom0 with another Xen... doesn't
> > that mean that Xen at least has a role in exposing it?
> >
> > Also, what would you think it's better to try next... try another
> > kernel?
>
> Figure out what the GP fault that gets recovered from is being
> caused by.
>
Yep, thanks.
Harmandeep is looking at (learning how to do) this already. If you feel
like sharing any knowledge/giving any advice on how to best achieve
that, I'm sure she'll appreciate (but if you can't or don't have time,
no problem :-D).
> Then - if indeed it worked on another hypervisor
> build - figure out the difference(s) in behavior.
>
Right. Harmandeep, you can try this rather easily!.
You have a clone of the xen.git already. I think you just have to:
- `make uninstall' (I'm not sure it will work, but it at least should
not harm!)
- clean the sources
- checkout, e.g., in a branch, one of the tags of a previous release,
say RELEASE-4.6.0 or RELEASE-4.5.0
- build again
- install
- update the bootloader
- reboot and report the result.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-19 14:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:03 Error booting Xen Harmandeep Kaur
2016-01-18 18:09 ` Andrew Cooper
2016-01-18 18:29 ` Dario Faggioli
2016-01-19 13:36 ` Jan Beulich
2016-01-19 14:51 ` Dario Faggioli [this message]
2016-01-19 15:07 ` Andrew Cooper
2016-01-19 16:27 ` Harmandeep Kaur
2016-01-19 16:47 ` Jan Beulich
2016-01-19 17:02 ` Andrew Cooper
2016-01-19 17:08 ` Dario Faggioli
2016-01-19 17:09 ` Andrew Cooper
2016-01-19 19:55 ` Harmandeep Kaur
2016-01-20 10:06 ` Jan Beulich
2016-01-21 15:14 ` Dario Faggioli
2016-01-21 15:24 ` Harmandeep Kaur
2016-01-25 13:42 ` Jan Beulich
2016-01-26 11:58 ` Dario Faggioli
2016-01-26 12:51 ` Harmandeep Kaur
2016-01-26 13:13 ` Harmandeep Kaur
2016-01-26 13:23 ` Jan Beulich
2016-01-26 17:01 ` Harmandeep Kaur
2016-01-26 17:23 ` Jan Beulich
2016-01-26 18:02 ` Harmandeep Kaur
2016-01-26 18:28 ` Dario Faggioli
2016-01-26 18:36 ` Harmandeep Kaur
2016-01-27 8:24 ` Jan Beulich
2016-01-27 13:12 ` Jan Beulich
2016-01-27 13:28 ` Harmandeep Kaur
2016-01-27 14:28 ` Jan Beulich
2016-01-28 19:17 ` Harmandeep Kaur
2016-01-29 10:13 ` Jan Beulich
2016-02-03 8:23 ` Dario Faggioli
2016-02-03 11:35 ` Harmandeep Kaur
2016-02-03 12:49 ` Jan Beulich
2016-02-03 12:55 ` Dario Faggioli
2016-02-03 13:10 ` Andrew Cooper
2016-02-03 13:17 ` Dario Faggioli
2016-02-03 16:57 ` Konrad Rzeszutek Wilk
2016-02-03 13:40 ` Harmandeep Kaur
2016-02-03 14:18 ` Jan Beulich
2016-01-26 13:22 ` Jan Beulich
2016-02-02 4:43 ` Shuai Ruan
[not found] ` <20160202044349.GA3036@shuai.ruan@linux.intel.com>
2016-02-02 10:39 ` Andrew Cooper
2016-02-03 0:56 ` Shuai Ruan
2016-02-03 7:56 ` Shuai Ruan
2016-01-19 14:07 ` Harmandeep Kaur
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=1453215095.11427.144.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=write.harmandeep@gmail.com \
--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 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.