On 06.07.2012 12:09, Amos Kong wrote:
> - Original Message -
>> Michael Tokarev writes:
>>> Gyus, please, pretty PLEASE stop doing things like this.
>>>
>>> Amos, your patch does TWO things. One is to clarify error
>>> message as correctly stated in your description, and second
>>> is to
- Original Message -
> Michael Tokarev writes:
>
> > On 06.07.2012 06:42, Amos Kong wrote:
> >> On 30/06/12 10:02, ak...@redhat.com wrote:
> >>> From: Amos Kong
> >>>
> >>> Currently qemu outputs some low-level error in qemu-sockets.c
> >>> when failed to start vnc server.
> >>> eg. 'get
Michael Tokarev writes:
> On 06.07.2012 06:42, Amos Kong wrote:
>> On 30/06/12 10:02, ak...@redhat.com wrote:
>>> From: Amos Kong
>>>
>>> Currently qemu outputs some low-level error in qemu-sockets.c
>>> when failed to start vnc server.
>>> eg. 'getaddrinfo(127.0.0.1,5902): Name or service not kn
On 06.07.2012 06:42, Amos Kong wrote:
> On 30/06/12 10:02, ak...@redhat.com wrote:
>> From: Amos Kong
>>
>> Currently qemu outputs some low-level error in qemu-sockets.c
>> when failed to start vnc server.
>> eg. 'getaddrinfo(127.0.0.1,5902): Name or service not known'
>>
>> Some libvirt users coul
On 30/06/12 10:02, ak...@redhat.com wrote:
From: Amos Kong
Currently qemu outputs some low-level error in qemu-sockets.c
when failed to start vnc server.
eg. 'getaddrinfo(127.0.0.1,5902): Name or service not known'
Some libvirt users could not know what's happened with this
unclear error messag
From: Amos Kong
Currently qemu outputs some low-level error in qemu-sockets.c
when failed to start vnc server.
eg. 'getaddrinfo(127.0.0.1,5902): Name or service not known'
Some libvirt users could not know what's happened with this
unclear error message. This patch added a more descriptive
error
