On 2012-10-03 11:55, Gleb Natapov wrote:
> On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
>> On 2012-10-01 15:19, Anthony Liguori wrote:
>>> Jan Kiszka <jan.kis...@siemens.com> writes:
>>>
>>>> On 2012-10-01 11:31, Marcelo Tosatti wrote:
>>>>
>>>> It's not just about default configs. We need to validate if the
>>>> migration formats are truly compatible (qemu-kvm -> QEMU, the other way
>>>> around definitely not). For the command line switches, we could provide
>>>> a wrapper script that translates them into upstream format or simply
>>>> ignores them. That should be harmless to carry upstream.
>>>
>>> qemu-kvm has:
>>>
>>>  -no-kvm
>>>  -no-kvm-irqchip
>>>  -no-kvm-pit
>>>  -no-kvm-pit-reinjection
>>>  -tdf <- does nothing
>>>
>>> There are replacements for all of the above.  If we need to add them to
>>> qemu.git, it's not big deal to add them.
>>
>> But I don't think we should add them to the source code. This can
>> perfectly be handled my a (disposable) script layer on top of
>> qemu-system-x86_64 - the namespace (qemu-kvm in most cases) is also free.
>>
>>>
>>>  -drive ...,boot= <- this is ignored
>>>
>>> cpu_set command for CPU hotplug which is known broken in qemu-kvm.
>>
>> Right, so nothing is lost when migrating to QEMU.
>>
>>>
>>> testdev which is nice but only used for development
>>>
> Jan, do you have a plan for testdev device? It would be a pity to have
> qemu-kvm just for that.

Nope, not on my schedule.

Jan


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to