From: "Duncan X. Simpson" <virtualdxs@gmail.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Can't read bios file
Date: Wed, 05 Apr 2017 13:43:33 +0000 [thread overview]
Message-ID: <CAB8Qo2TMdgsqNP4koe-7jtERwHd_t79w88C2M9cNKsvXtoFmCA@mail.gmail.com> (raw)
In-Reply-To: <20170405095709.GE1710@perard.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 910 bytes --]
I apologize for HTML, I'm using Google Inbox and I'm not sure how to
control it. Yes I am using AUR, and I can imagine somebody adding
--with-system-seabios=yes not understanding what it's supposed to be. Thank
you, I will take a look at that later today!
On Wed, Apr 5, 2017, 02:57 Anthony PERARD <anthony.perard@citrix.com> wrote:
> On Wed, Apr 05, 2017 at 01:39:13AM +0000, Duncan X. Simpson wrote:
> > Does anybody have advice as to what to do? Am I in the wrong place? Am I
> > missing something obvious?
>
> Could you send email in plain text only (no html)?
>
> Have you build Xen from a package in AUR? In that case, reading/writing
> comment there can be helpful.
>
> How do you compile Xen? If you compiled with
> --with-system-seabios, it should be
> --with-system-seabios=/usr/share/qemu/bios-256k.bin
> (on Arch Linux)
>
> Hope that help,
>
> --
> Anthony PERARD
>
--
Duncan X. Simpson, K7DXS
[-- Attachment #1.2: Type: text/html, Size: 1656 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-05 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 1:25 Can't read bios file Duncan X. Simpson
2017-04-04 2:05 ` Duncan X. Simpson
2017-04-04 18:03 ` Duncan X. Simpson
2017-04-05 1:39 ` Duncan X. Simpson
2017-04-05 9:57 ` Anthony PERARD
2017-04-05 13:43 ` Duncan X. Simpson [this message]
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=CAB8Qo2TMdgsqNP4koe-7jtERwHd_t79w88C2M9cNKsvXtoFmCA@mail.gmail.com \
--to=virtualdxs@gmail.com \
--cc=anthony.perard@citrix.com \
--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.