VMware vSphere

 View Only
  • 1.  DMotion Timeout with Hot Migration

    Posted Jul 31, 2007 07:23 PM

    Hi,

    I'm seaching and searching and can't find any answer to my issue so there it is !

    I have some issue with DMotion, I have 2 ESX (A) 2.5.3 and (B) 3.0.1. In the same farm in VC2.0.1. ESX B can see all LUNs of ESX A.

    ESX A is connect to different SAN storage then ESX B. (This is to transfer from a HP SAN to a EMC SAN, I don't think this is the issue)

    Unknow Warning message:[/u]

    When I try to do a Cold Migration or Hot Migration I receive this Warning message: "Migration will cause the virtual machine's configuration to be modified, to preserver the CPU feature requirement for its guest OS"[/i]

    With a Cold Migration the process go over without no issue.

    When I try to do this with a Hot Migration(VM power ON) the process say at 1% and 4-5min after I receive "Operation Time out"[/i]

    Both ESX are HP DL385 G1 Opteron 275.

    Also I receive thos errors in the vmware.log of the vm that I try to migrate.

    Jul 31 14:34:36: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#41a4ffef1e9b4ab0/vmx/migrateState/cmd/##1_60/op/=to

    Jul 31 14:34:36: vmx| VmxMigrateGetParam: srcIp=0x8d771d53 dstIp=0x8d771d52 mid=ab01e8a5 uuid=33383236-3038-5553-4536-33314e323251 priority=low

    Jul 31 14:34:36: vmx| MigrateSetInfo: state=1 srcIp=<141.119.29.83> dstIp=<141.119.29.82> mid=2869029029 uuid=33383236-3038-5553-4536-33314e323251 priority=low

    Jul 31 14:34:36: vmx| MigrateStateUpdate: Transitioning from state 0 to 1.

    Jul 31 14:34:38: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#41a4ffef1e9b4ab0/vmx/migrateState/cmd/##1_61/op/=start

    Jul 31 14:34:38: vmx| VmxMigrateGetStartParam: mid=ab01e8a5 dstwid=1065

    Jul 31 14:34:38: vmx| VMMon_InitMigration: Invalid argument

    Jul 31 14:34:38: vmx| MigrateStatusFailure: Failed to initialize migration at source. Error 16[/b]. Invalid argument.

    Jul 31 14:34:38: vmx|

    Jul 31 14:34:38: vmx| MigrateSetInfo: state=5 srcIp=<0.0.0.0> dstIp=<0.0.0.0> mid=0 uuid=(null) priority=(null)

    Jul 31 14:34:38: vmx| MigrateStateUpdate: Transitioning from state 1 to 5.

    Jul 31 14:34:38: vmx| Migrate_ClearDoneState: cleared state. State was 5.

    Jul 31 14:34:38: vmx| MigrateStateUpdate: Transitioning from state 5 to 0.

    Jul 31 14:34:38: vmx| Migrate from failed with error -22[/b].

    If that can help is is the vmx file after a cold migration

    config.version = "6"

    virtualHW.version = "3"

    floppy0.present = "true"

    powerType.powerOff = "default"

    powerType.powerOn = "default"

    powerType.suspend = "default"

    powerType.reset = "default"

    displayName = "Clone-2 of QK0H"

    extendedConfigFile = "Clone-2 of QK0H.vmxf"

    scsi0.present = "true"

    scsi0.sharedBus = "none"

    scsi0.virtualDev = "vmxlsilogic"

    memsize = "1024"

    scsi0:0.present = "true"

    scsi0:0.name = "Clone-2 of QK0H.vmdk"

    scsi0:0.deviceType = "scsi-hardDisk"

    scsi0:1.present = "true"

    scsi0:1.name = "Clone-2 of QK0H_1.vmdk"

    scsi0:1.deviceType = "scsi-hardDisk"

    ide0:0.present = "true"

    ide0:0.fileName = "/dev/cdrom"

    ide0:0.deviceType = "atapi-cdrom"

    ide0:0.startConnected = "false"

    floppy0.startConnected = "false"

    floppy0.fileName = "/dev/fd0"

    ethernet0.present = "true"

    ethernet0.virtualDev = "vmxnet"

    ethernet0.wakeOnPcktRcv = "false"

    ethernet0.networkName = "Vlan-Isolated-UTC"

    ethernet0.addressType = "vpx"

    ethernet0.generatedAddress = "00:50:56:bd:18:1b"

    ethernet1.present = "true"

    ethernet1.startConnected = "false"

    ethernet1.virtualDev = "vmxnet"

    ethernet1.wakeOnPcktRcv = "false"

    ethernet1.networkName = "Production"

    ethernet1.addressType = "vpx"

    ethernet1.generatedAddress = "00:50:56:bd:05:f7"

    guestOS = "winNetStandard"

    uuid.bios = "50 3d a8 da 6e 1c 98 5b-f3 bc 8d 69 c6 0b ac 8b"

    log.fileName = "vmware.log"

    sched.cpu.min = "0"

    sched.cpu.units = "mhz"

    sched.cpu.shares = "normal"

    sched.cpu.affinity = "all"

    sched.mem.minsize = "0"

    sched.mem.max = "1024"

    sched.mem.shares = "normal"

    sched.mem.affinity = "all"

    [i]cpuid.1.eax = "--xxxxxxxx--


    "

    cpuid.80000001.ecx = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0"

    cpuid.80000001.edx = "xx0xxxxxxxx0xxxxxxxxxxxxxxxxxxxx"[/i][/u]

    checkpoint.cptconfigname = "Clone-2 of QK0H"

    draw = "gdi"

    isolation.tools.dnd.disable = "true"

    priority.grabbed = "normal"

    priority.ungrabbed = "normal"

    remotedisplay.depth = "16"

    tools.synctime = "TRUE"

    cpuid stuff above it's allright ?

    Thank you !



  • 2.  RE: DMotion Timeout with Hot Migration
    Best Answer

    Posted Aug 01, 2007 10:34 AM

    When you talk about successfull cold migration are you talking about a VC Migrate operation or file move?

    the message is because you have different cpus on source and target.

    You can apply masking to do a Hot migration.

    Look at this thread:

    http://www.vmware.com/community/thread.jspa?threadID=95961&tstart=0