[one-users] [one-ecosystem] vmware deployment problem

[Tino Vazquez]

Hi Paul,

This may be a problem with the name of the ESX's vSwitch, more
precisely it not being vmnic0. If you didn't change it, by default is
"VM Network".

>From the documentation:

--
Networks can be defined in OpenNebula, and VMs can use leases from
these networks, being FIXED or RANGED. The only requisite is to input
the name of the VMware hypervisor defined vSwitch as the bridge of the
Virtual Network in OpenNebula. The default name for the vSwitch in the
ESX family is “VM Network”.
--

Regards,

-Tino

--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org



On Tue, Oct 26, 2010 at 12:30 PM, Paul Piscuc <paul.piscuc at sinergetic.ro> wrote:
> Hi,
>
> The error we are getting is the following:
> in /var/10/oned.log:
>
> Tue Oct 26 12:24:30 2010 [VMM][I]: [VMWARE] cmd failed
> [/srv/cloud/one/bin/tty_expect -u oneadmin -p sinergetic01 virsh -c
> esx://vmware.local?no_verify=1 start one-9]. Stderr:
> Tue Oct 26 12:24:30 2010 [VMM][I]: error: Failed to start domain one-9
> Tue Oct 26 12:24:30 2010 [VMM][I]: error: internal error Could not start
> domain
> Tue Oct 26 12:24:30 2010 [VMM][I]:
> Tue Oct 26 12:24:30 2010 [VMM][I]: . Stdout: ExitCode: 1
> Tue Oct 26 12:24:30 2010 [VMM][I]: ExitCode: 1
> Tue Oct 26 12:24:30 2010 [VMM][E]: Error deploying virtual machine
> Tue Oct 26 12:24:30 2010 [DiM][I]: New VM state is FAILE
>
> On the ESX, the error is:
> ./messages:Oct 26 10:10:09 Hostd: [2010-10-26 10:10:09.552 FFFB5B90 info
> 'ha-eventmgr'] Event 375 : Cannot power On one-10 on localhost.sns.ro in
> ha-datacenter. A general system error occurred:
> ./messages:Oct 26 10:10:09 Hostd: [2010-10-26 10:10:09.552 FFFB5B90 info
> 'vm:/vmfs/volumes/a286fd9a-499da3b5/10/images/disk.0/one-10.vmx'] State
> Transition (VM_STATE_POWERING_ON -> VM_STATE_OFF)
> ./messages:Oct 26 10:10:09 Hostd: [2010-10-26 10:10:09.578 FFFB5B90 warning
> 'vm:/vmfs/volumes/a286fd9a-499da3b5/10/images/disk.0/one-10.vmx'] Unable to
> get network object for network vmnic0
>
> It seems that the problem is generated by the networking stuff. In onevnet,
> we have the following template:
>
> NAME = "Public"
> TYPE = RANGED
> BRIDGE = vmnic0
> NETWORK_SIZE=30
> NETWORK_ADDRESS=10.11.12.70
>
> We have tried to bridge over the interface eth0, but ESX tries to bridge
> also to eth0, and not to vmnic0. Maybe is something related to the vmx
> configuration file. It is not changed, is a image generated by ESX.
>
> Thank for your help,
>
>
>
> On Tue, Oct 26, 2010 at 12:59 PM, Tino Vazquez <tinova at fdi.ucm.es> wrote:
>>
>> Hi Paul,
>>
>> Can you check the $ONE_LOCATION/var/8/images/*/vmware.log to see what
>> is failing?
>>
>> Regards,
>>
>
>