From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: Ian.Jackson@eu.citrix.com, jbeulich@suse.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Make possible point to system seabios instead include it in hvmloader
Date: Mon, 12 May 2014 09:49:04 +0100 [thread overview]
Message-ID: <53708B00.9040305@citrix.com> (raw)
In-Reply-To: <1399884230.561.78.camel@kazak.uk.xensource.com>
On 12/05/2014 09:43, Ian Campbell wrote:
> On Sat, 2014-05-10 at 14:08 +0200, Fabio Fantoni wrote:
>> Actually is possible specify upstream qemu and seabios from distro's
>> packages or custom builds with xen configure.
>> If these are used and qemu package will be updated, xen will use updated
>> qemu but if seabios package will be updated, xen will use the new one
>> only with xen rebuild.
> Correct.
>
>> If for example seabios will be updated with fixes and/or new version (in
>> some case required by newer qemu) xen will still have the bug fixed and
>> will have new bugs until will be rebuilded.
> Correct.
>
>> Is possible make hvmloader point to seabios specified in configure
>> instead include it in hvmloader?
> You would have to arrange for something (probably the toolstack) to load
> the seabios file off disk and place it into guest memory as part of
> building the domain and then you would need to invent some protocol
> (perhaps xenstore based) so that the toolstack could signal to hvmloader
> where to go an look for the seabios binary in guest RAM.
Making the BIOS a multiboot module and teaching hvmloader about
multiboot seems much simpler.
The toolstack already has code for doing this in the PV case.
~Andrew
next prev parent reply other threads:[~2014-05-12 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 12:08 Make possible point to system seabios instead include it in hvmloader Fabio Fantoni
2014-05-12 8:43 ` Ian Campbell
2014-05-12 8:49 ` Andrew Cooper [this message]
2014-05-12 9:01 ` Ian Campbell
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=53708B00.9040305@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=jbeulich@suse.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.