[one-users] vmware deploy error: raw driver
Tino Vazquez
tinova at opennebula.org
Wed May 4 06:41:17 PDT 2011
Hi Antoni,
This feature has been introduced by ticket [1]. Unfortunately, it has
not been tested against VMware server. I've opened another ticket [2]
to avoid a mandatory default value for the disk driver.
Meanwhile, you can change LibVirtDriverVMware.cc from
--
if ( !driver.empty() )
{
file << driver << "'/>" << endl;
}
else
{
file << default_driver << "'/>" << endl;
}
--
to
--
if ( !driver.empty() )
{
file << driver << "'/>" << endl;
}
--
Regards,
-Tino
[1] http://dev.opennebula.org/issues/517
[2] http://dev.opennebula.org/issues/611
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Wed, May 4, 2011 at 1:27 PM, antoni artigues <tartigues at iac3.eu> wrote:
> Hello
>
> I'm not usint ESX. I'm using vmware server 2.0.2
>
> And now. How I can solve my problem? I have to change the
> LibVirtDriverVMware.cc and recompile and reinstall my opennebula?
>
> Thanks in advance
>
> Antoni Artigues
>
> El mié, 04-05-2011 a las 12:52 +0200, Tino Vazquez escribió:
>> Hi Antoni,
>>
>> Which version of ESX are you using? When developing the drivers, I
>> found that the driver line didn't impede the deployment of VMs. If
>> with other ESX versions this is a problem, I will make it an optional
>> parameter with no hardcoded value to avoid this kind of situations.
>>
>> Best regards,
>>
>> -Tino
>>
>> --
>> Constantino Vázquez Blanco, MSc
>> OpenNebula Major Contributor
>> www.OpenNebula.org | @tinova79
>>
>>
>>
>> On Tue, May 3, 2011 at 3:43 PM, antoni artigues <tartigues at iac3.eu> wrote:
>> > Hi Tino
>> >
>> > With the "file" driver we obtain the same error:
>> >
>> > --------------------------
>> > $ /srv/cloud/one/bin/tty_expect -u oneadmin -p oneadmin10 virsh -c
>> > gsx://oscarnode9/?no_verify=1 define /srv/cloud/one/var/76/deployment.0
>> >
>> > error: Failed to define domain from /srv/cloud/one/var/76/deployment.0
>> > error: internal error Unknown driver name 'file'
>> > -------------------------
>> >
>> > However, If I delete the driver line from deployment.0 the tty command
>> > works well.
>> >
>> > Is it possible that the documentation is correct?
>> >
>> > Thanks in advance
>> >
>> > Antoni Artigues
>> >
>> > El mar, 03-05-2011 a las 15:16 +0200, Tino Vazquez escribió:
>> >> Hi Antoni,
>> >>
>> >> I believe this is a bug in the documentation. Please do try the following:
>> >>
>> >> DISK=[IMAGE="vmUbuntu",
>> >> TARGET="sda",
>> >> BUS="scsi",
>> >> DRIVER="file"]
>> >>
>> >>
>> >> If this works, I will update the doc.
>> >>
>> >> BTW, what version of ESX are you using?
>> >>
>> >> Regards,
>> >>
>> >> -Tino
>> >>
>> >> --
>> >> Constantino Vázquez Blanco, MSc
>> >> OpenNebula Major Contributor
>> >> www.OpenNebula.org | @tinova79
>> >>
>> >>
>> >>
>> >> On Tue, May 3, 2011 at 1:44 PM, antoni artigues <tartigues at iac3.eu> wrote:
>> >> > Hi
>> >> >
>> >> > I think the problem is in the "LibVirtDriverVMware.cc" file
>> >> >
>> >> > In opennebula 2.0.1 the <driver> option is not written to deployment.0
>> >> >
>> >> > However, in opennebula 2.2 the "LibVirtDriverVMware.cc" contains this
>> >> > new lines:
>> >> > ---------------------------------
>> >> > file << "\t\t\t<driver name='";
>> >> >
>> >> > if ( !driver.empty() )
>> >> > {
>> >> > file << driver << "'/>" << endl;
>> >> > }
>> >> > else
>> >> > {
>> >> > file << default_driver << "'/>" << endl;
>> >> > }
>> >> > ---------------------------------
>> >> >
>> >> > Why always creates the <driver> tag if it is not supported in vmware?
>> >> >
>> >> > Thanks in advance
>> >> >
>> >> > Antoni Artigues
>> >> >
>> >> > El mar, 03-05-2011 a las 13:37 +0200, antoni artigues escribió:
>> >> >> Hi Tino
>> >> >>
>> >> >> Okey. But in the documentation, for the driver option, It says:
>> >> >> "Specific image mapping driver. KVM: raw, qcow2. Xen:tap:aio:, file:.
>> >> >> VMware unsupported"
>> >> >>
>> >> >> So, it's not a supported option for VMware.
>> >> >>
>> >> >> In my older version of openneula, my deployment.0 don't have the
>> >> >> "<driver name='raw'/>" line, and this works fine.
>> >> >>
>> >> >> How can I delete the driver line in this openNebula version? or What is
>> >> >> the correct default value for the driver option?
>> >> >>
>> >> >> Here is my vmm_sh_vmware.conf:
>> >> >> -----------------------------
>> >> >> CPU = 1
>> >> >> MEMORY = 256
>> >> >> OS = [ ARCH = i686 ]
>> >> >>
>> >> >> # Name of the datastore in the remote VMware hypervisors
>> >> >> # mounting $ONE_LOCATION/var exported as a nfs share
>> >> >> # by the OpenNebula front-end
>> >> >>
>> >> >> DATASTORE = vmdatastore
>> >> >> -----------------------------
>> >> >>
>> >> >> Thanks in advance
>> >> >>
>> >> >> Antoni Artigues
>> >> >>
>> >> >>
>> >> >> El mar, 03-05-2011 a las 13:13 +0200, Tino Vazquez escribió:
>> >> >> > Hi Antoni,
>> >> >> >
>> >> >> > The "raw" value for the disk driver is the default value, hardcoded
>> >> >> > in the OPenNebula Core VMware driver. This is overridden by:
>> >> >> >
>> >> >> > * $ONE_LOCATION/etc/vmm_sh/vmm_sh_vmware.conf
>> >> >> > * The VM template, DISK section, DRIVER label.
>> >> >> >
>> >> >> > Regards,
>> >> >> >
>> >> >> > -Tino
>> >> >> >
>> >> >> > --
>> >> >> > Constantino Vázquez Blanco, MSc
>> >> >> > OpenNebula Major Contributor
>> >> >> > www.OpenNebula.org | @tinova79
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Tue, May 3, 2011 at 10:36 AM, antoni artigues <tartigues at iac3.eu> wrote:
>> >> >> > > Hello
>> >> >> > >
>> >> >> > > I'm using the last version of opennebula and vmware drivers addon.
>> >> >> > >
>> >> >> > > My image description is:
>> >> >> > >
>> >> >> > > ------------------------------------------
>> >> >> > > ME="vmUbuntu"
>> >> >> > > VCPU = 1
>> >> >> > > MEMORY = 1024
>> >> >> > > OS = [ ARCH = "x86_64" ]
>> >> >> > > DISK=[IMAGE="vmUbuntu",
>> >> >> > > TARGET="sda",
>> >> >> > > BUS="scsi"]
>> >> >> > > NIC=[NETWORK="vmware LAN bridged"]
>> >> >> > > ------------------------------------------
>> >> >> > >
>> >> >> > > When we try to create the image we obtain this error:
>> >> >> > >
>> >> >> > > ----------------------------
>> >> >> > > /srv/cloud/one/bin/tty_expect -u oneadmin -p xxxxxxxxx virsh -c
>> >> >> > > gsx://oscarnode9/?no_verify=1 define /srv/cloud/one/var/73/deployment.0
>> >> >> > >
>> >> >> > > error: Failed to define domain from /srv/cloud/one/var/73/deployment.0
>> >> >> > > error: internal error Unknown driver name 'raw'
>> >> >> > > ----------------------------
>> >> >> > >
>> >> >> > > We see that in the deployment.0 file there is a driver called "raw", but
>> >> >> > > we haven't defined this driver in the image description. Is it a bug
>> >> >> > > from openNebula?
>> >> >> > >
>> >> >> > > Here is the deployment.o:
>> >> >> > >
>> >> >> > > -------------------------------
>> >> >> > > <domain type='vmware'>
>> >> >> > > <name>one-73</name>
>> >> >> > > <vcpu>1</vcpu>
>> >> >> > > <memory>1048576</memory>
>> >> >> > > <os>
>> >> >> > > <type arch='x86_64'>hvm</type>
>> >> >> > > </os>
>> >> >> > > <devices>
>> >> >> > > <disk type='file' device='disk'>
>> >> >> > > <source file='[vmdatastore] 73/images/disk.0/disk.vmdk'/>
>> >> >> > > <target dev='sda' bus='scsi'/>
>> >> >> > > <driver name='raw'/>
>> >> >> > > </disk>
>> >> >> > > <interface type='bridge'>
>> >> >> > > <source bridge='Bridged'/>
>> >> >> > > <mac address='02:00:c0:a8:03:01'/>
>> >> >> > > </interface>
>> >> >> > > </devices>
>> >> >> > > </domain>
>> >> >> > > -------------------------------
>> >> >> > >
>> >> >> > > Thanks in advance
>> >> >> > >
>> >> >> > > Regards
>> >> >> > >
>> >> >> > > _______________________________________________
>> >> >> > > Users mailing list
>> >> >> > > Users at lists.opennebula.org
>> >> >> > > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>> >> >> > >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >
>> >
>> >
>
>
>
More information about the Users
mailing list