[one-users] suspend vm on esxi 5

Tino Vazquez tinova at opennebula.org
Fri Mar 23 05:53:09 PDT 2012


Hi Carlo,

This may be an issue then with the version of the disk. You may want
to try converting it to a later format using VMware Converter.

Regards,

-Tino

--
Constantino Vázquez Blanco, MSc
Project Engineer
OpenNebula - The Open-Source Solution for Data Center Virtualization
www.OpenNebula.org | @tinova79 | @OpenNebula



On Thu, Mar 22, 2012 at 5:54 PM, Carlo Bongiovanni
<c.bongiovanni at liberologico.com> wrote:
> Hi,
>
> Il 22 marzo 2012 17:38, Tino Vazquez <tinova at opennebula.org> ha scritto:
>> Hi,
>>
>> The .vmx file is created by libvirt. OpenNebula can be tailored to add
>> the line in the file, but I think is better to identify the problem.
>>
>>  1) Are you using a .vmdk disk created in esx5, or are you importing
>> from previous versions?
>
> the .vmdk is created from a vmware server (don't know which version)
>
>>  2) If you add the line, can you create snapshots?
>
> I haven't tried this one
>
>>  3) If you create a new VM from scratch, and do a snapshot using the
>> VI client, does it work?
>
> I only tried such a command, by ssh connecting to esxi server, and it
> worked smoothly:
>
> vim-cmd vmsvc/power.suspend Vmid
>
>
>>
>> Regards,
>>
>> -Tino
>>
>
>
> thanks
> c.
>
>> --
>> Constantino Vázquez Blanco, MSc
>> Project Engineer
>> OpenNebula - The Open-Source Solution for Data Center Virtualization
>> www.OpenNebula.org | @tinova79 | @OpenNebula
>>
>>
>>
>> On Thu, Mar 22, 2012 at 5:27 PM, Carlo Bongiovanni
>> <c.bongiovanni at liberologico.com> wrote:
>>> Hi All,
>>>
>>> I configured opennebula to use esxi 5 as hypervisor. The instantiate,
>>> shutdown, reboot commands work properly. I'm now testing the suspend
>>> function but I have such a problem:
>>>
>>> from sunstone I choose a RUNNING vm and suspend it, it goes in
>>> SAVE_SUSPEND state, then it goes in UNKNOWN one.
>>>
>>> first he tries to suspend
>>> Thu Mar 22 17:15:45 2012 [ReM][D]: VirtualMachineAction method invoked
>>> Thu Mar 22 17:15:45 2012 [DiM][D]: Suspending VM 36
>>>
>>> then I can see from vsphere that he cancels the operation because of a
>>> "full disk error"
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 Command
>>> execution fail: /srv/cloud/one/var/remotes/vmm/vmware/save one-36
>>> /srv/cloud/one/var//3
>>> 6/images/checkpoint vmware001 36 vmware001
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG E 36 save:
>>> Error executing: virsh -c 'esx://vmware001/?no_verify=1&auto_answer=1'
>>> suspend one-36 err
>>> : ExitCode: 1
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 out:
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 error:
>>> Failed to suspend domain one-36
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 error:
>>> internal error Could not suspend domain: InvalidState - The operation
>>> cannot be allowed
>>> at the current time because the virtual machine has a question pending:
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36
>>> 'msg.vmxaiomgr.retryabort.diskfull:The operation on the file
>>> "/vmfs/devices/multiextent/6979cbe4-disk-000001-s001.vmdk" failed (The
>>> file is too large).
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 The file
>>> system where disk
>>> "/vmfs/devices/multiextent/6979cbe4-disk-000001-s001.vmdk" resides is
>>> full.
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 Select
>>> Retry to attempt the operation again.
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 Select
>>> Cancel to end the session.
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 '.
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 ExitCode: 1
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: LOG I 36 Failed
>>> to execute virtualization driver operation: save.
>>>
>>> Thu Mar 22 17:19:19 2012 [VMM][D]: Message received: SAVE FAILURE 36 -
>>>
>>> Thu Mar 22 17:19:21 2012 [VMM][D]: Message received: LOG I 36 ExitCode: 0
>>>
>>> Thu Mar 22 17:19:21 2012 [VMM][D]: Message received: POLL SUCCESS 36 STATE=a
>>>
>>> I googled and found a possible solution:
>>> http://stanis.net/2012/02/error-creating-snapshot-on-virtual-machine-cannot-write-to-multiextents/
>>>
>>> but it requires to append a line to the vmx file used by the vm:
>>> workingDir = “/vmfs/volumes/4f062853-20101bf0-21bf-d4bed9af57d2/Name
>>> of Virtual Machine Folder Here/”
>>>
>>> Such a file is created by opennebula.. how could I change it in order
>>> to make it work?
>>>
>>> thanks for any help
>>> kind regards
>>>
>>> --
>>> Carlo Bongiovanni
>>>
>>> Liberologico S.r.l.
>>> web: www.liberologico.com
>>> Address: Sardegna Ricerche, Edificio 2
>>> Località Piscinamanna
>>> 09010 Pula (CA) - Italia
>>> Tel. +39 070 9243.2647
>>> callto://pacman81
>>> gtalk: carlo.bongiovanni
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>
>
>
> --
> Carlo Bongiovanni
>
> Liberologico S.r.l.
> web: www.liberologico.com
> Address: Sardegna Ricerche, Edificio 2
> Località Piscinamanna
> 09010 Pula (CA) - Italia
> Tel. +39 070 9243.2647
> callto://pacman81
> gtalk: carlo.bongiovanni



More information about the Users mailing list