From: John Snow <jsnow@redhat.com>
To: li <lijiamin036@163.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] configure options of qemu
Date: Tue, 25 Nov 2014 11:47:08 -0500 [thread overview]
Message-ID: <5474B28C.6080205@redhat.com> (raw)
In-Reply-To: <6c538796.a24d.149dfb4389a.Coremail.lijiamin036@163.com>
On 11/23/2014 09:49 PM, li wrote:
> Hi all,
> Thank you for your time to read this email, is there anyone can tell me
> the options qemu was configured when it was released?
> I configured it by myself and found that there was a audio latency
> problem, but the qemu in the repository doesn't have this problem,
> so i want to kown about its configuration options.
> the options i using is as below:
> ./configure --enable-spice --enable-usb-redir --enable-kvm
> --disable-werror --prefix=/home/stone/qemu --target-list=x86_64-softmmu
> --audio-card-list=ac97,es1370,sb16,cs4231a,adlib,gus,hda,ich6
> --audio-drv-list=pa,alsa,sdl,oss
> Best Regards
> stone
>
"The repository" -- whose? We don't dictate the configuration options
that the various distributions decide to package with. You'd have to ask
your distribution (Ubuntu? Debian? Fedora? CentOS?) what options they
packaged with.
Before you jump down that rabbit hole, though, try comparing the
versions you're using. It might just be a version difference. It would
be worth trying to configure the upstream sources that match the version
your distribution ships and seeing if you have the same problem to
determine if it's a bug or a configuration problem.
--
—js
prev parent reply other threads:[~2014-11-25 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 2:49 [Qemu-devel] configure options of qemu li
2014-11-24 3:06 ` li
2014-11-25 16:47 ` John Snow [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=5474B28C.6080205@redhat.com \
--to=jsnow@redhat.com \
--cc=lijiamin036@163.com \
--cc=qemu-devel@nongnu.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.