ll seems to work,
> expect for "Password&&" which gets converted to "Password&&" (if
> I type "Password&&" it works).
Could it be related to this patch where our JSON code mishandles %?
https://lists.gnu.org/archive/html/qemu
U_OPT_BOOL,
> +#ifdef CONFIG_OPENGL_DMABUF
> +},{
> +.name = "gl",
> +.type = QEMU_OPT_BOOL,
> +#endif
> },
How introspectible is this? Does QMP 'query-command-line-options' cope
will with showing 'gl' as a
MP to be introspectible, as scraping --help output
is not machine-friendly. (That said, you DO want to expose it in --help
output; I'm just complaining that --help output alone is not enough).
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvi
s libvirt going to introspect whether the command line supports
this option? Is there some QMP command that lists the set of valid
compression formats understood by a given qemu binary?
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
sig
faster to do the refresh from Fedora 18
than to figure out whether Fedora 19 is even buildable for mingw. Or,
if he builds from the (still-in-beta) Fedora 20, you'd get a build based
off of 1.1.2.
Development happens upstream, but we DO backport patches to the stable
release branches that
On 09/18/2013 01:43 AM, Daniel P. Berrange wrote:
> On Tue, Sep 17, 2013 at 12:38:03PM -0600, Eric Blake wrote:
>> [adding libvir-list, for some cross-compiling development hints]
>>
>> On 09/17/2013 11:57 AM, Fernando Lozano wrote:
>>
>>> Yes, the libvirt comes
t to have a more convenient way to bootstrap
libvirt.git for VPATH builds without having to rely on the hack that
options unrecognized by ./autogen.sh are passed on to ./configure, and
that ./configure --help is the easiest way to do avoid polluting the
top-level tree in a way that would interfere w
so, the
fact that you are using a pre-built version of a relatively old libvirt,
instead of building your own from the latest sources, makes it hard to
know what OTHER issues may have been fixed in the meantime (when given a
choice, developers prefer to debug issues in the latest source, rather
ork.
[On a personal note, even if I were NOT sending mail from a redhat.com
address, I would _still_ hope that you are able to work something out
with a Red Hat sales rep, or with any other open source support vendor -
everyone wins when more people are able to use an open source solution]
--
Eri
in that msi? Maybe it's just a case
of a stale build, for something that has been fixed upstream?
But I personally have not tried to build or debug on mingw, to know if
this is the only issue, or if you are staring at a number of other
portability issues to resolve first.
--
Eric B
Let me know if you need the entire guest xml, or what additional
debugging steps I can perform to assist you in helping me.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
11 matches
Mail list logo
