xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jason Dickens <jdickens@grammatech.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Crash w/ bios="ovmf"
Date: Mon, 27 Feb 2017 11:55:27 +0000	[thread overview]
Message-ID: <20170227115527.2lwcqer4zfwpjid5@citrix.com> (raw)
In-Reply-To: <eac30ea3-5962-002a-fa46-bff72e4d47b0@grammatech.com>

On Wed, Feb 22, 2017 at 03:50:28PM -0500, Jason Dickens wrote:
> I'm trying to find a solution to an immediate VM crash which occurs by
> simply adding "bios='ovmf' to my configuration?
> 
> I started with a standard Ubuntu install which contained Xen 4.6.0 and had
> the crash. The VM works fine booting w/ SeaBIOS once the configuration line
> is removed. It also works fine with OVMF using just QEMU.
> 
> Then I was led to believe that i needed to rebuild Xen with --enable-ovmf ,
> using the source from apt-get source, this proved to be difficult and
> ultimately I had to disable stub domains to get it to work. (in case, that
> is relevant)
> 
> Still I get the crash almost immediately after the VM is launched. With
> sdl=1 I can see the window flash up and disappear.
> I should mention that ultimately I plan to use a non-standard build of the
> OVMF kernel, but for now I'm happy to get it working with any one.
> 
> At this point, I have been studying the source to try and determine where
> things diverge. I find very little use of LIBXL_BIOS_TYPE_OVMF and can't
> find  exactly where setting hvm.bios that even matters?
> 
> In any case, I would appreciate help on how to avoid the crash and/or
> understanding the Xen modifications for OVMF.
> 

Because OVMF doesn't do regular releases, we ship a commit of it when we
release a new version of Xen.

Are you comfortable with building Xen from the development branch? If
you use 4.8 or our master branch, you should be able to provide an OVMF
blob without rebuilding HVMloader every time.

Wei.


> Jason
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-02-27 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 20:50 Crash w/ bios="ovmf" Jason Dickens
2017-02-27 11:55 ` Wei Liu [this message]
2017-02-27 16:59 ` Konrad Rzeszutek Wilk
2017-02-27 19:15   ` jdickens

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=20170227115527.2lwcqer4zfwpjid5@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=jdickens@grammatech.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 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).