called winexe, but we are in the process of finding a replacement
for winexe at the moment.
--
Chris Lalancette
[1] http://aeolusproject.org/oz.html
. In any case, it's a corner case that libvirt
will never intentionally put itself into, so either way is fine with me.
(I also tend to think that overwriting data without any notification isn't
very nice, but I also understand that this is a change in semantics)
--
Chris Lalancette
.
Now, I agree that this isn't the best way to do it; much better would
be a way for libvirt to query the capabilities of Qemu directly and
not rely on versions (not the least because of the problem you point
out above). But up until now we haven't had a better way to do it.
--
Chris Lalancette
details of the monitor. It's that
latter group that we want to make sure doesn't use this API.
--
Chris Lalancette
that the virDomainQemuInvokeMonitor
has been called.
--
Chris Lalancette
expression, s/match/modify/, against
the
argument to the -net option, and it makes more sense.
We are hoping to refine this proposal based on feedback, so comments and
criticisms
are welcome!
--
Chris Lalancette
one.
It is complex, I agree. I also think it is pretty powerful. But if
the need arises, we can always add it later. For now we'll go with just the
monitor passthrough and simple command-line addition, and we can evolve from
there.
--
Chris Lalancette
