Re: [Qemu-devel] qemu-kvm: remove "boot=on|off" drive parameter compatibility

[Marcelo Tosatti]

On Mon, Oct 01, 2012 at 08:19:29AM -0500, Anthony Liguori wrote:
> Jan Kiszka <address@hidden> 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.

At the moment the only purpose of this command line options is for
compability with scripts. My view is that scripts are easily fixed,
so we can just drop them. No need to carry this to QEMU.

>  -drive ...,boot= <- this is ignored
> 
> cpu_set command for CPU hotplug which is known broken in qemu-kvm.
> 
> testdev which is nice but only used for development
>
> Default nic is rtl8139 vs. e1000.

Config file (as suggested earlier on this thread).

> Some logic to move change the default VGA ram size to 16mb for pc-1.2
> (QEMU uses 16mb by default now too).

Config file.

> I think at this point, none of this matters but I added the various
> distro maintainers to the thread.
> 
> I think it's time for the distros to drop qemu-kvm and just ship
> qemu.git.  Is there anything else that needs to happen to make that
> switch?
> 
> Regards,
> 
> Anthony Liguori
> 
> >
> > But I would really stop worrying about the qemu-kvm code base.
> >
> > Jan
> >
> > -- 
> > Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
> > Corporate Competence Center Embedded Linux
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to address@hidden
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html