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 <tartig...@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@lists.opennebula.org > > > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org