From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Kevin Wilson <wkevils@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] QEMU version for DTS tests
Date: Tue, 25 Dec 2018 03:03:35 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9E67AC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAGXs5wXw+NOijBU=v9TnHAVoPtyYEA-z7cUp_YaH1vHd6SeNoA@mail.gmail.com>
Sorry for unclear document. Currently we have tested QEMU 2.11, Snice Qemu 2.7 removed pci-stub, QEMU 2.7+ should use vfio-pci to pass ports to VM.
I will add some documents revision to my backlog. Thanks for your good advices.
Hi Meijuan,
You are expert to set up DTS which qemu, could you kindly help Kevin?
Thanks in advance.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Kevin Wilson
> Sent: Friday, December 21, 2018 7:05 PM
> To: dts@dpdk.org
> Subject: [dts] QEMU version for DTS tests
>
> Hello, DTS Maintainer/developers,
>
> In Fedora 29 and recent Ubuntu releases, when we are trying to run DTS
> tests which launch QEMU VM they fail .
> The reason is that QEMU API changed, and some of the options which are
> used in DTS for launching QEMU are not supported anymore.
>
> So my question is: which QEMU version is supported by DTS ?
> If it is not known whether there is such a version which supports
> **all** the DTS test modules,
> it is enough to mention the QEMU version which is known to work with
> several DTS test modules (or preferably most DST test modules), and if so, I
> will also appreciate mentioning the names of these tests.
>
> Regards,
> Kevin Wilson
prev parent reply other threads:[~2018-12-25 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 11:04 Kevin Wilson
2018-12-25 3:03 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0B9E67AC@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wkevils@gmail.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).