From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: Kvm migration problem Date: Wed, 14 Apr 2010 11:17:32 +0200 Message-ID: <4BC5882C.2050407@amd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: "Wagner, Kai" Return-path: Received: from va3ehsobe005.messaging.microsoft.com ([216.32.180.15]:26314 "EHLO VA3EHSOBE005.bigfish.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752542Ab0DNJRz (ORCPT ); Wed, 14 Apr 2010 05:17:55 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Wagner, Kai wrote: > Hey, > im from germany and new in kvm. I'll tried the how-to's from your > page to migrate an windows vmware .vmdk to a kvm image. Do you mean the lower paragraph of this one? http://www.linux-kvm.org/page/How_To_Migrate_From_Vmware_To_KVM > I'll also > tried so start the kvm with "kvm -drive file ..." but that also > wont work. I'll hope you could get me an answer how to migrate > my vmware .vmdk to an working kvm img. Have you used the right .vmdk? Sometimes VMware creates a small text file containing only a few hundred bytes of text describing the actual disk. If you convert (or use) this file, it will create (or use) an empty disk image. If "$ file foo.qcow2" reports something with "size 0 + 0", you should look into the original .vmdk file, find the real file name and convert (or use) this one. > edit: If i want to start the converted img it always told me, > that there is problem with the img. Can you tell us the actual message? HTH, Andre. -- Andre Przywara AMD-OSRC (Dresden) Tel: x29712