search for: apabilities

Even though this option is not to be used according to the manual, it: a) still might be useful even for machine-readable logs b) should not break the machine-readable output Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- v2v/v2v.ml | 29 ++++++++++++++++++++++------- 1 file changed, 22 insertions(+), 7 deletions(-) diff --git a/v2v/v2v.ml b/v2v/v2v.ml index

...AVP 3 101 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 11 headers, 10 lines Using latest request as basis request Sending to 192.168.1.111 : 5060 (NAT) Found audio format UNKN Found audio format UNKN Found description format GSM Found description format telephone-event Capabilities: us - 6, them - 2/0, combined - 2 Non-codec capabilities: us - 1, them - 1, combined - 1 We're at xxx.xxx.xxx.xxx port 14276 Answering with preferred capability 2 Answering with non-codec capability 1 Reliably Transmitting (NAT): SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.111;rport;branch=z9hG4b...

...ine-readable does not write any data to stdout or stderr, even when specified as --machine-readable=stream:stdout (or stderr) for simple libvirt2libvirt migration. So point (b) from the commit message is probably invalid. Oh, actually, I don't see it being used for anything else than printing apabilities and estimates. I wonder where the json messages in machine readable logfile that virt-v2v-wrapper requests are coming from. One last thing is that currently any application that wants to run virt-v2v (virt-v2v-wrapper in my case) needs to parse the output to get any meaningful data from it. What...