qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Rebecca Cran <rebecca@bluestop.org>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Yuval Shaia <yuval.shaia@oracle.com>
Subject: Re: [Qemu-devel] RDMA wrongly detected as being supported on FreeBSD
Date: Thu, 26 Jul 2018 19:11:46 +0300	[thread overview]
Message-ID: <50119bfb-384d-49f0-609c-36de374a8c6b@gmail.com> (raw)
In-Reply-To: <20180725105944.GC2366@work-vm>



On 07/25/2018 01:59 PM, Dr. David Alan Gilbert wrote:
> * Marcel Apfelbaum (marcel.apfelbaum@gmail.com) wrote:
>> Hi,
>>
>> On 07/25/2018 10:32 AM, Thomas Huth wrote:
>>> On 25.07.2018 06:47, Rebecca Cran wrote:
>>>> In commit 18a398f6a39df4b08ff86ac0d38384193ca5f4cc, ./configure on
>>>> FreeBSD incorrectly detects RDMA support,
>> configure is looking for the rdma related libraries,  if they are there,
>> the rdma code will be compiled into QEMU.
>>
>> You can try and run configure with --disable-rdma flag until we find
>> a solution.
> Note that this flag is tied to both the RMDA migration and the RDMA
> device emulation; RDMA migration may well be working for the reporter.

That's in case they don't care for either RDMA functionality of course -
to be used until we would find a solution.

Thanks,
Marcel

> Dave
>
>>>>    with the build subsequently
>>>> failing with:
>>>>
>>>> /home/bcran/workspace/qemu/hw/rdma/vmw/pvrdma_cmd.c:19:10: fatal error:
>>>> 'linux/types.h' file not found
>>>> #include <linux/types.h>
>>>>            ^~~~~~~~~~~~~~~
>> Do you have the kernel-headers package installed?
>>
>>>> 1 error generated.
>>>> gmake[1]: *** [/home/bcran/workspace/qemu/rules.mak:69:
>>>> hw/rdma/vmw/pvrdma_cmd.o] Error 1
>>>> gmake[1]: *** Waiting for unfinished jobs....
>>>> gmake: *** [Makefile:481: subdir-x86_64-softmmu] Error 2
>>> When was it still working for you the last time? Was it still working
>>> with v3.0-rc1 ? Or just with v2.12 ? Any chance that you could bisect
>>> the problem to determine when it has been introduced?
>> Good idea.
>>
>> Thanks,
>> Marcel
>>
>>>    Thomas
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-07-26 16:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  4:47 [Qemu-devel] RDMA wrongly detected as being supported on FreeBSD Rebecca Cran
2018-07-25  7:32 ` Thomas Huth
2018-07-25 10:48   ` Marcel Apfelbaum
2018-07-25 10:59     ` Dr. David Alan Gilbert
2018-07-26 16:11       ` Marcel Apfelbaum [this message]
2018-07-25 11:14     ` Thomas Huth
2018-07-28  3:50       ` Rebecca Cran
2018-08-06  8:51         ` Thomas Huth
2018-08-11 16:47           ` Marcel Apfelbaum
2018-08-12  8:39             ` Yuval Shaia
2018-08-12 12:10               ` Marcel Apfelbaum
2018-08-15 13:37           ` Kamil Rytarowski
2018-08-16  8:55             ` Marcel Apfelbaum
2018-08-16  9:02               ` Thomas Huth
2018-08-16  9:07                 ` Marcel Apfelbaum
2018-07-29  3:08   ` Rebecca Cran

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=50119bfb-384d-49f0-609c-36de374a8c6b@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rebecca@bluestop.org \
    --cc=thuth@redhat.com \
    --cc=yuval.shaia@oracle.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).