From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: KVM usability
Date: Tue, 02 Mar 2010 16:13:41 +0100
Message-ID: <4B8D2B25.8040700@redhat.com>
References: <1608881698.266.1267537026723.JavaMail.root@yellowwing> <4B8D1F0F.40101@redhat.com> <20100302143709.GE7949@redhat.com> <4B8D2644.5020505@redhat.com> <20100302145642.GF7949@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Nikolai K. Bochev" <n.bochev@grandstarco.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Ingo Molnar <mingo@elte.hu>, Avi Kivity <avi@redhat.com>,
	Yanmin Zhang <yanmin_zhang@linux.intel.com>,
	ming m lin <ming.m.lin@intel.com>,
	sheng yang <sheng.yang@intel.com>,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	KVM General <kvm@vger.kernel.org>,
	Zachary Amsden <zamsden@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Cole Robinson <crobinso@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:18438 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753980Ab0CBPOb (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 2 Mar 2010 10:14:31 -0500
In-Reply-To: <20100302145642.GF7949@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 03/02/10 15:56, Daniel P. Berrange wrote:
>> Glad to hear that.  Are these bits in F12 virt-preview already?
>
> I believe so.

/me goes fetch updates to check it out.

>>> Migrating
>> >from another tool like VMWare  is a much harder than just importing
>>> the disk image, since you have to update the drivers inside the guest,
>>> likely reconfigure several config files, etc, etc. There is work on
>>> a full v2v tool to automate this task, for both Linux&   Windows guests.
>>
>> I meant migrating from another qemu management tool, be it some other
>> gui tool or self-baked shell scripts or something else.
>
> That's pretty much what the 'disk import' could deal with,  unless we wanted
> to provide a way to read the config files from those other  qemu mgmt tools
> directly on a case-by-case basis

What I'll expect:

At minimum a way to create a virtual machine without the auto-started 
installation, with no or minimal hardware plugged in, so I can configure 
it the way I want via "add hardware", then boot it.

Better would be some dialog to shortcut the "add hardware" clicking for 
the most common stuff, i.e. a single dialog box asking for disk image, 
nic type, mac address, sound card, serial console.  I guess this is 
roughly what the "disk import" feature will do for me.

Analyzing the guest image, trying to figure what nic, disk and mac 
address it expects and pre-filling the dialog box with the results would 
be really great.  I suspect that is alot of work for little gains, but 
hey, maybe the v2v tool has most of the bits needed for that anyway, so 
we can get that nevertheless.

cheers,
   Gerd