Re: [one-users] vmware deploy error: raw driver
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 tartig...@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 tartig...@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\tdriver 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 x 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'
nameone-73/name
vcpu1/vcpu
memory1048576/memory
os
type arch='x86_64'hvm/type
/os
devices
disk type='file' device='disk'
source file='[vmdatastore]
Re: [one-users] vmware deploy error: raw driver
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 tartig...@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 tartig...@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\tdriver 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 x 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
Re: [one-users] vmware deploy error: raw driver
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 tartig...@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 tartig...@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 tartig...@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\tdriver 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:
[one-users] vmware deploy error: raw driver
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 x 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' nameone-73/name vcpu1/vcpu memory1048576/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
Re: [one-users] vmware deploy error: raw driver
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 x 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' nameone-73/name vcpu1/vcpu memory1048576/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
Re: [one-users] vmware deploy error: raw driver
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 x 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' nameone-73/name vcpu1/vcpu memory1048576/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
Re: [one-users] vmware deploy error: raw driver
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\tdriver 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 x 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'
nameone-73/name
vcpu1/vcpu
memory1048576/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
Re: [one-users] vmware deploy error: raw driver
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 tartig...@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\tdriver 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 x 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'
nameone-73/name
vcpu1/vcpu
memory1048576/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
Re: [one-users] vmware deploy error
Hello I solved the problem. The vmware server couldn't read from the nfs file system. I have had to click on the refresh option in the data store section. Now I have another problem when I try to deploy the vm: - Thu Feb 17 15:09:38 2011 [LCM][I]: New VM state is BOOT Thu Feb 17 15:09:38 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/16/deployment.0 Thu Feb 17 15:09:39 2011 [VMM][I]: Command execution fail: /srv/cloud/one/lib/remotes/vmm/vmware/deploy oscarnode4 /srv/cloud/one/var/16/deployment.0 Thu Feb 17 15:09:40 2011 [VMM][I]: STDERR follows. Thu Feb 17 15:09:40 2011 [VMM][I]: ExitCode: 255 Thu Feb 17 15:09:40 2011 [VMM][E]: Error deploying virtual machine Thu Feb 17 15:09:40 2011 [DiM][I]: New VM state is FAILED Thu Feb 17 15:09:40 2011 [TM][W]: Ignored: TRANSFER SUCCESS 16 - -- I enter in the VI web access and I can see the one-16 registered as virtual machine, but it is stopped. I tried this: 1.Unregister the vm one-16 from the vmware server. 2.Preserve all the disk.0 files generated. 3.Delete the vm from opennebula with onevm delete 16 4.Execute from the command line /srv/cloud/one/lib/remotes/vmm/vmware/deploy oscarnode4 /srv/cloud/one/var/16/deployment.0 5.And the vm starts correctly! Why in opennebula fails??? I can't see more information about the error in the logs. I don't know here is the problem. Thanks in advance Regards Antoni Artigues El mié, 16-02-2011 a las 13:21 +0100, antoni artigues escribió: Hi Thanks for the answer. Well, the opennebula deletes the images folder after the error. But, I have been watching the disk.0 folder, before the error, and I haven't seen the one-5.vmx file. When it is generated? Regards Antoni Artigues El mié, 16-02-2011 a las 12:07 +0100, Tino Vazquez escribió: Hi Antoni, There is a couple of things we can check to find out the problem: * Is there in the front-end the following files: * $ONE_LOCATION/var/5/images/disk.0/disk.vmdk * $ONE_LOCATION/var/5/images/disk.0/one-5.vmx * If the above is true, try registering the one-5.vmx VM using the VI client (windows needed). Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Wed, Feb 16, 2011 at 9:19 AM, antoni artigues tartig...@iac3.eu wrote: : internal error HTTP response code 503 for upload to ___ 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
[one-users] vmware deploy error
Hello I'm still with the same problem. I'm using opennebula 2.0.1, vmware driver addon, and vmware server 2.0.2 I can't be able to deploy a vm into any cluster node. The error is at domain definition: Failed to define domain from /srv/cloud/one/var/5/deployment.0 The vm template is: -- NAME=ubuntuVM VCPU = 1 MEMORY = 1024 OS = [ ARCH = i686 ] DISK=[IMAGE=myVMwareVM] NIC=[NETWORK=vmware LAN] -- the domain file is: - domain type='vmware' nameone-5/name vcpu1/vcpu memory1048576/memory os type arch='i686'hvm/type /os devices disk type='file' device='disk' source file='[cloudds] 5/images/disk.0/disk.vmdk'/ target dev='hda'/ /disk interface type='bridge' source bridge='vmnet0'/ mac address='02:00:c0:a8:05:03'/ /interface /devices /domain - I try to execute the virsh command directly with this result: --- root@cloudmaster:# virsh -c gsx://oscarnode5?no_verify=1 define /srv/cloud/one/var/5/deployment.0 Enter username for oscarnode5 [root]: oneadmin Enter oneadmin's password for oscarnode5: error: Failed to define domain from /srv/cloud/one/var/5/deployment.0 error: internal error HTTP response code 503 for upload to 'https://oscarnode5:8333/folder/5%2fimages%2fdisk%2e0/one% 2d5.vmx?dcPath=ha%2ddatacenterdsName=cloudds' -- the complete log error is: --- Wed Feb 16 09:02:42 2011 [LCM][I]: New VM state is BOOT Wed Feb 16 09:02:42 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/5/deployment.0 Wed Feb 16 09:02:43 2011 [VMM][I]: Command execution fail: /srv/cloud/one/lib/remotes/vmm/vmware/deploy oscarnode5 /srv/cloud/one/var/5/deployment.0 Wed Feb 16 09:02:43 2011 [VMM][I]: STDERR follows. Wed Feb 16 09:02:43 2011 [VMM][I]: [VMWARE] cmd failed [/srv/cloud/one/bin/tty_expect -u oneadmin -p oneadmin10 virsh -c gsx://oscarnode5?no_verify=1 define /srv/cloud/one/var/5/deployment.0 ]. Stderr: Wed Feb 16 09:02:43 2011 [VMM][I]: error: Failed to define domain from /srv/cloud/one/var/5/deployment.0 Wed Feb 16 09:02:43 2011 [VMM][I]: error: internal error HTTP response code 503 for upload to 'https://oscarnode5:8333/folder/5%2fimages%2fdisk %2e0/one%2d5.vmx?dcPath=ha%2ddatacenterdsName=cloudds' Wed Feb 16 09:02:43 2011 [VMM][I]: Wed Feb 16 09:02:43 2011 [VMM][I]: . Stdout: ExitCode: 1 Wed Feb 16 09:02:43 2011 [VMM][I]: ExitCode: 1 Wed Feb 16 09:02:43 2011 [VMM][E]: Error deploying virtual machine Wed Feb 16 09:02:43 2011 [DiM][I]: New VM state is FAILED --- Thanks in advance regards Antoni Artigues El mar, 15-02-2011 a las 14:50 +0100, antoni artigues escribió: Hello I'm trying to deploy a vm in vmware server. But the final state is fail. Here is the vm log: Tue Feb 15 14:43:48 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: Command execution fail: /srv/cloud/one/lib/remotes/vmm/vmware/deploy oscarnode5 /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: STDERR follows. Tue Feb 15 14:43:49 2011 [VMM][I]: [VMWARE] cmd failed [/srv/cloud/one/bin/tty_expect -u oneadmin -p oneadmin10 virsh -c gsx://oscarnode5?no_verify=1 define /srv/cloud/one/var/1/deployment.0]. Stderr: Tue Feb 15 14:43:49 2011 [VMM][I]: error:Falló al definir un dominio para /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: error:error interno Código de respuesta HTTP 503 para enviar a 'https://oscarnode5:8333/folder/1% 2fimages%2fdisk%2e0/one%2d1.vmx?dcPath=ha%2ddatacenterdsName=cloudds' Tue Feb 15 14:43:49 2011 [VMM][I]: Tue Feb 15 14:43:49 2011 [VMM][I]: . Stdout: ExitCode: 1 Tue Feb 15 14:43:49 2011 [VMM][I]: ExitCode: 1 I don't know where could be the error. Thanks in advance regards Antoni Artigues ___ 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
Re: [one-users] vmware deploy error
Hi Antoni, There is a couple of things we can check to find out the problem: * Is there in the front-end the following files: * $ONE_LOCATION/var/5/images/disk.0/disk.vmdk * $ONE_LOCATION/var/5/images/disk.0/one-5.vmx * If the above is true, try registering the one-5.vmx VM using the VI client (windows needed). Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Wed, Feb 16, 2011 at 9:19 AM, antoni artigues tartig...@iac3.eu wrote: : internal error HTTP response code 503 for upload to ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] vmware deploy error
Hi Thanks for the answer. Well, the opennebula deletes the images folder after the error. But, I have been watching the disk.0 folder, before the error, and I haven't seen the one-5.vmx file. When it is generated? Regards Antoni Artigues El mié, 16-02-2011 a las 12:07 +0100, Tino Vazquez escribió: Hi Antoni, There is a couple of things we can check to find out the problem: * Is there in the front-end the following files: * $ONE_LOCATION/var/5/images/disk.0/disk.vmdk * $ONE_LOCATION/var/5/images/disk.0/one-5.vmx * If the above is true, try registering the one-5.vmx VM using the VI client (windows needed). Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Wed, Feb 16, 2011 at 9:19 AM, antoni artigues tartig...@iac3.eu wrote: : internal error HTTP response code 503 for upload to ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] vmware deploy error
Hello I'm trying to deploy a vm in vmware server. But the final state is fail. Here is the vm log: Tue Feb 15 14:43:48 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: Command execution fail: /srv/cloud/one/lib/remotes/vmm/vmware/deploy oscarnode5 /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: STDERR follows. Tue Feb 15 14:43:49 2011 [VMM][I]: [VMWARE] cmd failed [/srv/cloud/one/bin/tty_expect -u oneadmin -p oneadmin10 virsh -c gsx://oscarnode5?no_verify=1 define /srv/cloud/one/var/1/deployment.0]. Stderr: Tue Feb 15 14:43:49 2011 [VMM][I]: error:Falló al definir un dominio para /srv/cloud/one/var/1/deployment.0 Tue Feb 15 14:43:49 2011 [VMM][I]: error:error interno Código de respuesta HTTP 503 para enviar a 'https://oscarnode5:8333/folder/1% 2fimages%2fdisk%2e0/one%2d1.vmx?dcPath=ha%2ddatacenterdsName=cloudds' Tue Feb 15 14:43:49 2011 [VMM][I]: Tue Feb 15 14:43:49 2011 [VMM][I]: . Stdout: ExitCode: 1 Tue Feb 15 14:43:49 2011 [VMM][I]: ExitCode: 1 I don't know where could be the error. Thanks in advance regards Antoni Artigues ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
