Hi Eduardo,
Yes, df can be used as a non-root user, at least in ESX 5.1. I cannot
reproduce your scenario.
ssh configuration can be changed to log in as root to the esx, but
this is not recommended for production environments.
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
Still doesn't work.
I look in some vmware forums and the vmware staff told that this kind
of command is just for the root user.
Do you have an ESXi host and can issue this command as non-root?
On Thu, Dec 19, 2013 at 1:39 PM, Tino Vazquez wrote:
> Weird, it does work in my setup with those perm
Weird, it does work in my setup with those permissions.
Try setting setuid bit (chmod +s) and see if that helps,
-T
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in
As root the output is
-r-xr-xr-x1 root root 3357 Aug 19 2011 /sbin/df
On Thu, Dec 19, 2013 at 1:29 PM, Tino Vazquez wrote:
> Hi Eduardo,
>
> I see. What is the output of
>
> ls -l /sbin/df*
>
> Regards,
>
> -Tino
>
> --
> OpenNebula - Flexible Enterprise Cloud Made Simple
Hi Eduardo,
I see. What is the output of
ls -l /sbin/df*
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova
--
Confidentiality Warning: The
Tino,
The message "Error during version check: Failed to get vmkernel
version: Operation not permitted (running as non-root?)" appears when
I try to issue the "df" command in the host as oneadmin user.
On Thu, Dec 19, 2013 at 1:05 PM, Tino Vazquez wrote:
> Hi Eduardo,
>
> Please send through a
Hi Eduardo,
Please send through a bit more of context of the log, the previous and
following lines to the error:
"Error during version check: Failed to get vmkernel version: Operation
not permitted (running as non-root?)"
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Hello Tino,
The error was a problem in the last installation of ESXi, we perform a
fresh standard installation and this works.
About the problem, I perform the chmod but still got the same error message.
Eduardo
On Thu, Dec 19, 2013 at 7:51 AM, Tino Vazquez wrote:
> Hi Eduardo,
>
> I'll be in
Hi Eduardo,
I'll be interested in the patch for the 'non df' host, can you share that?
About the error, maybe you are missing this setuid:
chmod +s /bin/vim-cmd
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure
Hello again,
I fix the problem with the `non df` host and now the command is OK.
But it only works as a root, when I issue the command as oneadmin I go
the "Error during version check: Failed to get vmkernel version:
Operation not permitted (running as non-root?)" message.
There is something to
Hello Tino,
The "df" command does not exists in my version of ESXi (5.0).
After a serch in the VMWare KB, I found that the command to be used to
monitor vmfs disks is the "vdf".
But the sintax is quite different, I'll try to get more information
and send to you.
Eduardo
On Mon, Dec 16, 2013
Hi Eduardo,
>From the DS template, we see that
0
0
772
So there is a failure monitoring TOTAL and FREE space in the DS. This
comes from the following line in the monitoring script:
DF_STR=\$($DF -m | grep ${BASE_PATH%/} | sed -e 's/ \+/:/g')
Let's try this manually. What's the output of
Hello Tino,
I Change the datastore to be compatible with these parameters, as seen below
1
0
0
oneadmin
oneadmin
default
1
1
0
1
0
0
1
0
0
vmfs
vmfs
/vmfs/volumes/1
0
0
-1
0
0
772
Hi Eduardo,
The system datastore is monitored in different way than the images
one. In any case, for a correct storage configuration for VMware you
need:
* system datastore with 'vmfs' TM and /vmfs/volumes BASE_PATH
* images_datastore with 'vmfs' TM and 'vmfs' DS and /vmfs/volumes BASE_PATH
R
Tino,
But I have the same configuration with datastore "0" and it works.
Also I set the BASE_PATH in the template after the creation (they are
the default datastores).
""
Here is the output for the show command of the datastore "0"
0
0
0
oneadmin
oneadmin
system
1
1
Hi Eduardo,
On Wed, Dec 11, 2013 at 1:08 PM, Eduardo Roloff wrote:
> /var/lib/one/datastores/1
That's probably the reason why the DS is not getting properly
monitored. The BASE_PATH needs to point to /vmfs/volumes, you can set
it at DS creation time by adding it to the DS template.
Best,
-T
Hello Tino,
Yes, I have a bridge_list with this datastore.
And yes, the datastore seems to be successfully monitored
Wed Dec 11 13:06:15 2013 [ImM][D]: Datastore default (1) successfully monitored.
Here are the output of the show command
1
0
0
oneadmin
oneadmin
default
1
Hi Eduardo,
Ok, we need to focus on this error then, seems like the monitoring of
the host datastores is not working. Did you use a BRIDGE_LIST for the
datastore template?
Please send us the output of
$ onedatastore show -x
where ds_id is the id of the vmfs images datastore that claims it
does
Tino,
When I try to use a "vmfs" volume for image repository, It not works.
I follow the instructions on the documentation, but ONE can't get the
size of the volume.
When I try to upload an image to this datastore, I receive the message
"not enough space"
Mon Dec 9 17:43:59 2013 [ReM][E]: Re
Hi Eduardo.
On Mon, Dec 9, 2013 at 4:09 PM, Eduardo Roloff wrote:
> fs
That's the problem. The images datastore for VMware _must_ have a
'vmfs' DS drivers (as well as a BRIDGE_LIST). This explains why the
.vmdk is getting renamed (as the 'fs' ds drivers don't know howto
perform this renaming.
Hello Tino,
here are the output.
1
0
0
oneadmin
oneadmin
default
1
1
0
1
0
0
1
0
0
fs
vmfs
/var/lib/one/datastores/1
0
0
-1
10079
5402
2692
4
On Mon, Dec 9, 2013 at 7:53 AM,
Hi,
On Fri, Dec 6, 2013 at 6:33 PM, Eduardo Roloff wrote:
> Configured to access the VMWare host and the System DS to use vmfs
> (the Image DS I keep local).
That might be the issue, what is the output of
$ onedatastore show -x
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made S
More information.
I downloaded the Cloud Sandbox for Virtual Box.
Configured to access the VMWare host and the System DS to use vmfs
(the Image DS I keep local).
And when I import the TTY in vmware format, I got the same, It was
imported (and tranfered when try to create a VM) with the original
Hello Tino,
I create another Nebula front-end from scratch.
And the same is happens, all the images are imported to Nebula with
the original filenames.
Eduardo
On Thu, Dec 5, 2013 at 1:56 PM, Eduardo Roloff wrote:
> Tino,
>
> There is no "Error renaming file" in the log
>
> The only mention ab
Tino,
There is no "Error renaming file" in the log
The only mention about my image import process was below
Thu Dec 5 13:50:48 2013 [ImM][I]: Copying
/var/tmp/thin-body20131205-2910-1o35uep-0 to repository for image 19
Thu Dec 5 13:50:53 2013 [ImM][I]: Image (19) copied and ready to use.
Edua
Strange indeed. I've just tried on a 4.4 and imports as disk.vmdk from ttylinux.
This is the renaming code:
---
if [ -d "$SRC" -a ! -f "$SRC/disk.vmdk" ]; then
BASE_DISK_FILE=`ls $SRC | grep '\.vmdk$' | grep -v
'\-\(flat\|delta\|s[0-9]*\)\.vmdk$'`
exec_and_log "mv -f $SRC/$BASE_DISK_FILE
Just to isolate any problems with the images generated by me I
download the TTY-VMWARE from the Nebula Marketplace and import it.
It was imported with the name "ttylinux.vmdk".
On Thu, Dec 5, 2013 at 1:29 PM, Eduardo Roloff wrote:
> Tino,
>
> I created two images now, (1) disk,vmk and (2) RHEL.v
Tino,
I created two images now, (1) disk,vmk and (2) RHEL.vmdk.
I compressed both with tar.gz and imported to OpenNebula using Sunstone.
The (1) is imported with disk,vmdk name and the (2) was imported with
the RHEL.vmdk name.
Both are functional, but when I transfer to the VMWare host they are
Hi Eduardo,
On Thu, Dec 5, 2013 at 3:28 PM, Eduardo Roloff wrote:
> When I import the image, it supposed to be renamed to disk.vmdk?
Exactly, the import process should rename it automatically, and fail
otherwise. Not sure why this is not the case, if you reimport the
image again, does it get ren
Tino,
The copy of the image occurs without problems.
The path " /volumes/vmfs//12/disk.0" exists and the disk file
is copied with the original filename like RHEL-x64.vmdk.
But when the BOOT will occurrs, the Nebula script is using "disk.vmdk"
instead of the "RHEL-x64.vmdk"
When I import the ima
Hi Eduardo,
All registered vmdks (regardless or whether they are compressed or
not) are renamed to disk.vmdk, for internal handling.
The problem you are experiencing is that the prolog is not copying the
image properly, probably due to a misconfiguration.
Could you check that the following path
Hello,
I configured a ONE 4.4 installation with CentOS in the front end and
ESXi on hosts.
I uploaded an vmware image through sunstone (RHEL-x64.vmdk) using the
tar.gz format.
But when I try to instantiate a VM using this image the front end
tranfer the image to the host, but when it tryes to st
32 matches
Mail list logo
