From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Konrad Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen 4.2.0 won't boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
Date: Thu, 30 Aug 2012 09:19:35 -0700 (PDT) [thread overview]
Message-ID: <175f3c87-367d-4b1d-bf0c-517313f89ff6@default> (raw)
In-Reply-To: <20120829224434.GA4650@localhost.localdomain>
> From: Konrad Rzeszutek Wilk
>
> On Wed, Aug 29, 2012 at 03:22:40PM -0700, Dan Magenheimer wrote:
> > Anybody else see this: a FC17 dom0 which boots fine for 4.1.3
> > crashes early in boot with Xen 4.2.0-rc4?
> >
> > The hardware is a new Dell Optiplex 790 which I've noticed has a couple
> > of idiosyncrasies when booting recent upstream versions of Linux:
> > 1) reboot=pci is required or reboot hangs
> > 2) reducing visible memory via memmap= on a Linux command line is
> > fairly difficult (requires a very complex sequence of Linux boot
> > parameters, presumably due to a weird e820 RAM map in this hardware)
> >
> > These idiosyncrasies may or may not be related to the dom0 crash,
> > just mentioning them in case they suggest an easy workaround.
>
> What happens if you run with 'console=vga vga=text,keep' on the
> hypervisor line and on the Linux command line: 'console=hvc0
> earlyprink=xen debug loglevel=8'
Ah, good, thanks for the pointer. Haven't had to do that in awhile.
The dom0 tombstone has an xsave_init call in it... I tried booting
with xsave=0 as a Xen boot parameter and I can now boot 4.2.0-rc4
with FC17 dom0.
Sorry for the noise.
Thanks,
Dan
next prev parent reply other threads:[~2012-08-30 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 22:22 Xen 4.2.0 won't boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3 Dan Magenheimer
2012-08-29 22:44 ` Konrad Rzeszutek Wilk
2012-08-30 16:19 ` Dan Magenheimer [this message]
2012-08-30 6:16 ` bing
2012-08-30 17:04 ` Dan Magenheimer
2012-08-31 11:05 ` Jan Beulich
2012-08-31 14:59 ` Dan Magenheimer
2012-08-31 17:32 ` Konrad Rzeszutek Wilk
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=175f3c87-367d-4b1d-bf0c-517313f89ff6@default \
--to=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.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.