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

Re: [Xen-users] moving a VMWare image to Xen / conversion?


  • To: "Petrescu, Florin" <fpetrescu@xxxxxxxxxxxxxxxx>
  • From: Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx>
  • Date: Wed, 12 May 2010 17:07:07 -0300
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 12 May 2010 13:09:29 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=rqEpbngN/TBgnr7z96RQdjT2lG7/w1D84yEvhz0sunjl6UdyjO8OYBG8PeaLoOD8vR PYEGtJS0k4s4yrfB0R0Sq75YHEnyMlQ0bVydw+aPxKP0NvAQR1AOvU6Qi1qyDv4g6Tsw u/si73mn8XvgOxXzVfQyeEBk3SLDIuUkgC+PQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Check if the kernel of your CentOS have the option "CONFIG_XEN=y"... Maybe that is the problem...

On 12 May 2010 17:01, Petrescu, Florin <fpetrescu@xxxxxxxxxxxxxxxx> wrote:

Greetings,

 

I have a CentOS VMware image with two vmdk files/disks which are flattened (34 and 21G)

I have checked the image by opening it in VMPlayer, and it opened just fine.

I have used qemu-img convert on both of them to and save them as *.img

(they were raw anyway, but I don’t believe that it did change anything)

Here is the XYZ_VM.vmx file content:

------------------------------------ XYZ_VM.vmx ---------------------------------------

#!/usr/bin/vmware

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "7"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

nvram = "XYZ_VM.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

unity.customColor = "|23c0c0c0"

tools.upgrade.policy = "useGlobal"

powerType.powerOff = "hard"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "hard"

 

displayName = "XYZ_VM"

extendedConfigFile = "XYZ_VM.vmxf"

 

scsi0.present = "TRUE"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "XYZ_VM.vmdk"

scsi0:0.deviceType = "disk"

scsi0:1.present = "TRUE"

scsi0:1.fileName = "XYZ_VM_1.vmdk"

scsi0:1.deviceType = "disk"

ide0:0.present = "TRUE"

ide0:0.clientDevice = "TRUE"

ide0:0.deviceType = "cdrom-raw"

ide0:0.startConnected = "FALSE"

ethernet0.present = "TRUE"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.networkName = "VM Network"

ethernet0.addressType = "vpx"

guestOS = "other26xlinux"

uuid.location = "56 4d b0 75 2a 96 ff 08-91 ad 69 63 37 58 88 84"

uuid.bios = "56 4d b0 75 2a 96 ff 08-91 ad 69 63 37 58 88 84"

vc.uuid = "52 70 33 58 04 2e 49 01-85 68 26 9b e7 4a ea ab"

 

 

ethernet0.generatedAddress = "00:50:56:ba:61:cb"

tools.syncTime = "FALSE"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

sched.swap.derivedName = "/vmfs/volumes/4a6f5302-2d18ac2b-4b9b-002219502c60/XYZ_VM/XYZ_VM-3193663b.vswp"

scsi0:0.redo = ""

scsi0:1.redo = ""

vmotion.checkpointFBSize = "16777216"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

vmci0.pciSlotNumber = "33"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "-1137182814"

hostCPUID.0 = "0000000a756e65476c65746e49656e69"

guestCPUID.0 = "0000000a756e65476c65746e49656e69"

userCPUID.0 = "0000000a756e65476c65746e49656e69"

hostCPUID.1 = "0001067600040800000ce3bdbfebfbff"

guestCPUID.1 = "0001067600010800800822010febfbff"

userCPUID.1 = "0001067600040800000822010febfbff"

hostCPUID.80000001 = "00000000000000000000000120100800"

guestCPUID.80000001 = "00000000000000000000000120100800"

userCPUID.80000001 = "00000000000000000000000120100800"

evcCompatibilityMode = "FALSE"

 

ethernet0.startConnected = "TRUE"

 

tools.remindInstall = "TRUE"

floppy0.present = "FALSE"

replay.filename = ""

---------------------------------------------------------------------------------------

 

I have created a config file called XYZ_XENVM which looks like this:

 

------------------------------------ XYZ_XENVM ----------------------------------------

name = "XYZ_XENVM"

# uuid = "f2030423-963f-e7d5-4bef-6bb47f1d0c99"

uuid =   "52703358-042e-4901-8568-269be74aeaab"

maxmem = 4096

memory = 4096

vcpus = 2

bootloader = "/usr/bin/pygrub"

>

>

>

vfb = [ "type=vnc,vncunused=0,vncdisplay=53126,keymap=en-us" ]

disk = [ 'file:/wa2/ATC5/XYZ_VM-flat.img,xvda,w',\

'file:/wa2/ATC5/XYZ_VM_1-flat.img,xvdb,w' ]

root="/dev/xvda1"

vif = [ "mac=00:50:56:ba:61:cb,bridge=xenbr0,script=vif-bridge" ]

---------------------------------------------------------------------------------------

 

I am using "xm create XYZ_XENVM" but getting the following error:

 

[root@TServerA xen]# xm create XYZ_XENVM

Using config file "./XYZ_XENVM".

Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n')

[root@TServerA xen]#

 

ANY help would be highly appreciated!

 

Thanks much,

 

FPT

 

 

 

 
The materials in this message are private and may contain Protected Healthcare Information. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

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

_______________________________________________
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®.