From: Ross Philipson <ross.philipson@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Art Napor <artnapor@yahoo.com>
Subject: Re: HVM firmware passthrough - helper library
Date: Wed, 20 Mar 2013 16:08:13 -0400 [thread overview]
Message-ID: <514A172D.8050605@citrix.com> (raw)
In-Reply-To: <1363806237.80975.YahooMailNeo@web161405.mail.bf1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
> Ross,
>
> Finally got back to this project to test out the helper lib using the v3
> hvm-firmware passthrough patches with Xen 4.2.1. When building from
> tools/firmware the build failed with the following output:
>
> make
> gcc -Wl,-soname -Wl,libxenhvm.so.1.0 -shared -o libxenhvm.so.1.0.0
> xenhvm.opic smbios_module.opic acpi_module.opic xh_internal.opic
> /home/ajn131/rpmbuild/SOURCES/xen-4.2.1/tools/firmware/libhvm/../../../tools/xenstore/libxenstore.so
>
> xenhvm.opic: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make: *** [libxenhvm.so.1.0.0] Error 1
>
> I was hoping to integrate the build into the RPM. Any thoughts? Should I
> try it with the latest 4.3?
>
>
> Thanks Again,
>
> -
> Art
Art,
Can you try the attached tarball. A colleague found and fixed a couple
of issues in my sample including the face that it was including in the
wrong Rules.mk.
Thanks
Ross
> ------------------------------------------------------------------------
> *From:* Ross Philipson <Ross.Philipson@citrix.com>
> *To:* "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
> *Cc:* "Art Napor (artnapor@yahoo.com)" <artnapor@yahoo.com>
> *Sent:* Tuesday, January 8, 2013 5:04 PM
> *Subject:* HVM firmware passthrough - helper library
>
> Attached is a tarball with a helper library for reading host ACPI and
> SMBIOS firmware and creating firmware files that can be used with the
> HVM firmware passthrough patches I submitted. I used it in my testing of
> the patches and planned to use it later when we moved to a new Xen
> version. This library was requested by a few people - I hope you find it
> useful.
>
> Ross Philipson
> Senior Software Engineer
> Citrix Systems, Inc
> 14 Crosby Drive
> Bedford, MA 01730
> 781-301-7949
> ross.philipson@citrix.com <mailto:ross.philipson@citrix.com>
>
[-- Attachment #2: xen-libhvm.tar.gz --]
[-- Type: application/gzip, Size: 13730 bytes --]
[-- Attachment #3: 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:[~2013-03-20 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 22:04 HVM firmware passthrough - helper library Ross Philipson
2013-01-09 10:44 ` Ian Campbell
2013-01-09 17:57 ` Ross Philipson
2013-02-01 20:26 ` Ross Philipson
2013-02-04 10:24 ` Ian Campbell
2013-02-04 18:42 ` Ross Philipson
[not found] ` <1363806237.80975.YahooMailNeo@web161405.mail.bf1.yahoo.com>
2013-03-20 20:08 ` Ross Philipson [this message]
2013-03-21 19:42 ` Art Napor
2013-03-24 21:10 ` Ross Philipson
2013-03-27 4:50 ` Art Napor
2013-04-01 22:04 ` Ross Philipson
2013-04-02 3:19 ` Art Napor
2013-04-02 21:15 ` Ross Philipson
2013-04-23 22:06 ` Art Napor
2013-04-24 13:09 ` Ross Philipson
2013-09-12 19:29 ` Art Napor
2013-09-13 13:25 ` Ross Philipson
2013-09-14 13:45 ` Andrew Bobulsky
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=514A172D.8050605@citrix.com \
--to=ross.philipson@citrix.com \
--cc=artnapor@yahoo.com \
--cc=xen-devel@lists.xensource.com \
/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).