Re: [Qemu-devel] Re: [PATCH 2/7] Enable I/O thread and VNC threads by default

From: Aurelien Jarno <aurelien@aurel32.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Paul Brook <paul@codesourcery.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Arun Bharadwaj <arun@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Re: [PATCH 2/7] Enable I/O thread and VNC threads by default
Date: Tue, 08 Feb 2011 12:29:30 +0100	[thread overview]
Message-ID: <4D51291A.8090908@aurel32.net> (raw)
In-Reply-To: <4D5185EB.8090108@codemonkey.ws>

Anthony Liguori a écrit :
> On 02/08/2011 04:27 AM, Aurelien Jarno wrote:
>> Stefan Hajnoczi a écrit :
>>    
>>> Introducing IOTHREAD made !CONFIG_IOTHREAD platforms second class
>>> citizens.  I think you'd like people to provide full support when they
>>> introduce new features.
>>>
>>>      
>> I think you really pointed the problem here. We should probably add a
>> feature that will make KVM second class citizen so that people can
>> understand what it means.
>>    
> 
> Aurelien,
> 
> Have you actually run QEMU on Windows and tried to use it to do 
> something useful?
> 
> As an exercise, walk through the various releases of QEMU and compare 
> how well it works on Windows to any Unix platform.  Windows support in 
> QEMU has always been a second class citizen.

I never tried to get it working on windows, but I know some people using
it there. We should just don't ignore them. Maybe it's not perfect, but
it is enough for those people.

> If someone is willing to stand up and properly maintain it, I'm all for 
> doing whatever we can to be supportive of that person but as of right 
> now, that doesn't exist.

There are regular patches for windows support, Stefan Weil is producing
builds regularly. Maybe it doesn't have all the features, but people are
making sure it basically works.

Now you want to break that because the *new* feature you want to
introduce is not supported on windows. I insist on the fact it is a new
feature simply because it was *disabled* by default. So I don't buy the
argument about "that person don't exist".

Send a call for help on that subject, give the people some time to come
with a solution (let's put a deadline), and then if nobody appears we
can definitely consider Windows support as dead. But it should not be
done arbitrary.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net