[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Xen HVM images on VMware ESX


  • To: Diwaker Gupta <diwaker.lists@xxxxxxxxx>
  • From: "Joseph L. Casale" <jcasale@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 24 Apr 2008 13:08:16 -0600
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 24 Apr 2008 12:09:23 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcimOWoVsiXqr3PpTaS2kXemt6vI3wABGV0l
  • Thread-topic: [Xen-users] Xen HVM images on VMware ESX

>So when I create a new VM in ESX, it create *two* VMDK files. The
>first is a descriptor file containing some meta data. The other
>(-flat.vmdk) is the real data. Running 'qemu-img info' on the flat
>VMDK indicates that it is in the RAW format.

Good, so you know the expected format of esx now.

>I tried overwriting both the VMDKs (flat and descriptor) with the VMDK
>converted using qemu-img, one at a time.

You lost me? I thought you fiogured out one is text pointer?

>Replacing the descriptor file
>leads to complaints saying IDE disk being used as SCSI disk and the VM
>crashes.

>Replacing the flat VMDK file doesn't lead to a crash, but I
>don't see anything on the console. Not even the BIOS stuff.

What crashes here specifically? What does your esx vm log say?

jlc

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.