From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
David Erickson <halcyon1981@gmail.com>,
jacek burghardt <jaceksburghardt@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: LSI SAS2008 Option Rom Failure
Date: Thu, 19 Jul 2012 12:31:06 +0100 [thread overview]
Message-ID: <5007EFFA.7080201@citrix.com> (raw)
In-Reply-To: <1342696026.26734.48.camel@zakaz.uk.xensource.com>
On 19/07/12 12:07, Ian Campbell wrote:
> On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
>> On 19/07/12 08:22, Ian Campbell wrote:
>>> David also previous tried our branch of upstream qemu and had problems
>>> there too -- I thought we'd backported the basic PCI passthrough support
>>> but he was seeing
>>> libxl: error: libxl_qmp.c:288:qmp_handle_error_response:
>>> received an
>>> error message from QMP server: Parameter 'driver' expects a
>>> driver
>>> name
>>> (see upthread for more details)
>>
>> This is because the pci passthrough is not compiled in QEMU. I could
>> maybe try to improve this error message.
>
> Should this be enabled in our build system and/or referenced in the
> wiki?
This should not be needed as it is enable by default if possible. But I
don't know what went wrong here :(.
Otherwise, to be sure that pci passthrough is compiled in, use the
--enable-xen-pci-passthrough configure option.
--
Anthony PERARD
next prev parent reply other threads:[~2012-07-19 11:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 21:02 LSI SAS2008 Option Rom Failure ivo
2012-07-18 23:52 ` David Erickson
2012-07-19 0:18 ` David Erickson
2012-07-19 0:24 ` ivo
2012-07-19 0:56 ` David Erickson
2012-07-19 1:02 ` David Erickson
[not found] ` <CAHyyzzTMX4wcg+DNEL91dWmo0R-6oGJLNH5O50bSUeHkmTWAwQ@mail.gmail.com>
2012-07-19 3:56 ` David Erickson
2012-07-19 7:22 ` Ian Campbell
2012-07-19 10:57 ` Anthony PERARD
2012-07-19 11:07 ` Ian Campbell
2012-07-19 11:31 ` Anthony PERARD [this message]
2012-07-19 11:38 ` Ian Campbell
2012-07-19 11:44 ` Anthony PERARD
2012-07-19 11:48 ` Ian Campbell
2012-07-19 11:48 ` Stefano Stabellini
2012-07-19 11:59 ` Ian Campbell
2012-07-19 12:00 ` Stefano Stabellini
2012-07-19 15:27 ` David Erickson
2012-07-31 7:35 ` David Erickson
2012-07-31 9:04 ` Ian Campbell
2012-07-31 9:35 ` Jan Beulich
2012-07-31 9:41 ` Ian Campbell
2012-07-31 9:47 ` Jan Beulich
2012-07-31 10:08 ` Anthony PERARD
2012-07-31 15:32 ` David Erickson
2012-07-31 10:16 ` Stefano Stabellini
2012-07-31 15:28 ` David Erickson
2012-07-31 15:35 ` Ian Campbell
2012-07-31 16:12 ` David Erickson
2012-07-31 11:39 ` Stefano Stabellini
2012-07-31 16:05 ` David Erickson
2012-08-01 11:13 ` Stefano Stabellini
2012-08-01 17:52 ` David Erickson
2012-08-02 7:45 ` Ian Campbell
2012-08-02 16:24 ` David Erickson
2012-08-02 16:45 ` Ian Campbell
2012-08-02 17:10 ` David Erickson
2012-08-02 17:12 ` David Erickson
2012-08-02 18:39 ` Ian Campbell
2012-08-02 17:38 ` David Erickson
2012-08-03 16:50 ` David Erickson
2012-08-06 10:23 ` Stefano Stabellini
2012-07-19 0:18 ` ivo
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 9:47 David Erickson
2012-07-18 9:59 ` Ian Campbell
2012-07-18 17:55 ` David Erickson
2012-07-18 18:19 ` David Erickson
2012-07-18 19:14 ` David Erickson
2012-07-18 20:13 ` James Regan
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=5007EFFA.7080201@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=halcyon1981@gmail.com \
--cc=jaceksburghardt@gmail.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).