From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fam Zheng Subject: Re: Qemu-img Date: Wed, 04 Dec 2013 09:18:20 +0800 Message-ID: <529E82DC.10903@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE To: RB , kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50290 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755638Ab3LDBS3 (ORCPT ); Tue, 3 Dec 2013 20:18:29 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 2013=E5=B9=B412=E6=9C=8804=E6=97=A5 07:47, RB wrote: > On Tue, Dec 3, 2013 at 4:26 PM, CDR wrote: >> In Fedora 20 >> rpm -qa | grep qemuqemu-img convert -O qcow2 Neustar-flat.vmdk >> /home/neustar.qcow2-img >> qemu-img-1.6.1-2.fc20.x86_64 >> but when I try to boot with the image, it fails. Please see the imag= e attached. >> So the conversion is unbootable. >> Any idea? > > I'd appreciate your not unicasting the query to me, it's a public > list. Your attached image indicates the guest VM started booting but > failed at some point, probably when trying to mount the root > partition. The format conversion appears to have worked, but it's no= t > going to fiddle the internals of the image if it was dependent on > something specific to VMware. I don't see the screenshot here but... Telling from the file name, this vmdk file should be in fact a "raw"=20 disk and the conversion shouldn't be a problem (you can use `xxd -l 512= =20 Neustar-flat.vmdk` to see if it's simply an MBR, or containing "KDMV"=20 magic in the first bytes). It might be the guest OS driver or configuration that don't=20 automatically work on kvm. How did you export this vmdk from ESX, what'= s=20 the guest OS, and what's your command line to boot it? =46am